Model Context Protocol (MCP) server for mapping clinical terminology to Observational Medical Outcomes Partnership (OMOP) concepts using Large Language Models
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"omop-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
omop_cdm_documentationLive OMOP Common Data Model documentation
https://omophub.com
omop_conceptOMOP concept details and information
https://omophub.com/concepts/{concept_id}
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.
MCP server for Oura Ring API v2 (sleep, activity, readiness, heart rate, workouts).
MCP Security Weekly
Get CVE alerts and security updates for Omop_mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.

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.
Before configuring the MCP server, ensure you have:
uv installed on your system
Clone the repository
git clone https://github.com/OHNLP/omop_mcp.git
cd omop_mcp
Set up environment variables
Copy .env.template to .env and 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
Add the following configuration to your claude_desktop_config.json file:
Location:
~/Library/Application\ Support/Claude/claude_desktop_config.json%APPDATA%/Claude/claude_desktop_config.jsonConfiguration:
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"]
}
}
}
The OMOP MCP server provides tools and resources for:
find_omop_concept.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
See CONTRIBUTING.md for guidelines to contribute to the project.
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
This project is licensed under the Apache License 2.0. See LICENSE file for details.
Contact: jaerongahn@gmail.com