Omophub Mcp

OMOPHub MCP Server

Medical vocabularies for AI agents.
Search, map, and navigate 11M+ OMOP concepts: SNOMED CT, ICD-10, RxNorm, LOINC, and more. Directly from Claude, Cursor, VS Code, or any MCP-compatible client.

[npm version] [Codecov] [npm downloads] [License] [TypeScript] [MCP Compatible]

Quick Start · Tools · Examples · Docs · Website

Why OMOPHub MCP?

Working with medical vocabularies today means downloading multi-gigabyte CSV files, loading them into a local database, and writing SQL to find what you need. Every time.

OMOPHub MCP Server gives your AI assistant instant access to the entire OHDSI ATHENA vocabulary. No database setup, no CSV wrangling, no context switching. Just ask.

You: "Map ICD-10 code E11.9 to SNOMED"
Claude: Found it - E11.9 (Type 2 diabetes mellitus without complications)        maps to SNOMED concept 201826 (Type 2 diabetes mellitus)        via standard 'Maps to' relationship.

Use cases:

• Concept lookup - Find OMOP concept IDs for clinical terms in seconds
• Cross-vocabulary mapping - Map between ICD-10, SNOMED, RxNorm, LOINC, and 120+ vocabularies
• Hierarchy navigation - Explore ancestors and descendants for phenotype definitions
• Concept set building - Let your AI agent assemble complete concept sets for cohort definitions
• Code validation - Verify medical codes and check their standard mappings

Quick Start

1. Get an API Key

Sign up at omophub.com → create an API key in your dashboard.

2. Add to Your AI Client

{  "mcpServers": {    "omophub": {      "command": "npx",      "args": ["-y", "@omophub/omophub-mcp"],      "env": {        "OMOPHUB_API_KEY": "oh_your_key_here"      }    }  }}

claude mcp add omophub -- npx -y @omophub/omophub-mcp# Then set OMOPHUB_API_KEY in your environment

{  "mcpServers": {    "omophub": {      "command": "npx",      "args": ["-y", "@omophub/omophub-mcp"],      "env": {        "OMOPHUB_API_KEY": "oh_your_key_here"      }    }  }}

{  "servers": {    "omophub": {      "command": "npx",      "args": ["-y", "@omophub/omophub-mcp"],      "env": {        "OMOPHUB_API_KEY": "oh_your_key_here"      }    }  }}

# Start HTTP server on port 3100npx -y @omophub/omophub-mcp --transport=http --port=3100 --api-key=oh_your_key_here
# MCP endpoint: http://localhost:3100/mcp# Health check:  http://localhost:3100/health

claude mcp add omophub --transport http \  -H "Authorization: Bearer oh_your_key_here" \  https://mcp.omophub.com

{  "servers": {    "omophub": {      "type": "http",      "url": "https://mcp.omophub.com",      "headers": { "Authorization": "Bearer oh_your_key_here" }    }  }}

{  "mcpServers": {    "omophub": {      "url": "https://mcp.omophub.com",      "headers": { "Authorization": "Bearer oh_your_key_here" }    }  }}

# HTTP mode (default in Docker) - serves MCP on port 3100docker run -e OMOPHUB_API_KEY=oh_your_key_here -p 3100:3100 omophub/omophub-mcp
# Stdio mode (for piping)docker run -i -e OMOPHUB_API_KEY=oh_your_key_here omophub/omophub-mcp --transport=stdio

3. Start Asking

"What's the OMOP concept ID for type 2 diabetes?"

"Map ICD-10 code E11.9 to SNOMED"

"Show me all descendants of Diabetes mellitus in SNOMED"

Available Tools

Resources

Prompts

Example Prompts

Find a concept → search_concepts

"Search for metformin in RxNorm"

Cross-vocabulary mapping → map_concept

"I have SNOMED concept 201826 - what's the ICD-10 code?"

Build a concept set → search_concepts → get_hierarchy → map_concept

"Help me build a concept set for Type 2 diabetes including all descendants"

Completeness matters here. map_concept returns one page at a time (page_size 1-200, default 100). A widely-used drug ingredient can have well over a thousand NDC mappings, so a single call is a sample, not the answer. Check has_more in the response and keep incrementing page until it is false — otherwise the concept set looks complete while silently missing codes.

Use find_similar_concepts for exploration, not for this: it is ranked embedding similarity, so it has no notion of set membership and cannot be exhaustive no matter how large page_size is.

Validate a code → get_concept_by_code → map_concept

"Is ICD-10 code E11.9 valid? What does it map to in SNOMED?"

Semantic search → semantic_search

"Find concepts related to 'heart attack'"

Explore a concept → explore_concept

"Give me everything about SNOMED concept 201826"

FHIR-to-OMOP resolution → fhir_resolve

"Resolve FHIR SNOMED code 44054006 to OMOP — what table does it go in?"

CodeableConcept → fhir_resolve_codeable_concept

"This CodeableConcept has both SNOMED 44054006 and ICD-10 E11.9 — which should I use for OMOP?"

Find similar → find_similar_concepts

"What concepts are similar to 'Type 2 diabetes mellitus'?"

Configuration

Environment Variables

CLI Arguments

# Stdio mode (default)npx @omophub/omophub-mcp --api-key=oh_your_key --base-url=https://custom.api.com/v1
# HTTP modenpx @omophub/omophub-mcp --transport=http --port=3100 --api-key=oh_your_key
# Stdio mode with standalone health endpointnpx @omophub/omophub-mcp --api-key=oh_your_key --health-port=8080

Health Endpoint (Docker / Kubernetes)

In HTTP mode, the health endpoint is available at /health on the same port as the MCP endpoint:

npx @omophub/omophub-mcp --transport=http --port=3100 --api-key=oh_your_keycurl http://localhost:3100/health# → {"status":"ok","version":"1.5.0","uptime_seconds":42}

In stdio mode, use --health-port for a standalone health endpoint:

HEALTH_PORT=8080 OMOPHUB_API_KEY=oh_your_key npx @omophub/omophub-mcpcurl http://localhost:8080/health

The Docker image defaults to HTTP mode on port 3100 with health checks built in.

Development

git clone https://github.com/OMOPHub/omophub-mcp.gitcd omophub-mcpnpm installnpm run buildnpm test

Run locally:

OMOPHUB_API_KEY=oh_your_key npx tsx src/index.ts

Troubleshooting

Links

• Documentation
• Get an API Key
• Python SDK
• Community & Support

License

MIT - see LICENSE