fhir-mcp-server and omop_mcp
These are complements, as the OHNLP/omop_mcp server can be exposed as an MCP Server via wso2/fhir-mcp-server, allowing the former's OMOP concept mapping functionality to be accessible through a broader FHIR MCP interface.
About fhir-mcp-server
wso2/fhir-mcp-server
FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.
Provides multiple transport protocols (stdio, SSE, streamable HTTP) and supports SMART-on-FHIR OAuth 2.0 authentication for secure integration with healthcare systems like Epic and HAPI FHIR servers. Integrates with MCP clients including Claude Desktop, VS Code, and MCP Inspector to enable AI-powered querying and analysis of clinical data through standardized FHIR APIs.
About omop_mcp
OHNLP/omop_mcp
Model Context Protocol (MCP) server for mapping clinical terminology to Observational Medical Outcomes Partnership (OMOP) concepts using Large Language Models
Implements an agentic framework that queries the OMOPHub API for vocabulary searches and concept suggestions, with domain-specific vocabulary prioritization (e.g., LOINC for measurements, SNOMED for conditions). Integrates with Claude Desktop via stdio transport and supports batch CSV processing for standardizing clinical terminology at scale. Provides contextual mapping by leveraging table/field metadata to improve concept disambiguation.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work