Health Record MCP Server

Health record mcp mcp server 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.

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

• grep_record — Performs text or regular expression searches across all parts of the fetched record (structured FHIR data + text from notes/attachments). Ideal for finding
• query_record — Executes read-only SQL SELECT queries directly against the structured FHIR data. Useful for precise lookups based on known FHIR resource structures (e.g
• eval_record — Executes custom JavaScript code directly on the fetched data (FHIR resources + attachments). Offers maximum flexibility for complex calculations, combining

Installing the health record mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Health Record MCP sits in that group, and the shape of its toolset — grep_record, query_record, eval_record — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• Maintained by jmandel.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the health record mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.