openEHR Assistant FAQs

Question 1

How can developers quickly get started with openEHR Assistant?

Accepted Answer

Developers can quickly deploy openEHR Assistant using Docker. Pre-built Docker images are available, and the README provides a quick start guide for running it with Docker Compose in both production and development environments.

Question 2

What are the core technical features of this MCP server?

Accepted Answer

Key features include a PSR-compliant PHP 8.4 codebase, attribute-based MCP tool discovery, robust Docker images, support for streamable HTTP and stdio transports, structured logging with Monolog, and simple environment-driven configuration.

Question 3

What is openEHR Assistant and what does it do?

Accepted Answer

openEHR Assistant is a PHP 8.4 Model Context Protocol (MCP) server designed to help end-users perform various openEHR-related tasks and interact with openEHR APIs. It acts as a bridge, making openEHR data and specifications accessible to AI assistants and other MCP clients.

Question 4

What specific openEHR resources and tools does it expose?

Accepted Answer

openEHR Assistant exposes tools to interact with Clinical Knowledge Manager (CKM) for searching and retrieving archetypes, and for searching/getting openEHR Type specifications (BMM JSON). It also offers optional guided prompts to orchestrate multi-step workflows with these tools.

Question 5

Which AI assistants and clients can I use with openEHR Assistant?

Accepted Answer

The server is compatible with any MCP-enabled client, including popular AI assistants like Claude Desktop, Cursor, and LibreChat. It allows these clients to discover and utilize the openEHR tools and prompts it provides.

openEHR Assistant

openEHR Assistant

Key Features

Use Cases

Key Features

Use Cases