fhir-mcp-server and openehr-server-mcp
Both tools implement the Model Context Protocol (MCP) and thus serve the same purpose of exposing data through MCP, but one is for FHIR servers while the other is for openEHR servers, making them complementary for systems needing to expose both data models via MCP, or competitors for an organization choosing between FHIR and openEHR.
About fhir-mcp-server
wso2/fhir-mcp-server
FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.
This tool helps healthcare developers and innovators connect AI and large language models (LLMs) to healthcare data. It takes information from any existing FHIR server or API, transforms it, and makes it accessible to modern AI/LLM tools like VS Code or Claude Desktop. This allows developers to easily search, retrieve, and analyze clinical information using AI.
About openehr-server-mcp
Cadasto/openehr-server-mcp
An openEHR Model Context Protocol (MCP) Server implemented in PHP
Exposes openEHR REST operations (templates, compositions, EHR management, AQL execution) as MCP tools with attribute-based discovery via PHP SDK, bridging AI assistants to clinical data systems. Includes guided prompts for common workflows (vital signs, assessments, medication review) and supports both stdio and streamable HTTP transports via Caddy with environment-driven configuration. Designed to complement the openEHR Assistant MCP Server for complete EHR ecosystem integration.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work