Epic Fhir MCP Server for Claude Desktop 10 tools — connect in under 2 minutes
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Epic Fhir and 2,500+ MCP Servers from a single visual interface.




{
"mcpServers": {
"epic-fhir": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Epic Fhir MCP Server
Connect Epic electronic health records to any AI agent and query clinical data through natural conversation instead of navigating complex EHR interfaces.
Claude Desktop is the definitive way to connect Epic Fhir to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Patient Search — Find patients by name, date of birth, or medical record number across your Epic system
- Clinical Encounters — Review admissions, ER visits, and outpatient appointments with dates, reasons, and locations
- Lab Results & Vitals — Pull observations including blood work, vital signs, and social history with reference ranges
- Diagnoses & Conditions — List active and resolved conditions with ICD-10 codes, onset dates, and severity
- Medications & Allergies — View current prescriptions, dosage instructions, and documented allergic reactions
- Appointments & Immunizations — Check upcoming schedules and full vaccination history with lot numbers
The Epic Fhir MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Epic Fhir to Claude Desktop via MCP
Follow these steps to integrate the Epic Fhir MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using Epic Fhir
Look for the 🔌 icon in the chat. your 10 tools are now available
Why Use Claude Desktop with the Epic Fhir MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Epic Fhir through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Epic Fhir + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Epic Fhir MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Epic Fhir MCP Tools for Claude Desktop (10)
These 10 tools become available when you connect Epic Fhir to Claude Desktop via MCP:
get_patient
Returns name, DOB, gender, race, ethnicity, address, phone, email, and all identifiers. Get patient details by ID
list_allergies
Includes substance, reaction type, severity, and clinical status. List allergies and intolerances
list_appointments
Includes date/time, provider, location, and status. List patient appointments
list_conditions
Includes ICD-10 codes, clinical status, verification status, onset date, and severity. List diagnoses and conditions
list_diagnostic_reports
Includes report type, results, conclusion, and performing organization. List diagnostic reports
list_encounters
Includes encounter type, period, reason, and location. List patient encounters/visits
list_immunizations
Includes vaccine type (CVX code), administration date, dose, site, and lot number. List immunizations
list_medications
Includes medication name, dosage, frequency, route, prescriber, and status. List medication requests
list_observations
Filter by category: vital-signs, laboratory, social-history. Includes values, units, reference ranges, and interpretation. List clinical observations
search_patients
Returns patient demographics including name, DOB, gender, address, and identifiers. Search patients by name, DOB, or MRN
Example Prompts for Epic Fhir in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with Epic Fhir immediately.
"Find all patients named Smith born in 1985."
"Show me the latest lab results for patient e63wACU8F."
"List all active medications for this patient."
Troubleshooting Epic Fhir MCP Server with Claude Desktop
Common issues when connecting Epic Fhir to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Epic Fhir + Claude Desktop FAQ
Common questions about integrating Epic Fhir MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect Epic Fhir with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Epic Fhir to Claude Desktop
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.
