Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"openEHR": {
"args": [
"run",
"-i",
"--rm",
"--network=host",
"-e",
"EHRBASE_URL=http://localhost:8080/ehrbase/rest",
"-e",
"EHRBASE_JSON_FORMAT=wt_flat",
"ctodeakai/openehr-mcp-server:latest"
],
"command": "docker"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server designed to interface with openEHR REST APIs, specifically the EHRbase implementation. This server enables MCP clients like Claude Desktop to create compositions for openEHR templates and submit them to a server. For production grade EHR integrations you must use an AI Model where you can ensure data privacy.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.
MCP server for Oura Ring API v2 (sleep, activity, readiness, heart rate, workouts).
MCP Security Weekly
Get CVE alerts and security updates for Openehr Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server designed to interface with openEHR REST APIs, specifically the EHRbase implementation. This server enables MCP clients like Claude Desktop to create compositions for openEHR templates and submit them to a server. For production grade EHR integrations you must use an AI Model where you can ensure data privacy.
See https://modelcontextprotocol.io/introduction for more information about MCP.
Current version: 0.1.0
This project follows semantic versioning. For details on our versioning strategy, see VERSIONING.md.
Not yet implemented
The easiest way to get started is to use the pre-built Docker image available on Docker Hub.
Ensure you have a running EHRbase server. For running one locally, see below.
Edit your Claude Desktop configuration file (claude_desktop_config.json) and add an "openEHR" configuration block inside the "mcpServers" section.
This file can usually be found in the following locations:
{
"mcpServers": {
"openEHR": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"-e","EHRBASE_URL=http://localhost:8080/ehrbase/rest",
"-e","EHRBASE_JSON_FORMAT=wt_flat",
"ctodeakai/openehr-mcp-server:latest"
]
}
}
}
You can point EHRBASE_URL to your own EHRbase server or use the provided docker-compose setup.
The MCP server supports different JSON serialization formats for interacting with the EHRbase API. You can configure the format using the optional EHRBASE_JSON_FORMAT environment variable:
"-e", "EHRBASE_JSON_FORMAT=wt_flat"
Available format options:
For more information on how to set up Claude Desktop with MCP servers, see https://modelcontextprotocol.io/quickstart/user.
For this MCP server to work, you currently require