MCP Server for FHIR® · Open source

Connect AI agents to your FHIR® server, read-only

healsens-fhirmcp is a Model Context Protocol server that gives AI agents safe access to an HL7® FHIR® R4 or R5 server, with knowledge of exactly which resources and searches that server supports.

Request a demo View on GitHub

HEALSENS-FHIRMCP / CONFIG.YAMLExample

target:
  base_url: https://fhir.example.org/fhir
  bearer_token_env: FHIR_BEARER_TOKEN
server:
  transport: sse   # or stdio

Tools exposed to the agent

fhir_readread-onlyRead one resource by type and id

fhir_searchread-onlyTyped search from the CapabilityStatement

fhir_capability_statementread-onlyWhat this server supports

fhir_structure_definitionread-onlyResource definitions

fhir_operation_definitionread-onlyOperation definitions

fhir_invoke_operationread-onlyRead-only operations

Capabilities

A small, precise tool set for agents

Agents get exactly what they need to answer questions from FHIR® data, and nothing that can change it.

Read-only by design

Every tool reads. One fixed target server. Behaviour your security team can reason about.

Schema-aware search

Typed search based on the server’s live CapabilityStatement, so agents ask valid questions instead of guessing.

FHIR® R4 and R5

Official FHIR definitions for both versions are built in.

Definitions on demand

Agents can look up structure and operation definitions while they work.

Bearer-token authentication

Works with secured servers. Patient-level access stays with your server’s own access control.

Open source

AGPL-3.0 on GitHub. Runs over stdio or SSE with any MCP client.

How it works

From configuration to grounded answers

STEP 01

Configure

Point it at one FHIR® R4 or R5 base URL. It only ever talks to that server.

STEP 02

Discover

At start-up it reads the CapabilityStatement and combines it with the built-in definitions.

STEP 03

Expose tools

Read, typed search, definitions and read-only operations become MCP tools.

STEP 04

Answer

Your assistant or agent answers questions grounded in the records on that server.

See it in action

A working demo on synthetic patient data

We run the MCP server against a FHIR® server filled with synthetic patients and connect it to an AI assistant. You ask questions; the agent finds and reads the right resources and answers from them.

Live agent sessionWatch each tool call the agent makes on the FHIR server.
Synthetic data onlyNo real patient data is used in the demo.
Your questionsBring the questions your team would ask of its own data.

Request a demo

AGENT SESSION / HEALSENS-FHIRMCPSynthetic data

Which lab observations were recorded for this patient last month?

fhir_capability_statement Observation: search by patient, category, date

fhir_search Observation?patient=…&category=laboratory&date=ge…

fhir_read Observation/… read-only

Last month’s laboratory observations are a lipid panel and an HbA1c test. Here they are with dates and units.

FHIR® R4Grounded in server data

Use cases

Where teams use it

Hospitals and clinics

Internal AI assistants

Let an assistant look up data on your existing FHIR® server without opening up write access.

Research

Exploring study data

Give analysts and agents one consistent way to explore study data held on a FHIR server.

Digital health

AI features on a FHIR backend

Add AI to your product without writing a custom connector for every model.

FAQ

Frequently asked questions

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants and agents use external tools and data sources in a consistent way.

Does it work with our FHIR® server?

If your server supports FHIR R4 or R5 and publishes a CapabilityStatement, it should. Secured servers are supported with a bearer token.

Can the agent change data?

No. Every tool is read-only.

Who decides which patient data an agent may see?

Your FHIR server. The MCP server limits what an agent can do; patient-level access stays with your existing access control.

Can you adapt it for us?

Yes. We help with deployment, configuration for your server and custom tools. See Health Data Engineering.

See it with your own questions

Request a demo on synthetic data, or tell us about your FHIR® setup and we will suggest how to connect your agents.

Request a demo