Connector guide3-minute read11 MCP tools7 languages

How to Connect FHIR R4 to Cursor — via MCP

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

HCBy HelpCode teamUpdated 3 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

FHIR R4

FHIR R4

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

tools

11

Region

INTL

Category

Healthcare

Authentication

Bearer Token

Required env vars

FHIR_BASE_URLFHIR_ACCESS_TOKEN
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Skip the install. Get this working in under 2 minutes.

Start a free trial on cloud.anythingmcp.com, add the FHIR R4 in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.

Start free trial

Summary

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Try asking

Example prompts for FHIR R4

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

FHIR R4 · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → FHIR R4, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

FHIR R4 + Cursor

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

FHIR_BASE_URL, FHIR_ACCESS_TOKEN

Step 1 — Get credentials

This is a generic FHIR R4 client, not a vendor connector. Point it at any R4 server — a hospital's HAPI instance, a national test server, a vendor's sandbox — and it speaks the standard.

  1. Set FHIR_BASE_URL to the server's base, the URL that answers /metadata. No trailing slash.
  2. Set FHIR_ACCESS_TOKEN to a bearer token. Most real deployments use SMART on FHIR, whose authorisation flow issues short-lived tokens; obtain one and paste it here, or use a long-lived service token if the server offers one. A server that needs no auth still needs a placeholder here — put anything.

…(continued in the in-app connector instructions)

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Cursor

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}
  1. Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
  2. Save the file and restart Cursor.
  3. Open Cursor → Settings → MCP to verify FHIR R4 is listed and "Connected".
  4. Start chatting — all FHIR R4 tools are now invokable.

Available tools

ToolWhat it does
fhir_get_capability_statementRead the server's CapabilityStatement: which resource types it holds, which interactions and search parameters each supports, and its FHIR v
fhir_searchSearch any resource type with FHIR's standard parameters
fhir_read_resourceRead one resource instance by type and id, returning the full resource rather than a Bundle entry
fhir_search_patientsSearch Patients by name, identifier, birth date or family name
fhir_get_patient_observationsRead the Observations recorded for one patient — vital signs, laboratory results, measurements — optionally narrowed to one LOINC code or ca
fhir_get_patient_conditionsRead the Conditions recorded for one patient — the problem list — with their clinical and verification status
fhir_get_patient_encountersRead the Encounters for one patient — admissions, visits and consultations — with their class, period and the practitioners involved
fhir_get_patient_medicationsRead the MedicationRequests for one patient — what has been prescribed, in what dosage, by whom and with what status
fhir_get_patient_reportsRead the DiagnosticReports for one patient — laboratory panels, imaging reports and pathology — with their category, status and conclusions
fhir_get_patient_everythingRun the $everything operation on one patient: every resource the server associates with them, in one Bundle
fhir_next_pageFetch the next page of a search result

FAQ

Does Cursor support custom MCP servers on the free tier? Yes — MCP is available on Hobby, Pro and Business plans.

Next steps

Was this guide helpful?

Your FHIR R4 agent is one click away.

Install the connector, paste the key, prompt Cursor. Free for 7 days, no credit card.

Related guides

Connectors

How to Connect FHIR R4 to Meta Muse — via MCP

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Connectors

How to Connect FHIR R4 to ChatGPT — via MCP

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Connectors

How to Connect FHIR R4 to Claude — via MCP

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Connectors

How to Connect FHIR R4 to Gemini — via MCP

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Connectors

FHIR R4 to MCP — Drive FHIR R4 from any AI Agent

Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.

Connectors

How to Connect Baserow to Cursor — via MCP

Read Baserow tables, fields, and rows from Baserow Cloud or a self-hosted instance. 4 generic read-only tools using database-token authentication.