Skip to main content
Glama

OMOP MCP Server

License arXiv

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

OMapper Screenshot

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:

  1. uv installed on your system

  2. Clone the repository

    git clone https://github.com/OHNLP/omop_mcp.git
    cd omop_mcp
  3. 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

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"]
    }
  }
}

Related MCP server: PubMed Advanced MCP Server

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

Available Tools

2 tools
batch_map_concepts_from_csvC

Process a CSV file of keywords, mapping each row and returning a CSV with mapping results appended as new columns.

Inputs: csv_path (required).

find_omop_conceptB
Find OMOP concepts for a given keyword, table, and field.
Returns multiple candidates for LLM to choose from based on context.

Args:
    keyword: The clinical term to map
    omop_table: The OMOP CDM table name
    omop_field: The concept ID field name
    max_results: Maximum number of candidate concepts to return

Returns:
    Dict containing candidate concepts or error information if no results found.

Inputs: keyword (required), omop_field (required), omop_table (required), max_results.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one handles single keyword lookup, the other processes CSV files in batch. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow a consistent snake_case pattern with descriptive verbs (find, batch_map) and nouns (concept, concepts from CSV), making them predictable.

    Tool Count3/5

    With only 2 tools, the set feels thin even for a narrow domain. While it covers the core mapping function, a few more tools (e.g., get concept details) would make it more robust.

    Completeness3/5

    The tools cover single and batch mapping, which are the primary use cases. However, missing operations like retrieving concept details or filtering by domain leave minor gaps for advanced workflows.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      This MCP server provides 16 intelligent tools for searching, retrieving, and linking biomedical literature from PubMed and PMC. It enables LLM applications to perform complex queries, batch processing, and cross-database linking.
      16
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides access to the NIH UMLS API and the NIH VSAC FHIR API. This server enables AI models to search medical terminology, look up concept definitions, explore relationships between medical concepts, map codes between different medical coding systems, and work with curated clinical value sets.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for FHIR interoperability, enabling natural language querying and manipulation of clinical data with full CRUD operations, semantic search, and RAG capabilities.
      13
      MIT