Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP server for OMOP concept mapping
This project provides an MCP server for turning free-text clinical terms into OMOP concepts. It connects an agent to OMOP Hub vocabulary search, concept suggestion, and terminology mapping, so the agent can work with standardized medical terms in context.
Builders who want an MCP-connected agent to map clinical terminology into OMOP concepts.
You can standardize medical terms into OMOP concepts without leaving your agent workflow.
What it does
Clinical term mapping
Maps free-text clinical terms to standardized OMOP concepts with LLM help.
OMOP Hub vocabulary search
Uses the OMOPHub API for concept lookup and suggestion.
Batch mapping
Includes a CSV-based batch mapping tool in `scripts/batch_mapping.py`.
Domain-aware concept choice
Prioritizes vocabularies by OMOP domain, such as LOINC for measurements and SNOMED for conditions.
Live OMOP documentation access
Exposes OMOP CDM documentation as a resource for the agent.
How to get it
- 1Clone the repository
git clone https://github.com/OHNLP/omop_mcp.git cd omop_mcp
- 2Copy .env.template to .env and fill in your API credentials. You will need both an LLM…
cp .env.template .env
- 3Prompt
Map `Temperature Temporal Scanner - RR` for `measurement_concept_id` in the `measurement` table.
README
OMOP MCP Server
Model Context Protocol (MCP) server for mapping clinical terminology to Observational Medical Outcomes Partnership (OMOP) concepts using Large Language Models (LLMs). The vocabulary API is supported by OMOP HUB, and you can obtain an API key from omophub.com.
Demo Website

Overview
This server provides an agentic framework to standardize medical terms into the OMOP Common Data Model (CDM). It uses the OMOPHub API for vocabulary searching, concept suggestion, and terminology mapping.
Installation
Before configuring the MCP server, ensure you have:
-
uv installed on your system
- Install from: https://docs.astral.sh/uv/getting-started/installation/
-
Clone the repository
git clone https://github.com/OHNLP/omop_mcp.git cd omop_mcp -
Set up environment variables
Copy
.env.templateto.envand fill in your API credentials. You will need both an LLM provider key and an OMOPHUB_API_KEY (for vocabulary lookups).cp .env.template .env
Configuration for Claude Desktop
Add the following configuration to your claude_desktop_config.json file:
Location:
- MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
Configuration:
Replace <path-to-local-repo> with the actual path to your cloned repository.
{
"mcpServers": {
"omop_mcp": {
"command": "uv",
"args": ["--directory", "<path-to-local-repo>", "run", "omop_mcp"]
}
}
}
Features
The OMOP MCP server provides tools and resources for:
- Mapping clinical terminology: Intelligent mapping of free-text terms to standardized OMOP concepts.
- Vocabulary Search: Direct access to OMOP vocabulary via
find_omop_concept. - Batch Processing: Tool for mapping multiple concepts from a CSV file.
- Preferred Vocabularies: Automatic domain-specific vocabulary prioritization (e.g., LOINC for measurements, SNOMED for conditions).
- Live Documentation: Resource access to live OMOP CDM documentation.
Usage Example
The agent is most effective when you provide context such as the OMOP table or field name.
Prompt:
Map `Temperature Temporal Scanner - RR` for `measurement_concept_id` in the `measurement` table.
Response Example:
CONCEPT_ID: 46235152
CODE: 75539-7
NAME: Body temperature - Temporal artery
CLASS: Clinical Observation
CONCEPT: Standard
VALIDITY: Valid
DOMAIN: Measurement
VOCAB: LOINC
REASON: This LOINC concept specifically represents body temperature measured at the temporal artery.
URL: https://omophub.com/concepts/46235152
Contributing
See CONTRIBUTING.md for guidelines to contribute to the project.
Citation Policy
If you use this software, please cite the pre-print at arXiv (cs.AI) below:
An Agentic Model Context Protocol Framework for Medical Concept Standardization
License
This project is licensed under the Apache License 2.0. See LICENSE file for details.
Contact: jaerongahn@gmail.com
Files in the repo
- .github
- assets
- notebooks
- reference
- scripts
- src
- .env.template
- .gitignore
- .pre-commit-config.yaml
- .python-version
- cliff.toml
- CONTRIBUTION.md
- Dockerfile
- LICENSE
- omop_mcp_config.template.json
- pyproject.toml
- README.md
- uv.lock
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.
20 MB lightweight cross-platform database client for 90+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 90+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP Server。