MCP server
by erikhoward
Azure FHIR offers secure, authenticated access to Azure Health Data Services FHIR servers for standards-compliant health
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.
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.
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.
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
According to our notes, Azure FHIR benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Azure FHIR surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Azure FHIR has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Azure FHIR is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Azure FHIR into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Azure FHIR is the kind of server we cite when onboarding engineers to host + tool permissions.
Azure FHIR reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Azure FHIR into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Azure FHIR is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Azure FHIR is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 49
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.
Requires Python 3.13 or higher and uv.
Install uv first.
See the FastMCP guidance on mcp.json here: https://gofastmcp.com/integrations/mcp-json-configuration
USE_FAST_MCP_OAUTH_PROXY=falseHTTP_TRANSPORT=false to use stdio transport{
"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"
}
}
}
}
The OAuth on-behalf-of flow requires a confidential Azure AD application that represents the MCP server.
FHIR-MCP-Server, set Supported account types to Single tenant, and leave the redirect URI unset for now.Application (client) ID and Directory (tenant) ID for later use.api://{appId}. Add a scope named user_impersonation with admin consent display/description also set to user_impersonation.FHIR-MCP-Secret-New). Copy the secret value immediately; it is required for the MCP server clientSecret setting.http://localhost:9002/auth/callback
Ensure Default client type remains No so the app stays confidential.Environment variables:
USE_FAST_MCP_OAUTH_PROXY=trueHTTP_TRANSPORT=trueStart the MCP server with:
uv pip install -e .
uv run --env-file .env azure-fhir-mcp-server
{
"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 |
search_fhir - Search for FHIR resources based on a dictionary of search parametersget_user_info - (OAuth only) Returns information about the authenticated Azure userThe 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 resource1 - 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.
# 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 are welcome! Please feel free to submit a Pull Request.
git checkout -b feature/AmazingFeature)git commit -m '✨ Add some AmazingFeature')git push origin feature/AmazingFeature)Licensed under MIT - see LICENSE.md file.
This is not an official Microsoft or Azure product.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.