Search ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP. STDIO or Streamable HTTP.
Connect Clinicaltrialsgov to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Search ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP. STDIO or Streamable HTTP. The clinicaltrialsgov mcp server is what makes that connection.
Seven tools for searching, discovering, analyzing, and matching clinical trials:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
clinicaltrials_search_studies — Primary search tool with full ClinicalTrials.gov query capabilitiesclinicaltrials_get_study_results — The clinicaltrials_get_study_results tool exposed by this serverclinicaltrials_find_eligible — The clinicaltrials_find_eligible tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration is passed through the environment: MCP_TRANSPORT_TYPE, CT_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Clinicaltrialsgov's toolset — clinicaltrials_search_studies, clinicaltrials_get_study_results, clinicaltrials_find_eligible and 2 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| clinicaltrials_search_studies | Primary search tool with full ClinicalTrials.gov query capabilities. |
| clinicaltrials_get_study_results | The clinicaltrials_get_study_results tool exposed by this server. |
| clinicaltrials_find_eligible | The clinicaltrials_find_eligible tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
{
"mcpServers": {
"clinicaltrialsgov-mcp-server": {
"type": "streamable-http",
"url": "https://clinicaltrials.caseyjhand.com/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Configuration value read at startup. | Optional |
| CT_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.