MedData MCP Server
mcp-name: io.github.anthesiallc/meddata
A Model Context Protocol server that exposes the MedData API as tools, so any MCP client (Claude Desktop, Cursor, ChatGPT connectors, or an agent framework) can look up drug and supplement data and check interactions conversationally.
It's a thin wrapper: each tool maps to one MedData REST endpoint. All the data work happens in the API.
Tools
| Tool | What it does |
|---|---|
search_drugs |
Search drugs by brand or generic name; returns RxCUI + details |
get_drug |
Full drug profile by RxCUI |
get_drug_by_ndc |
Drug profile by NDC package code |
search_supplements |
Search supplements by name; returns supplement IDs |
get_supplement |
Full supplement fact sheet by ID |
check_interactions |
Interactions across a mixed list of 2-10 drugs/supplements |
get_usage |
Current billing period usage and plan limit |
Get an API key
Free tier is 250 calls/month, no credit card:
curl -X POST https://meddata.anthesia.io/api/v1/signup \
-H 'Content-Type: application/json' \
-d '{"email":"you@example.com"}'
The key comes back in the api_key field of the response.
Install and run
The easiest way is with uv (no manual venv needed):
# stdio transport (default — for Claude Desktop, Cursor, most local clients)
MEDDATA_API_KEY=md_your_key uvx meddata-mcp
# streamable-HTTP transport (for remote / web clients)
MEDDATA_API_KEY=md_your_key uvx meddata-mcp --http
Or install with pip into its own environment:
pip install meddata-mcp
MEDDATA_API_KEY=md_your_key meddata-mcp
Note: install into a dedicated environment. The
mcpSDK requires a newerstarlettethan the MedData API app pins, so the two will conflict if installed together.
Environment variables:
MEDDATA_API_KEY(required) — your MedData API key.MEDDATA_BASE_URL(optional) — defaults tohttps://meddata.anthesia.io.MEDDATA_TIMEOUT(optional) — request timeout in seconds, default30.
Client configuration
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"meddata": {
"command": "uvx",
"args": ["meddata-mcp"],
"env": { "MEDDATA_API_KEY": "md_your_key" }
}
}
}
Cursor
Add the same block to ~/.cursor/mcp.json (or the project .cursor/mcp.json).
Develop from source
cd mcp_server
python -m venv .venv
.venv/Scripts/python -m pip install -e . # Windows
# .venv/bin/pip install -e . # macOS/Linux
MEDDATA_API_KEY=md_your_key .venv/Scripts/python -m meddata_mcp.server
Notes
- Data is for informational purposes only and is not medical advice.
- Interaction data comes from established medical databases; an empty result means none were found in those sources, not that a combination is proven safe.
Metadata
Release files for meddata-mcp 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meddata_mcp-0.2.1.tar.gz | 8.1 kB | Without provenance | Details for meddata_mcp-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meddata_mcp-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for meddata_mcp-0.2.1-py3-none-any.whl |
Total release size: 17.3 kB
Release files / meddata_mcp-0.2.1.tar.gz
| Download URL | meddata_mcp-0.2.1.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
380d75aaf1fdfaa7e877ecac85229922bddf7f45d8483cd90e9db726dcb81386
|
|
BLAKE2b-256 checksum How to use checksums |
5795486ee1ff1d914b3cfbc7515341ad608fdb18edc3d653766661fed5a476b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / meddata_mcp-0.2.1-py3-none-any.whl
| Download URL | meddata_mcp-0.2.1-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
babf9328745f28e63cc4c5f7087c039312a7af1de920eb3127285a5b3dc75f4c
|
|
BLAKE2b-256 checksum How to use checksums |
dbf866e88e896b9cf64bced8a2c906588681d8dac382c946a50b9028470eef17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for meddata-mcp 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.