Skip to content

Metriport MCP connector

The Metriport connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent register patients, request medical record summaries, run document queries, and manage facilities and cohorts in Metriport, each person signed in as themselves, every action logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Show Metriport patients added to cohorts this week.

Working in Metriport with Elaichi

  • Get single Metriport patient by ID
  • List all Metriport patients
  • Metriport patients get medical record summary
Ask anything…
Governance / Audit log Last 24 hours
Metriport Metriport patients get medical record summary Emily Carter · ChatGPT · 9:41 AM Done
Metriport List all Metriport patients Emily Carter · ChatGPT · 9:41 AM Done
Metriport Get single Metriport patient by ID Emily Carter · ChatGPT · 9:41 AM Done
Metriport Create a Metriport patient Megan Brooks · Claude · 9:38 AM Done
Metriport Update a Metriport patient by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Metriport to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Metriport MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Metriport MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Metriport MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Metriport MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Metriport MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Metriport to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Metriport through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Metriport is logged.

  • Intake

    Register a new patient before their visit

    Add a patient to Metriport with their demographics and the facility they are being seen at, so their outside records can start being gathered before they arrive.

  • Care coordination

    Pull a medical record summary for a referral

    Ask for a patient's consolidated medical record summary in Metriport and check whether it is ready, so the referring notes, medications, and history are in hand before the appointment.

  • Clinical operations

    Check on a record query that is still running

    Start a document query for a patient and ask how far along it is, instead of refreshing a dashboard while a clinician waits.

  • Health information management

    Find the right patient and avoid duplicates

    Match a person against existing Metriport patients, look them up by the ID from your own system, and fix demographics on the record without creating a second one.

  • Population health

    Group patients into a cohort for outreach

    Add a list of patients to a cohort in Metriport, see which cohorts a patient already belongs to, and keep treatment relationships current as a panel changes.

  • Practice administration

    Keep facilities and rosters up to date

    Add a new clinic location, update its details, and bulk create or update patients when a practice or a batch of new patients joins.

Try asking

  • “Show Metriport patients added to cohorts this week.”
  • “Get the medical record summary for patient 4821.”
  • “Which facilities are set on our newest Metriport patients?”

See all 61 Metriport tools →

What connecting Metriport gets you

6 screens from Elaichi, each doing one job for your Metriport account.

Elaichi Agent

Ask Elaichi to work across your apps.

Show Metriport patients added to cohorts this week.

Get the medical record summary for patient 4821.

Which facilities are set on our newest Metriport patients?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about patients and read the answer.

Plain language questions return live Metriport patients, cohorts and facilities.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.

Every client reaches Metriport over OAuth, with no SDK and no shared key.

ElaichiTools
Tool Action Description
Create a Metriport patient Create Create a new patient in Metriport for a specified facility where the patient is receiving care. Returns the created patient object including id, firstName, lastName, dob, genderAtBirth, address, personalIdentifiers, and facilityIds. Required: facilityId, firstName, lastName, dob, genderAtBirth, address.
Get single Metriport patient by ID Get Get a single Metriport patient by id. Returns: id, eTag, firstName, lastName, dob, genderAtBirth, address, personalIdentifiers, and facilityIds. Required: id.
Update a Metriport patient by ID Update Update a Metriport patient's demographics, personal identifiers, address, contact info, and consent status. Returns the updated patient object including id, eTag, firstName, lastName, dob, genderAtBirth, address, personalIdentifiers, and facilityIds. Required: id, facilityId.
List all Metriport patients List List Patients in Metriport, optionally filtered by the Facility where they receive care. Returns: id, firstName, lastName, dob, genderAtBirth, address, personalIdentifiers, facilityIds, eTag. All Patients are returned when no facility is specified.
Delete a Metriport patient by ID Delete Delete a Metriport patient by id. Returns an empty 204 response on success. Required: id.

Tool catalog

61 Metriport tools arrive ready to call.

Patient, cohort and facility methods are listed and callable without custom code.

ElaichiToolboxes
Name Source template Tools Created

