Healsens Fhirmcp MCP Server

Open-source, conformance-aware MCP server for FHIR R4 and R5. The healsens fhirmcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

• FHIR-aware instead of endpoint-agnostic
• grounded in real conformance metadata instead of prompt-only assumptions
• safe by design with a read-only toolset and a fixed target server
• usable in production integration flows over stdio or native SSE

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• fhir_read — fhir_search
• fhir_capability_statement — fhir_structure_definition
• fhir_operation_definition — fhir_invoke_operation

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the healsens fhirmcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Healsens Fhirmcp's toolset — fhir_read, fhir_capability_statement, fhir_operation_definition — is a fair guide to whether it matches your workflow. It is maintained by healsens; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.