The Azure AHDS FHIR MCP Server provides a Model Context Protocol (MCP) interface for interacting with Azure FHIR servers to perform healthcare data operations:
Search FHIR Resources: Perform searches on FHIR resources using specific search parameters via the
search_fhirtoolAccess Resource Collections: Retrieve collections of standard FHIR resources (Patient, Observation, Medication) via MCP resource protocol (e.g.,
fhir://Patient/)Access Specific Resources: Retrieve specific FHIR resources by ID (e.g.,
fhir://Observation/{id})Secure Authentication: Utilize OAuth2 for secure access with client ID, client secret, and tenant ID
Developer-Friendly: Supports local development environments with customizable logging levels
Allows loading configuration from .env files for development environments, supporting variables like fhirUrl, clientId, clientSecret, and tenantId.
Enables contributions through GitHub's pull request workflow, with specific guidance on forking and submitting changes.
Supports development setup with Linux-specific virtual environment creation commands.
Provides specific installation paths and configuration guidance for running on macOS systems.
Built on Python 3.13+, offering a Pythonic implementation of the MCP server for Azure FHIR integration.
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.
Setup 🛠️
Installation 📦
Requires Python 3.13 or higher and uv.
Install uv first.
Configuration ⚙️
See the FastMCP guidance on mcp.json here: https://gofastmcp.com/integrations/mcp-json-configuration
Client Credentials Flow (default):
Used for service-to-service authentication
Leave
USE_FAST_MCP_OAUTH_PROXY=falseKeep
HTTP_TRANSPORT=falseto use stdio transportUses Azure AD client credentials flow
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.
In the Azure portal, go to Microsoft Entra ID ➜ App registrations ➜ New registration. Give it a descriptive name such as
FHIR-MCP-Server, set Supported account types to Single tenant, and leave the redirect URI unset for now.After the app is created, capture the generated
Application (client) IDandDirectory (tenant) IDfor later use.Under Expose an API, select Set for the Application ID URI and accept the suggested value
api://{appId}. Add a scope nameduser_impersonationwith admin consent display/description also set touser_impersonation.Under Certificates & secrets, create a New client secret (for example
FHIR-MCP-Secret-New). Copy the secret value immediately; it is required for the MCP serverclientSecretsetting.Under Authentication, add the following Web redirect URIs to support the FastMCP OAuth proxy:
http://localhost:9002/auth/callbackEnsure Default client type remains No so the app stays confidential.
Under API permissions, choose Add a permission ➜ APIs my organization uses, search for your Azure Health Data Services FHIR server, and add the delegated scopes required for your scenario. Grant admin consent so the FastMCP proxy can request tokens without an interactive prompt.
Environment variables:
Set
USE_FAST_MCP_OAUTH_PROXY=trueRequires
HTTP_TRANSPORT=true
Start the MCP server with:
Update mcp.json:
The following is a table of available environment configuration variables:
Variable | Description | Default | Required |
| Azure FHIR server base URL (include
) | - | Yes |
| Azure App registration client ID | - | Yes |
| Azure App registration client secret | - | Yes |
| Azure AD tenant ID | - | Yes |
| Enable FastMCP Azure OAuth proxy integration |
| No |
| Run the MCP server over HTTP transport (required for OAuth proxy) |
| No |
| Port exposed when
|
| No |
| Override FHIR audience scope for the OBO flow (space-separated) |
| No |
| Public base URL of your FastMCP server |
| No |
| OAuth callback path appended to the base URL |
| No |
| Azure App registration Application ID URI |
| No |
| Space-separated scopes requested by the Azure provider |
| No |
| Optional space-separated scopes added to the authorize request | - | No |
| Logging level |
| No |
Available Tools 🔧
FHIR Resource Operations
search_fhir- Search for FHIR resources based on a dictionary of search parametersget_user_info- (OAuth only) Returns information about the authenticated Azure user
Resource Access
The server provides access to all standard FHIR resources through the MCP resource protocol:
fhir://Patient/- Access all Patient resourcesfhir://Patient/{id}- Access a specific Patient resourcefhir://Observation/- Access all Observation resourcesfhir://Observation/{id}- Access a specific Observation resourcefhir://Medication/- Access all Medication resourcesfhir://Medication/{id}- Access a specific Medication resourceAnd many more...
Related MCP server: HAPI-MCP
Development 💻
Local Development Setup
1 - Clone the repository:
2 - Create and activate virtual environment:
Linux/macOS:
Windows:
3 - Install dependencies:
4 - Copy and configure environment variables:
Edit .env with your settings:
5 - Claude Desktop Configuration
Open claude_desktop_config.json and add the following configuration.
On MacOs, the file is located here: ~/Library/Application Support/Claude Desktop/claude_desktop_config.json.
On Windows, the file is located here: %APPDATA%\Claude Desktop\claude_desktop_config.json.
6 - Restart Claude Desktop.
Running Tests
Contributions 🤝
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/AmazingFeature)Commit your changes (
git commit -m '✨ Add some AmazingFeature')Push to the branch (
git push origin feature/AmazingFeature)Open a Pull Request
License ⚖️
Licensed under MIT - see LICENSE.md file.
This is not an official Microsoft or Azure product.