The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Omop MCP listing page.
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
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).
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.
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:
Response Example:
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