LABSCO SUMMARY

One tool, and what it gives you is the query language rather than a menu of canned lookups.

search_fhir takes the resource type and a parameter set, which puts modifiers, prefixes, chained parameters and result management within reach without a FHIR client library in the loop. Answers come back as paginated searchset bundles, so a wide query returns a page rather than everything at once. It reads and only reads: search_fhir is the entire surface, so nothing here creates, updates or deletes a resource.

What it is

A single search tool over an Azure FHIR service, taking a resource type and the set of search parameters to apply to it.

What you get

Searches by resource-specific and common parameters, including _id, _lastUpdated and _tag, with prefixes for ranges and comparisons
Search modifiers such as :missing, :exact, :contains and :text
Chained searches, so a query can follow a reference to another resource
Results returned paginated, in FHIR searchset bundles

Requirements

An Azure FHIR endpoint in fhirUrl, and the application credentials allowed to read it: clientId, clientSecret and tenantId.

Setup effort

One command plus credentials — uvx azure-fhir-mcp-server, then supply credentials

See installation options

USE CASES

01

Answering a question against the FHIR store without writing a client first

Name the resource type, pass the search parameters with whatever modifiers the question needs, and read the searchset bundle that comes back.

search_fhir

02

Sweeping for records that changed since the last run

Filter on _lastUpdated with a prefix for the comparison, and page through the bundle until the cursor runs out.

search_fhir

1 tool

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`search_fhir`

Search FHIR resources using comprehensive Azure FHIR search capabilities.

Supports resource-specific and common search parameters, modifiers, prefixes, chained searches, and result management. Returns paginated results in FHIR searchset bundles.

Key Features:

Resource-specific and common search parameters (_id, _lastUpdated, _tag, etc.)
Search modifiers (:missing, :exact, :contains, :text, :not, etc.)
Prefixes for ordered parameters (gt, lt, ge, le, etc.)
Chained searches (e.g., Encounter?subject:Patient.name=Jane)
Reverse chained searches using _has parameter
Include and revinclude searches (_include, _revinclude)
Result parameters (_count, _sort, _elements, _summary, _total)
Composite search parameters for complex queries
Pagination support with configurable page sizes (max 1000)

Args: resource_type: FHIR resource type to search (e.g., 'Patient', 'Observation', 'Condition') search_params: Dictionary of FHIR search parameters. Common examples:

{"name": "Smith", "_count": 50} - Search patients by name, limit 50 results
{"birthdate": "gt1990-01-01", "_sort": "birthdate"} - Patients born after 1990, sorted
{"identifier": "12345", "_include": "Patient:general-practitioner"} - Include GP
{"code": "77386006", "_include": "Observation:subject"} - Pregnancy observations with patients
{"_lastUpdated": "gt2024-01-01"} - Resources updated after date ctx: MCP Context for logging and progress reporting

Returns: List of matching FHIR resources extracted from searchset Bundle

BEFORE YOU INSTALL

What to know first

Tools you get

1 tool when we connected.

Requires

uvx on PATH
Python 3.13 or later
fhirUrl in your environment
clientId in your environment
clientSecret in your environment
tenantId in your environment

CONTEXT COST

Light Standing cost

Rated by the size of the one tool definition that rides along on every turn

INSTALLATION

Connect your client

Add the block to your client, or run the command directly.

Server setup

Configuration file

JSON

{
  "mcpServers": {
    "fhir": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "azure-fhir-mcp-server"
      ],
      "env": {
        "fhirUrl": "https://<YOUR_FHIR_SERVER>.azurehealthcareapis.com/fhir",
        "clientId": "<YOUR_CLIENT_ID>",
        "clientSecret": "<YOUR_CLIENT_SECRET>",
        "tenantId": "<YOUR_TENANT_ID>"
      }
    }
  }
}

The four env values: fhirUrl is your Azure Health Data Services FHIR base URL (include /fhir); clientId, clientSecret and tenantId come from an Azure app registration (Microsoft Entra ID → App registrations) with a client secret, allowed to read that FHIR service.

uvx

TERMINAL

uvx azure-fhir-mcp-server

Azure AHDS FHIR MCP Server