Healsens FHIR MCP

What is Healsens FHIR MCP?

Healsens FHIR MCP is an open-source, conformance-aware MCP server for FHIR R4 and R5. It fronts a configured FHIR base URL and exposes a focused, read-only MCP surface for resource read, typed search, conformance discovery, and safe read-only operations, embedding version-matched FHIR conformance artifacts combined with the live CapabilityStatement of the connected server.

How to use Healsens FHIR MCP?

Copy the example config, set target.base_url to your FHIR R4 or R5 server, export the bearer token environment variable named in the config if authentication is required, sync the vendored conformance artifacts, then build and run the server over stdio or SSE. For stdio, run the binary with FHIRMCP_CONFIG set; for SSE, configure the transport block in the config and start the server to expose an SSE endpoint at http://127.0.0.1:8081/sse.

Key features of Healsens FHIR MCP

• Single configured FHIR target server
• Read-only MCP tool surface
• FHIR R4 and R5 support
• Embedded core StructureDefinition and OperationDefinition registries
• Live CapabilityStatement fetch with caching
• Typed read and typed search
• Conservative read-only operation invocation
• Discovery and schema resources under the fhirmcp:// URI scheme
• Native stdio and SSE hosting modes

Use cases of Healsens FHIR MCP

• Making FHIR data usable by AI agents safely and predictably
• Healthcare AI integrations that need schema-aware, read-only FHIR access
• Production integration flows over stdio or native SSE
• Evaluating a credible foundation for healthcare MCP deployments

FAQ from Healsens FHIR MCP

What FHIR versions are supported?

FHIR R4 and R5 are both supported, including server-specific capability discovery at startup.

Is the server read-only?

Yes, the server is intentionally read-only by design, focused on safe retrieval, discovery, and supported read-only operations.

What transport modes are available?

The server supports both stdio (traditional subprocess MCP) and native SSE hosting modes.

How do I configure authentication?

Export the bearer token environment variable named in the config file if your FHIR server requires authentication.

Does the server support write operations?

No, this implementation deliberately does not include write capabilities; it is a read-only toolset.