2,500+ MCP servers ready to use
Vinkius

Epic Fhir MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "epic-fhir": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Epic Fhir
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

GitHub Copilot Agent mode brings Epic Fhir data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Epic Fhir MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Epic Fhir

Ask Copilot: "Using Epic Fhir, help me...". 10 tools available

Why Use VS Code Copilot with the Epic Fhir MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Epic Fhir through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Epic Fhir + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Epic Fhir MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Epic Fhir MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Epic Fhir to VS Code Copilot via MCP:

01

get_patient

Returns name, DOB, gender, race, ethnicity, address, phone, email, and all identifiers. Get patient details by ID

02

list_allergies

Includes substance, reaction type, severity, and clinical status. List allergies and intolerances

03

list_appointments

Includes date/time, provider, location, and status. List patient appointments

04

list_conditions

Includes ICD-10 codes, clinical status, verification status, onset date, and severity. List diagnoses and conditions

05

list_diagnostic_reports

Includes report type, results, conclusion, and performing organization. List diagnostic reports

06

list_encounters

Includes encounter type, period, reason, and location. List patient encounters/visits

07

list_immunizations

Includes vaccine type (CVX code), administration date, dose, site, and lot number. List immunizations

08

list_medications

Includes medication name, dosage, frequency, route, prescriber, and status. List medication requests

09

list_observations

Filter by category: vital-signs, laboratory, social-history. Includes values, units, reference ranges, and interpretation. List clinical observations

10

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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Epic Fhir immediately.

01

"Find all patients named Smith born in 1985."

02

"Show me the latest lab results for patient e63wACU8F."

03

"List all active medications for this patient."

Troubleshooting Epic Fhir MCP Server with VS Code Copilot

Common issues when connecting Epic Fhir to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Epic Fhir + VS Code Copilot FAQ

Common questions about integrating Epic Fhir MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Epic Fhir to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.