Back to MCP Servers
🔌

the-momentum/fhir-mcp-server

MITAPI key required

🐍 🏠 ☁️ - MCP Server that connects AI agents to FHIR servers. One example use case is querying patient history in natural language.

PythonAI & LLMs

Install

npx -y the-momentum-fhir-mcp-server

Required environment variables

MASTER_KEYSet in your MCP config
FHIR_SERVER_CLIENT_SECRETSet in your MCP config
PINECONE_API_KEYSet in your MCP config

claude_desktop_config.json

claude_desktop_config.json
{
  "mcpServers": {
    "the-momentum-fhir-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "the-momentum-fhir-mcp-server"
      ],
      "env": {
        "MASTER_KEY": "<YOUR_MASTER_KEY>",
        "FHIR_SERVER_CLIENT_SECRET": "<YOUR_FHIR_SERVER_CLIENT_SECRET>",
        "PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY>"
      }
    }
  }
}

Add this to your Claude Desktop config file. Find it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

What this does

the-momentum/fhir-mcp-server exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation. That makes it useful when you want Claude to reach into other AI providers and LLM tooling without copy-pasting context every turn.

Requirements

This server needs the following environment variables to be set before it can run:

MASTER_KEY
FHIR_SERVER_CLIENT_SECRET
PINECONE_API_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Common use cases

  • Delegate reasoning to a different model or LLM provider from a Claude session
  • Pull live model documentation, rate limits, or usage data into context
  • Chain Claude with another agent or evaluation pipeline