Components
The openEHR Assistant is two pieces that are useful separately and better together: a server that knows openEHR, and a plugin that knows when to ask it.
Pre-release
Expect frequent updates and breaking changes until version 1.0.
MCP server
The knowledge and tooling layer. It exposes openEHR domain knowledge to AI assistants over the Model Context Protocol, so an agent can discover, explain, design and review openEHR artefacts.
Not a clinical data repository
This is a knowledge and authoring-assistance server. It reads specifications, published archetypes and its own guide corpus, and it never stores patient data.
| Hosted endpoint | https://openehr-assistant-mcp.apps.cadasto.com/ |
| Transport | streamable-http, or stdio when run locally |
| Runtime | PHP 8.4, Docker-only |
| Works with | Any MCP client — Claude Desktop, Claude Code, Cursor, LibreChat, and others |
It provides tools, guided prompts, readable openehr:// resources and argument
completions — all listed on Features.
| Repository | cadasto/openehr-assistant-mcp |
| Capability reference | Available MCP elements |
| Contributor docs | docs/ — requirements, architecture, decisions, testing |
Plugin
The workflow layer, for Claude Code and Cursor. The server answers questions; the plugin decides which questions to ask, in what order, and with which guidance loaded — turning a pile of capable tools into a modelling workflow.
It adds skills that trigger on intent, subagents for delegated retrieval, explicit slash commands, and hooks that keep openEHR conventions in view. Again, the full inventory is on Features.
| Repository | cadasto/openehr-assistant-plugin |
| Install guide | docs/install.md — install, update, MCP permissions, Cursor |
How they fit together
The plugin bundles a .mcp.json that registers the hosted server under the name
openehr-assistant. Use that same name if you also configure the server by hand,
or you will end up with two entries pointing at one endpoint.
To aim the plugin at a local or stdio server instead, follow MCP wiring in the plugin repository; Install has the server URLs and per-client configuration.
You can use the server on its own with any MCP client. The plugin, however, expects a server to talk to.
Maintainer tooling
Building tools, guides or examples for these repositories is supported by a third, separate plugin — openehr-assistant-dev. It is aimed at maintainers, not clinical end users; see Contributing.