omop_mcp

Name: omop_mcp Review
Item: omop_mcp
Rating: 2.0
Author: Aaron Matthews

Connector Development Poor

Works inClaude Code Claude Cowork Claude Chat

Poor Scanned — metadata only

Reduces manual effort and error in clinical data standardization by automating terminology mapping to OMOP common data models, enabling consistent analytics …

Model Context Protocol (MCP) server for mapping clinical terminology to Observational Medical Outcomes Partnership (OMOP) concepts using Large Language Models

Ask Claude to map clinical diagnosis codes to standardized OMOP concept identifiers
Generate OMOP-compliant data structures from unstructured clinical notes and terminology
Find appropriate OMOP concept mappings for custom medical vocabulary terms quickly

39 starsFreeNo code needed

Below standard — Significant caveats apply. Not recommended without careful review of the security and evaluation sections.

Why it matters

Reduces manual effort and error in clinical data standardization by automating terminology mapping to OMOP common data models, enabling consistent analytics across healthcare systems.

Best for

Healthcare IT teams and data engineers integrating clinical data pipelines requiring OMOP standardization.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://github.com/OHNLP/omop_mcp

By OHNLP

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.

Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.

Command

claude mcp add omop_mcp -- npx -y omop_mcp

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

Once it’s connected, paste this into Claude:

Map clinical diagnosis codes to standardized OMOP concept identifiers

CostFree

Trust Signals Auto-scanned

Stars39Contributors1Last updated2026-05-11Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-25 · scanner v1

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse Active

Discussed on Hacker News, Reddit

Show HN: Open-Source FHIR –> OMOP Pipeline — Hacker News · 2 pts

1 mentions across 1 sources

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 39 GitHub stars; 1 contributors; last commit 75d ago; license no license.

Things to check

Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
Single maintainer. Consider the risk if this person stops maintaining the project.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

1/5

Versatility

2/5

Reliability

3/5

Security

3/5

Overall score2.05 / 5.00 PoorEvaluatedJul 2026

Scored from trust signals (evidence-eval-v1): 39 GitHub stars; 1 contributors; last commit 75d ago; license no license.

← Back to the Claude Observatory