MedData MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEDDATA_API_KEY | Yes | Your MedData API key (required) | |
| MEDDATA_TIMEOUT | No | Request timeout in seconds, defaults to 30 | 30 |
| MEDDATA_BASE_URL | No | Base URL for MedData API, defaults to https://meddata.anthesia.io | https://meddata.anthesia.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_drugsA | Search for drugs by brand or generic name. Returns matching drugs with their RxCUI (the identifier you pass to get_drug), generic and brand names, and dosage form/strength when known. Use this first when you have a drug name but need its details or RxCUI. Args: name: Brand or generic drug name, e.g. "aspirin" or "Lipitor". limit: Max results to return (1-50). |
| get_drugA | Get the full profile for a drug by its RxCUI. Returns names, dosage forms, NDC codes, label sections, and related data. Get the RxCUI from search_drugs first if you only have a name. Args: rxcui: RxNorm Concept Unique Identifier, e.g. "1191" for aspirin. |
| get_drug_by_ndcA | Get a drug profile by its NDC (National Drug Code) package code. Use when you have an NDC from a label or packaging rather than a name. Args: ndc_code: NDC code, e.g. "0363-0160". |
| search_supplementsA | Search for dietary supplements by name. Returns matching supplements with their IDs (pass to get_supplement) and summary info. Use first when you have a supplement name like "Vitamin D" or "Fish Oil". Args: name: Supplement name, e.g. "Vitamin D" or "magnesium". limit: Max results to return (1-50). |
| get_supplementA | Get the full fact sheet for a supplement by its ID. Returns ingredients, recommended intake, and NIH reference data. Get the ID from search_supplements first. Args: supplement_id: Numeric supplement ID from search_supplements. |
| check_interactionsA | Check interactions across a mixed list of drugs and supplements. Accepts 2-10 items (drug names, supplement names, or both) and returns known interactions among them. Interaction data comes from established medical databases; it is never generated or inferred, so an empty result means none were found in those sources, not that the combination is proven safe. Args: items: 2-10 drug and/or supplement names, e.g. ["warfarin", "aspirin", "Fish Oil"]. |
| get_usageB | Show this API key's current billing period usage and plan limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: check_interactions for interactions, get_drug and get_drug_by_ndc for drug profiles by different identifiers, get_supplement for supplement profiles, search tools for lookup, and get_usage for billing. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., search_drugs, get_drug_by_ndc, check_interactions). The naming style is uniform and predictable.
With 7 tools, the server is well-scoped for its purpose of drug and supplement information retrieval and interaction checking. Each tool earns its place without overcomplicating the surface.
The tool set covers search and retrieval for both drugs and supplements, plus interaction checking. A minor gap is the lack of a direct way to check interactions involving a single drug or supplement against a broader set, but the core workflows are supported.