Conversational access to ClinicalTrials.gov — an MCP server for pharma analysts, CRO teams, and health-tech builders
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"clinicaltrials-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# clinicaltrials-mcp **Conversational access to 400,000+ clinical trials — for pharma analysts, CRO teams, and health-tech builders.** A Python MCP server that connects Cursor, Claude Desktop, and any MCP-compatible client directly to ClinicalTrials.gov. Ask questions in plain English. Get clean, structured answers in seconds — no API keys, no setup, no parsing raw JSON. [](https://pypi.org/project/clinicaltrials-mcp/) [](https://www.python.org/downloads/) [](LICENSE) --- ## The Problem Today's workflow for a pharma analyst: 1. Go to clinicaltrials.gov 2. Struggle with the filter UI 3. Export raw JSON 4. Parse it manually or write a one-off script 5. Copy into Excel or Word 6. Repeat 40 times for a competitive analysis 7. **Total time: 2–3 days** With clinicaltrials-mcp in Cursor or Claude Desktop: 1. Ask a question in plain English 2. Get a structured, synthesised answer in seconds 3. Follow up, drill down, compare — conversationally 4. **Total time: 20 minutes** --- ## Install & Setup ### Step 1 — Install ```bash pip install clinicaltrials-mcp ``` No API key. No account. No configuration required. ### Step 2 — Add to your MCP client ```json { "mcpServers": { "clinicaltrials": { "command": "uvx", "args": ["clinicaltrials-mcp"] } } } ``` `uvx` runs the package without requiring it on your `$PATH`. If you don't have `uv`: `pip install uv`. Restart your MCP client. The 5 tools appear automatically. --- ### Running from source (contributors / developers) ```bash git clone https://github.com/agents100x/clinicaltrials-mcp cd clinicaltrials-mcp uv sync ``` ```json { "mcpServers": { "clinicaltrials": { "command": "uv", "args": [ "run", "--directory", "/path/to/clinicaltrials-mcp", …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.