Azure Fhir MCP Server
Azure Health Data Services FHIR resources accessed via standardized MCP tools.
Data last scanned today · Reviewed today
Overview
Azure Fhir MCP Server provides a specialized interface for interacting with Azure Health Data Services (AHDS) FHIR instances. It maps healthcare data operations to MCP tools, allowing AI models to interface with clinical information stored within the Azure ecosystem. The server supports authentication via Azure AD using either standard Client Credentials flow for service-to-service communication or the OAuth On-Behalf-Of flow for user impersonation. Installation requires Python 3.13+ and the use of the uv package manager.
Our verdict
This server carries a high-risk rating of 39/100, primarily due to its lack of read-only functionality, meaning every installation inherently possesses full write access to your FHIR resources. Because it is community-maintained rather than official and has not undergone editorial review, users should exercise significant caution. It is suitable for isolated testing environments, but should not be deployed in production or with sensitive production healthcare data until the codebase is independently verified and access controls are better defined.
- Supports secure Azure AD OAuth authentication flows.
- Zero direct dependencies minimizes the supply-chain surface area.
- Licensed under the permissive MIT license.
- Requires full write access with no read-only mode available.
- Project is community-maintained with no official vendor support.
- Limited activity with no updates in nearly 300 days.
Tools
| Tool | Description | Risk |
|---|---|---|
| search_fhir | Search for FHIR resources based on a dictionary of search parameters | low |
| get_user_info | (OAuth only) Returns information about the authenticated Azure user | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the software prerequisites for this server?
This MCP server requires Python 3.13 or higher and the uv package manager.
›Does this server support different authentication methods?
Yes, it supports the Client Credentials flow for service-to-service authentication and the OAuth On-Behalf-Of (OBO) flow for delegated user access.
›How do I switch between standard and OAuth authentication?
Use the USE_FAST_MCP_OAUTH_PROXY environment variable; set it to true for OBO flow or leave it false for Client Credentials flow.
›Is HTTP transport required for all deployments?
No, stdio transport is the default behavior when HTTP_TRANSPORT is set to false. HTTP transport is specifically required when enabling the FastMCP OAuth proxy.
›What information is needed to configure the server connection?
You must provide your Azure FHIR server base URL, Azure App registration client ID, client secret, and your Azure AD tenant ID.
›Which FHIR resources can I access through this server?
The server provides access to all standard FHIR resources using the MCP resource protocol with URIs such as fhir://Patient/{id} and fhir://Observation/{id}.
Badge
Maintain this server? Add the live badge to your README.