OMOPHub

MCP server for the OHDSI OMOP standard medical vocabularies (SNOMED CT, ICD-10, RxNorm, LOINC and 120+ more): search concepts, look up a code, map it across vocabularies, walk hierarchies and resolve FHIR codes from Claude, Cursor, VS Code and other MCP clients. A coding and data-mapping reference, not clinical advice.

📊 Data & notebooksReader submission6Updated 2026-10-24By OMOPHubLicense: MITAuth: OMOPHub API key (free account: 3,000 API calls a month); local npx/Docker server reads OMOPHUB_API_KEY, hosted server takes it as a Bearer headerGitHub ↗

Found viaWebReader submission GitHubOMOPHub/omophub-mcp (GitHub) MakerOMOPHub pricing

Test results

No full client pass yet

Claude CodeNot tested yet—

CursorNot tested yet—

Claude DesktopNot tested yet—

ChatGPT (Codex)Not tested yet—

In the free test queue: #55, est. Thu, Jan 14. Skip the line with a $29 or $99 priority test.

Protocol: not tested

Install

claude mcp add omophub -- npx -y @omophub/omophub-mcp

Set OMOPHUB_API_KEY in your environment first. Hosted option: claude mcp add omophub --transport http -H "Authorization: Bearer <your key>" https://mcp.omophub.com

{
  "mcpServers": {
    "omophub": {
      "command": "npx",
      "args": ["-y", "@omophub/omophub-mcp"],
      "env": { "OMOPHUB_API_KEY": "<your key>" }
    }
  }
}

Save in .cursor/mcp.json. Or use the hosted server: "url": "https://mcp.omophub.com" with an Authorization: Bearer header.

{
  "mcpServers": {
    "omophub": {
      "command": "npx",
      "args": ["-y", "@omophub/omophub-mcp"],
      "env": { "OMOPHUB_API_KEY": "<your key>" }
    }
  }
}

Settings > Developer > Edit Config. The README says Claude Desktop's custom connector UI can't send the key header, so use npx.

From the maker’s docs (checked Oct 26, 2026). Our harness hasn’t run this server yet, so these steps are not verified by us.

Not connecting? Troubleshooting: Claude Code · Cursor · Claude Desktop · ChatGPT (Codex)

Test history

No test runs yet.