Example MCP SSE Server intgrated with FHIR Server
LocalAbout Example MCP SSE Server intgrated with FHIR Server
An example MCP server that connects to a FHIR server and provides FHIR resource operations. It is intended to demonstrate MCP–FHIR integration and relies on a supplied auth token rather than implementing OAuth.
Key features
- 01Create FHIR resources
- 02Read FHIR resources
- 03Accept resource type and body or ID
Use cases
- 01Demonstrating MCP integration with FHIR
- 02Creating or reading Patient and Appointment resources
MCP support
Exposes tools to MCP clients for creating and reading resources on a connected FHIR server. Authentication uses a supplied token; FHIR OAuth is not implemented.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEExample MCP SSE Server intgrated with FHIR Server
A Model Context Protocol (MCP) server implementation that integrates with FHIR server to implement FHIR specific tool definitions. This is quick and dirty implementation and sole objective is to demonstrate MCP + FHIR integration. This implementation doesn't cover FHIR server OAuth and depends on supplied Auth token.
I have tested this integration for Patient and Appointment resources without any issues.
This MCP server implements two tools
- Create FHIR Resource
Takes Two input parameters
- ResourceType
- ResourceBody
- Read FHIR Resource
Takes Two input parameters
- ResourceType
- ResourceID
Dependencies
- @modelcontextprotocol/sdk - SDK for Model Context Protocol
- Express - Web framework for Node.js
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.