Azure FHIR▌

by erikhoward
Azure FHIR offers secure, authenticated access to Azure Health Data Services FHIR servers for standards-compliant health
Provides secure access to Azure Health Data Services FHIR servers, enabling authenticated retrieval and search of healthcare resources across 70+ resource types for medical applications requiring standards-compliant patient data access.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Healthcare developers building medical applications
- / Clinical data integration projects
- / Medical research requiring patient data access
- / Healthcare analytics and reporting systems
capabilities
- / Query FHIR healthcare resources
- / Search across 70+ medical data types
- / Authenticate via Azure AD credentials
- / Retrieve patient records securely
- / Access standardized healthcare data
- / Integrate with Azure Health Services
what it does
Connects to Azure Health Data Services FHIR servers to retrieve and search healthcare data across 70+ standardized resource types. Uses Azure AD authentication for secure access to patient records and medical information.
about
Azure FHIR is a community-built MCP server published by erikhoward that provides AI assistants with tools and capabilities via the Model Context Protocol. Azure FHIR offers secure, authenticated access to Azure Health Data Services FHIR servers for standards-compliant health It is categorized under cloud infrastructure, developer tools.
how to install
You can install Azure FHIR in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Azure FHIR is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
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=false - Keep
HTTP_TRANSPORT=falseto use stdio transport - Uses Azure AD client credentials flow
{
"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.
- 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=true - Requires
HTTP_TRANSPORT=true
- Set
-
Start the MCP server with:
uv pip install -e .
uv run --env-file .env azure-fhir-mcp-server
- Update mcp.json:
{
"mcpServers": {
"fhir": {
"type": "http",
"url": "http://localhost:9002/mcp"
}
}
}
The following is a table of available environment configuration variables:
| Variable | Description | Default | Required |
|---|---|---|---|
fhirUrl | Azure FHIR server base URL (include /fhir) | - | Yes |
clientId | Azure App registration client ID | - | Yes |
clientSecret | Azure App registration client secret | - | Yes |
tenantId | Azure AD tenant ID | - | Yes |
USE_FAST_MCP_OAUTH_PROXY | Enable FastMCP Azure OAuth proxy integration | false | No |
HTTP_TRANSPORT | Run the MCP server over HTTP transport (required for OAuth proxy) | false | No |
FASTMCP_HTTP_PORT | Port exposed when HTTP_TRANSPORT=true | 9002 | No |
FHIR_SCOPE | Override FHIR audience scope for the OBO flow (space-separated) | {fhirUrl}/.default | No |
FASTMCP_SERVER_AUTH_AZURE_BASE_URL | Public base URL of your FastMCP server | http://localhost:9002 | No |
FASTMCP_SERVER_AUTH_AZURE_REDIRECT_PATH | OAuth callback path appended to the base URL | /auth/callback | No |
FASTMCP_SERVER_AUTH_AZURE_IDENTIFIER_URI | Azure App registration Application ID URI | api://{clientId} | No |
FASTMCP_SERVER_AUTH_AZURE_REQUIRED_SCOPES | Space-separated scopes requested by the Azure provider | user_impersonation | No |
FASTMCP_SERVER_AUTH_AZURE_ADDITIONAL_AUTHORIZE_SCOPES | Optional space-separated scopes added to the authorize request | - | No |
LOG_LEVEL | Logging level | INFO | 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 resource- And many more...
Development 💻
Local Development Setup
1 - Clone the repository:
git clone https://github.com/erikhoward/azure-fhir-mcp-server.git
cd azure-fhir-mcp-server
2 - Create and activate virtual environment:
Linux/macOS:
python -m venv .venv
source .venv/bin/activate
Windows:
python -m venv .venv
.venv\Scripts\activate
3 - Install dependencies:
pip install -e ".[dev]"
4 - Copy and configure environment variables:
cp .env.example .env
Edit .env with your settings:
fhirUrl=https://your-fhir-server.azurehealthcareapis.com/fhir
clientId=your-client-id
clientSecret=your-client-secret
tenantId=your-tenant-id
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.
{
"mcpServers": {
"fhir": {
"command": "uv",
"args": [
"--directory",
"/path/to/azure-fhir-mcp-server/repo",
"run",
"azure_fhir_mcp_server"
],
"env": {
"LOG_LEVEL": "DEBUG",
"fhirUrl": "https://your-fhir-server.azurehealthcareapis.com/fhir",
"clientId": "your-client-id",
"clientSecret": "your-client-secret",
"tenantId": "your-tenant-id"
}
}
}
}
6 - Restart Claude Desktop.
Running Tests
# Run all tests
python -m pytest tests/ -v
# Run with coverage
pytest tests/ --cov=src/azure_fhir_mcp_server
# Run specific test
pytest tests/test_fastmcp_metadata.py::TestFastMCPMetadata::test_fastmcp_server_discovery -v
# Run with detailed output
pytest tests/test_fastmcp_metadata.py::TestFastMCPMetadata::test_output_detailed_metadata -v -s
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.
FAQ
- What is the Azure FHIR MCP server?
- Azure FHIR is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Azure FHIR?
- This profile displays 49 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★49 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
According to our notes, Azure FHIR benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Ren Diallo· Dec 16, 2024
Strong directory entry: Azure FHIR surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Daniel Bansal· Dec 4, 2024
Azure FHIR has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Anika Wang· Nov 23, 2024
Azure FHIR is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Oshnikdeep· Nov 15, 2024
We wired Azure FHIR into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Kiara Liu· Nov 7, 2024
Useful MCP listing: Azure FHIR is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Kiara Garcia· Oct 26, 2024
Azure FHIR reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★William Khanna· Oct 14, 2024
We wired Azure FHIR into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Ganesh Mohane· Oct 6, 2024
Azure FHIR is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Sakshi Patil· Sep 25, 2024
Useful MCP listing: Azure FHIR is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 49