Langcare Fhir MCP Server
FHIR R4 resources accessible in AI agents via Go-based integration.
Data last scanned today · Reviewed today
Overview
This server provides an MCP interface for interacting with FHIR-compliant Electronic Medical Records (EMR). It supports major platforms including Epic, Cerner, and OpenEMR, as well as generic FHIR R4 servers and the Google Cloud Healthcare API, using Go as its primary implementation language. The server features a library of over 40 clinical skills, covering areas like medication management, lab result interpretation, and clinical decision support. Users can also leverage additional components such as the LangCare CLI, clinical UI apps for Claude Desktop, and pre-built clinical AI agents.
Our verdict
With a security score of 24/100, this server is classified as high-risk. It lacks OAuth support and mandates full write access to your EMR without a read-only configuration option, posing significant potential for accidental data modification in a clinical environment. Given it is a community-maintained project rather than an official vendor release, it should be evaluated with extreme caution before deployment in any live health record system.
- Supports multiple EMR backends including Epic and Cerner
- Zero direct dependencies reduces supply chain attack surface
- Comprehensive documentation for 40+ clinical workflows
- Written in Go for performance and portability
- High-risk rating due to lack of read-only mode
- Authentication relies solely on bearer tokens without OAuth
- Community-maintained with a single contributor bus-factor risk
- Not subject to editorial or third-party security review
Setup
{
"mcpServers": {
"langcare-mcp-fhir": {
"args": [
"-y",
"@langcare/langcare-mcp-fhir"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
Tools
| Tool | Description | Risk |
|---|---|---|
| fhir_read | Read a FHIR resource by type and ID. | low |
| fhir_search | Search FHIR resources with query parameters. | low |
| fhir_create | Create a new FHIR resource. | medium |
| fhir_update | Update an existing FHIR resource. | medium |
| fhir_explorer | Interactive FHIR resource browser. Search, read, create, and update any FHIR R4 resource type with JSON detail views. | medium |
| patient_chart_review | Clinical dashboard with patient demographics, active conditions, medications, vitals, labs, and vitals trend charts (BP + weight over time). | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Which FHIR version is supported by this server?
The server is built specifically to support the FHIR R4 standard.
›What EMR systems are compatible with this MCP server?
It is compatible with Epic, Cerner, OpenEMR, GCP Healthcare API, and any other generic FHIR R4-compliant server.
›How is the server configured?
You must provide a YAML configuration file to the server that specifies your backend connection settings, using one of the provided templates.
›Does this server store Protected Health Information (PHI)?
No, the server acts as a stateless proxy and does not persistently store PHI.
›What authentication methods are supported for connecting to a FHIR backend?
The server supports Bearer Token, OAuth 2.0 with automatic token refresh, and mTLS for service-to-service communication.
›What are the available generic FHIR operations?
The server provides four tools: fhir_read, fhir_search, fhir_create, and fhir_update, all of which function with any FHIR R4 resource type.
Badge
Maintain this server? Add the live badge to your README.