Langcare MCP Fhir logo

Langcare MCP Fhir

Proxies AI agent requests to FHIR R4 EMR systems through four generic MCP operations.

Install Langcare MCP Fhir

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "langcare-mcp-fhir": {
      "command": "npx",
      "args": [
        "-y",
        "@langcare/langcare-mcp-fhir"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @langcare/langcare-mcp-fhir

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 14d ago.

Overview

The langcare-mcp-fhir MCP server connects MCP clients to FHIR R4 backends, including Epic, Cerner, OpenEMR, and GCP Healthcare API. Written in Go, it proxies requests without storing data in a database and supports stdio and Streamable HTTP transports. Its four generic tools read, search, create, and update any FHIR R4 resource type. Reach for it when an agent needs controlled access to an existing FHIR-based EMR.

Use cases

  • Connect an AI client to an Epic FHIR endpoint
  • Search patient and clinical resources with FHIR parameters
  • Create observations through an MCP tool
  • Update existing FHIR resources from an agent workflow

Key features

  • Generic read, search, create, and update tools
  • FHIR R4 backend proxy
  • Epic, Cerner, OpenEMR, and GCP Healthcare API support
  • Stdio and Streamable HTTP transports
  • OAuth2, SMART on FHIR, bearer, and Basic Auth options
  • PHI log scrubbing and audit logging

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

14/14 checks healthy over the last 52d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @langcare/langcare-mcp-fhir (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars70Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Langcare MCP Fhir works

What langcare-mcp-fhir MCP server does

The langcare-mcp-fhir MCP server exposes an existing FHIR R4 API to MCP-compatible AI clients. It is intended for EMR environments such as Epic, Cerner, OpenEMR, and the GCP Healthcare API, while also supporting generic FHIR R4 servers.

Rather than maintaining its own clinical database, the server acts as a proxy. Agent requests are translated into FHIR API calls, and responses are returned through MCP. The implementation is written in Go and uses the official Go MCP SDK.

The core interface is resource-agnostic. The same operations can work with resources such as Patient, Observation, or Medication, provided the connected FHIR backend supports the requested operation.

How it works

The langcare-mcp-fhir MCP server accepts MCP requests over stdio or Streamable HTTP and forwards them to the configured FHIR service. A YAML configuration file identifies the backend and its connection settings. Claude Desktop can start the process with a command and a -config argument.

Four generic tools form the primary API:

  • fhir_read retrieves a resource using its type and ID.
  • fhir_search searches a resource type with FHIR query parameters.
  • fhir_create submits a new resource to the backend.
  • fhir_update updates an existing resource by type and ID.

The security model separates authentication between the MCP client and the FHIR backend. Documented backend and client options include bearer tokens, OAuth 2.0 with token refresh, SMART on FHIR backend services using private_key_jwt, SMART on FHIR, Basic Auth, and extensible custom methods.

Setup and configuration

Install the package globally with npm:

Terminal
npm install -g @langcare/langcare-mcp-fhir

Alternatively, run it without a global installation:

Terminal
npx @langcare/langcare-mcp-fhir -config /path/to/config.yaml

Choose a configuration template for Epic, Cerner, OpenEMR, GCP Healthcare API, or a generic FHIR R4 service. Then add the executable and configuration path to the MCP client's server configuration. The documented Claude Desktop setup uses the langcare-mcp-fhir command and passes -config followed by the YAML file path. Credentials are intended to come from environment variables rather than configuration files.

Tools and capabilities

In addition to the four core FHIR tools, the distribution includes optional clinical workflow material and interactive MCP Apps. These apps provide browser-like resource views and clinical dashboard displays inside MCP-capable hosts such as Claude Desktop, using the same FHIR operations for data access.

Limitations and notes

The server does not provide its own persistent clinical data store; it depends on an accessible and correctly configured FHIR R4 backend. Supported operations are limited to the documented read, search, create, and update tools. Backend permissions, authentication, resource support, and FHIR behavior remain responsibilities of the connected EMR or FHIR service.

The langcare-mcp-fhir MCP server is described as stateless and as avoiding persistent PHI storage, but deployments still need appropriate credential management, access controls, and healthcare compliance review. Consult the project’s security and local testing documentation before connecting it to production data.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Langcare MCP Fhir

langcare-mcp-fhir is an MCP server that connects AI clients to FHIR R4 EMR systems such as Epic, Cerner, OpenEMR, and GCP Healthcare API. Its main tools read, search, create, and update any supported FHIR resource through a configured backend.

Install it with `npm install -g @langcare/langcare-mcp-fhir`, or run it directly with `npx @langcare/langcare-mcp-fhir -config /path/to/config.yaml`. You also need a YAML configuration file for the target FHIR backend.

Add the server command and YAML path to Claude Desktop’s `mcpServers` configuration, then restart Claude Desktop. The documented entry uses `command: "langcare-mcp-fhir"` and passes `-config` with your configuration file.

It supports four generic operations: `fhir_read`, `fhir_search`, `fhir_create`, and `fhir_update`. They operate on FHIR R4 resource types such as Patient, Observation, and Medication.

Yes, it provides configuration templates and authentication support for Epic and Cerner FHIR-based EMR systems. It also supports OpenEMR, GCP Healthcare API, and generic FHIR R4 servers.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLangcare MCP Fhir AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/langcare-mcp-fhir?style=directory)](https://allmcps.com/mcp/langcare-mcp-fhir)
HTML Embed
<a href="https://allmcps.com/mcp/langcare-mcp-fhir"><img src="https://allmcps.com/api/badge/langcare-mcp-fhir?style=directory" alt="Langcare MCP Fhir on AllMCPs" /></a>