Care coordination toolbox

Metriport · patients and treatment relationships

Metriport starter 18 Mar 4, 2026

Clinical records toolbox

Metriport · medical record summaries

— 9 Mar 2, 2026

Patient intake toolbox

Metriport · patient creation and matching

— 24 Feb 27, 2026

Population health toolbox

Metriport · cohorts and bulk imports

Metriport starter 6 Feb 19, 2026

Network operations toolbox

Metriport · facilities and assignments

— 31 Jan 30, 2026

Compliance toolbox

Metriport · patient access review

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Metriport toolbox.

Curate one toolbox per team so each sees only relevant Metriport tools.

ElaichiConnections
Connection Scope Status Access
ME

Metriport (Primary care)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ME

Metriport (Cardiology clinic)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ME

Metriport (Patient intake)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ME

Metriport (Population health)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
ME

Metriport (Records team)

Connected by Ryan Hayes

Personal • Active Not shared
ME

Metriport (Partner network)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Metriport accounts without credentials.

Each connection shows who connected it and which teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Metriport Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Metriport Patients Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Metriport Patients List Toolbox

Audit log

Every Metriport call is written down.

When, who, what happened, type and resource, appended for each patient request.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Metriport digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch patients

    Metriport

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Metriport

    Queued

Automations

A schedule runs the whole patient digest.

Metriport records are fetched, grouped, drafted by an agent, approved, then posted back.

Metriport health

Refreshed 4 minutes ago · every 15 minutes · from the patients collection

Live

Patients

1,284 ↓ 12%

Cohorts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Patients created

Last 14 days

By team

Share of activity

Primary care 34%

Cardiology clinic 27%

Patient intake 21%

Population health 18%

Collections and dashboards

Metriport patient numbers land before anyone asks.

Four metrics, 14 days of records created and a team breakdown, computed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Metriport

All three can connect Metriport to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Metriport, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Metriport tools Allow or restrict single Metriport tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Metriport call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Metriport tools for your AI agents

61 tools are ready to call through Elaichi's MCP endpoint the moment you connect Metriport, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Metriport to Claude?

Connect Metriport in Elaichi first: pick Metriport from the catalog and paste in the API key from your Metriport dashboard, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. That is the whole setup, and there is no client ID or secret to generate. Sign in with your Elaichi account and Claude can start working with Metriport patients, facilities, and record queries.

Does Metriport work with ChatGPT and Cursor as well as Claude?

Yes. Once Metriport is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Metriport once and every client you use picks it up.

What can an AI agent actually do with my Metriport data?

An agent can register a patient in Metriport, match a person against existing patients, update demographics, and request a medical record summary or start a document query and tell you when it is ready. It can also add patients to cohorts, set which facility a patient is seen at, and keep facility details current. Because Metriport exposes a lot of actions, short concrete asks such as "get the record summary status for this patient" work better than long paragraphs.

Does connecting Metriport give the AI access to every patient?

No. Every request to Metriport runs with the access of the person who signed in to Elaichi, so an agent can only reach the patients, facilities, and records that person's Metriport access already allows. Elaichi can narrow that further by restricting single actions or the whole connector, but it can never grant more than the person already has.

Can my team share one Metriport connection?

Yes. One administrator connects Metriport in Elaichi and shares the connection with a team, and nobody else on the team ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who registered a patient or requested a record, not a shared account.

Can I stop an agent from deleting or changing things in Metriport?

Yes. Restrictions in Elaichi work per action, so you can allow reading Metriport patients and record summaries while restricting deleting patients or removing facilities. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.

What happens to a Metriport connection when someone leaves?

Offboarding a person in Elaichi ends their access to Metriport through every client at once, with no keys to rotate on their way out. A shared Metriport connection keeps working for everyone else on the team. If you ever want to remove Metriport entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

Does the Metriport MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Metriport is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Metriport?

Yes. Both let Claude, ChatGPT or Cursor use Metriport. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Metriport call.

How is Elaichi different from Composio for Metriport?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Metriport: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Metriport in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot