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 — uvx azure-fhir-mcp-server