openehr

This MCP server provides a set of tools to interact with an openEHR server (EHRbase) via the MCP protocol. It exposes operations to list and retrieve templates, create and manage EHRs, and create or read openEHR compositions against a target EHRbase instance. Typical usage involves configuring Claude Desktop (or any MCP client) to connect to this MCP server, then invoking the available MCP tools such as openehr_template_list, openehr_template_get, openehr_ehr_create, openehr_composition_create, and openehr_composition_get to perform common openEHR workflows. The server communicates with the EHRbase REST API using the EHRBASE_URL you provide via environment configuration, and it supports different JSON formats through the EHRBASE_JSON_FORMAT setting.

Prerequisites:\n- Docker installed and running on your host (or a compatible container runtime).\n- Access to an EHRbase server instance (locally or remotely).\n- Optional: a Python environment if you choose to run or test scripts locally.\n\nInstall and run using Docker:\n1. Pull and run the pre-built image:\n\nbash\ndocker pull ctodeakai/openehr-mcp-server:latest\ndocker run -i --rm --network=host \\n -e EHRBASE_URL=http://localhost:8080/ehrbase/rest \\n -e EHRBASE_JSON_FORMAT=wt_flat \\n ctodeakai/openehr-mcp-server:latest\n\n2. Ensure the EHRbase server is running and accessible at the configured URL.\n3. Use Claude Desktop or your MCP client to configure the server with the same settings.\n\nAlternative: Local development (optional)\n- If you want to run tests or develop locally, set up a Python environment and replicate the configuration by invoking the server container or porting the logic as needed.\n\nIf you prefer to run in a different runtime, adapt the command accordingly to your environment and ensure the EHRbase URL and JSON format environment variable are correctly set.

Tips and common issues:\n- Ensure EHRbase is reachable at the EHRBASE_URL you configure; network/firewall issues can block access.\n- The EHRBASE_JSON_FORMAT can be set to wt_flat (default), canonical, or wt_structured; verify compatibility with your EHRbase instance.\n- When using Docker, the --network=host option simplifies local testing but may have security implications; adjust to your environment (e.g., bridge network) if required.\n- The provided CLI/tools assume the EHRbase server exposes the standard openEHR REST endpoints; verify the base path in your deployment.\n- For production-grade deployments, ensure proper authentication, secret management, and least-privilege network access.\n- If you modify templates or EHR data, validate with the MCP client’s test flows before production use.