Health Record MCP Server

MCP server using SMART on FHIR (Public Client) via Bun to search/query patient EHR data.

Remote serverstreamable-http

What is the Health Record MCP Server?

Health Record MCP lets Claude, Cursor and other MCP clients work with Health Record MCP directly. MCP server using SMART on FHIR (Public Client) via Bun to search/query patient EHR data.

What Health Record MCP does

This project acts as a specialized server providing tools for Large Language Models (LLMs) and other AI agents to interact with Electronic Health Records (EHRs). It leverages the SMART on FHIR standard for secure data access and the Model Context Protocol (MCP) to expose the tools.

Practical notes

  • Maintained by jmandel.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
grep_recordPerforms text or regular expression searches across *all* parts of the fetched record (structured FHIR data + text from notes/attachments). Ideal for finding keywords or specific mentions (e.g., "diabetes", "aspirin").
query_recordExecutes read-only SQL SELECT queries directly against the structured FHIR data. Useful for precise lookups based on known FHIR resource structures (e.g., finding specific lab results by LOINC code).
eval_recordExecutes custom JavaScript code directly on the fetched data (FHIR resources + attachments). Offers maximum flexibility for complex calculations, combining data from multiple sources, or custom formatting.

Example prompts to try

  • “Use Health Record MCP to grep record.”
  • “Use Health Record MCP to query record.”
  • “Use Health Record MCP to eval record.”

Frequently asked questions

MCP server using SMART on FHIR (Public Client) via Bun to search/query patient EHR data. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.