Practice Fusion MCP connector
Connect Practice Fusion to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up encounters, conditions, allergies, care plans, immunizations and coverages, with each person signed in as themselves and every lookup logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize this week's encounters for Dr. Patel's panel
Working in Practice Fusion with Elaichi
-
Get single Practice Fusion allergy intolerance by ID
-
List all Practice Fusion allergy intolerances
-
Get single Practice Fusion care plan by ID
How to connect Practice Fusion to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Practice Fusion MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Practice Fusion MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
Practice Fusion MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Practice Fusion MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Practice Fusion MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 Practice Fusion to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 Practice Fusion through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Practice Fusion is logged.
-
Clinical
Catch up on a patient before the visit
Pull a patient's conditions, allergy intolerances, immunizations and the last few encounters from Practice Fusion into one short summary before walking into the room.
-
Care coordination
See who is on a patient's care team
Ask which care team members and goals are attached to a patient and which care plans are still open, without clicking through each tab in Practice Fusion.
-
Billing
Check coverage before a claim goes out
Look up a patient's coverage details in Practice Fusion and match them against the encounter being billed so the claim is right the first time.
-
Front desk
Confirm where and when a patient was seen
Find a patient's recent encounters and the location each one happened at when they call to ask about a visit.
-
Quality
Review diagnostic reports across a panel
Ask for the diagnostic reports from a date range and list the results that still have no follow-up encounter in Practice Fusion.
-
Medical records
Produce a continuity of care document
When a patient transfers, generate a CCD from their Practice Fusion document references and hand it to the receiving practice without rebuilding it by hand.
Try asking
- “Summarize this week's encounters for Dr. Patel's panel”
- “List patients with open care plans and no encounter since March”
- “Which immunizations are recorded for patient Maria Lopez?”
What connecting Practice Fusion gets you
6 screens from Elaichi, each doing one job for your Practice Fusion account.
Ask Elaichi to work across your apps.
Summarize this week's encounters for Dr. Patel's panel
List patients with open care plans and no encounter since March
Which immunizations are recorded for patient Maria Lopez?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any patient's chart in plain language.
Allergies, conditions, encounters and care plans, answered from live Practice Fusion records.
Copy the endpoint
AI apps
Practice Fusion in every MCP client, connected once.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared key.
Tool catalog
48 Practice Fusion tools, no custom code needed.
Encounters, conditions, immunizations, coverages and diagnostic reports, ready to call the day you connect.
Toolboxes
Each team gets its own Practice Fusion toolbox.
Clinical staff see care plans, billing sees coverages, each scoped to what their work needs.
Shared connections
Share a Practice Fusion connection, never a credential.
One person connects, teams and members work through it, and nobody else handles a secret.
Audit log
Every Practice Fusion call is logged by name.
When, who, what happened, and which encounter or report was read, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Practice Fusion digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch encounters
Practice Fusion
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Practice Fusion
Queued
Workflows
A schedule starts the work, a person approves.
A schedule pulls the week's encounters, groups them, drafts a digest, and a person approves.
Practice Fusion health
Refreshed 4 minutes ago · every 15 minutes · from the encounters collection
Encounters
1,284 ↓ 12%
Conditions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Encounters created
Last 14 days
By team
Share of activity
Main clinic 34%
Downtown clinic 27%
Billing 21%
Care coordination 18%
Collections and dashboards
Practice Fusion numbers computed with no model involved.
Encounters, diagnostic reports and immunizations over fourteen days, by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Practice Fusion
All three can connect Practice Fusion to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Practice Fusion tools | Allow or restrict single Practice Fusion 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 Practice Fusion 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.
Practice Fusion tools for your AI agents
48 tools are ready to call through Elaichi's MCP endpoint the moment you connect Practice Fusion, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Practice Fusion to Claude?
Connect Practice Fusion in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Practice Fusion requires an OAuth application registered inside Practice Fusion itself, so one person brings its client ID and secret into Elaichi once and signs in through the Practice Fusion sign-in screen. After that nobody else on the team has to generate a client ID or secret, they just sign in as themselves.
Does Practice Fusion work with ChatGPT and Cursor as well as Claude?
Yes. Once Practice Fusion 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 Practice Fusion once and every client picks it up.
What can an AI agent actually do with my Practice Fusion data?
An agent connected to Practice Fusion can look up a patient's conditions, allergy intolerances, immunizations, care plans, care teams, goals, coverages, devices, encounters, diagnostic reports and locations, and it can generate a continuity of care document from a patient's document references. In practice that means asking for a pre-visit summary, a coverage check or a list of reports from last week and getting an answer from the live chart. Short, concrete asks such as a patient name and a date range work better than long sentences.
Does connecting Practice Fusion give the AI access to every patient?
No. Every call into Practice Fusion runs under the account of the person who signed in, so an agent can only see the patients, encounters and reports that person can already see in Practice Fusion. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Practice Fusion already allows.
Can I stop an agent from deleting or changing things in Practice Fusion?
This Practice Fusion connector reads records and generates care documents, it does not edit or delete charts. Even so, you can restrict any individual action, such as generating a CCD or listing coverages, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it against Practice Fusion no matter what the prompt says.
What happens to a Practice Fusion connection when someone leaves?
Offboarding a person in Elaichi ends their access to Practice Fusion through every client at once. If they were using a shared Practice Fusion connection, it keeps working for everyone else on the team. If you want Practice Fusion gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Practice Fusion MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Practice Fusion 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 Practice Fusion?
Yes. Both let Claude, ChatGPT or Cursor use Practice Fusion. 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 Practice Fusion call.
How is Elaichi different from Composio for Practice Fusion?
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 Practice Fusion: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Practice Fusion 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