Azure AHDS FHIR MCP Server
Listed on its own since 2026-09-25. Until then it was part of azure-fhir-mcp-server, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-erikhoward-azure-fhir-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Azure AHDS FHIR MCP Server 🚀 A Model Context Protocol (MCP) server implementation for Azure Health Data Services FHIR (Fast Healthcare Interoperability Resources). This service provides a standardized interface for interacting with Azure FHIR servers, enabling healthcare data operations through MCP tools. [](https://opensource.org/licenses/MIT) [](https://www.python.org/) [](https://github.com/modelcontextprotocol/spec) ## Setup 🛠️ ### Installation 📦 Requires Python 3.13 or higher and `uv`. Install [uv](https://docs.astral.sh/uv/getting-started/installation/) first. ### Configuration ⚙️ See the FastMCP guidance on `mcp.json` here: [https://gofastmcp.com/integrations/mcp-json-configuration](https://gofastmcp.com/integrations/mcp-json-configuration) #### Client Credentials Flow (default): - Used for service-to-service authentication - Leave `USE_FAST_MCP_OAUTH_PROXY=false` - Keep `HTTP_TRANSPORT=false` to use stdio transport - Uses Azure AD client credentials flow ```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" } } } } ``` #### OAuth On-Behalf-Of Flow: ##### Create the Azure App Registration The OAuth on-behalf-of flow requires a confidential Azure AD application that represents the MCP server. 1. In the Azure portal, go to **Microsoft Entra ID ➜ App registrations ➜ New registration**. Give it a descriptive name such as `FHIR-MCP-Serve…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.