Canvas Medical MCP connector
The Canvas Medical connector brings appointments, allergy intolerances, care plans, care teams and claims to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person works with the records their own Canvas Medical login already allows.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Canvas Medical to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Canvas Medical once
-
Open Connections, choose Add connection, and pick Canvas Medical.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Canvas Medical app, then approve. Canvas Medical needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Canvas Medical 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.
Canvas Medical 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 today. The plugin directory lives at chatgpt.com/plugins.
Canvas Medical 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.
Connect Canvas Medical 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.
Use cases
What teams do with Canvas Medical through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Front desk
Book the visit while the patient is on the phone
Find an open slot, create the appointment and confirm it back without leaving the conversation. Reschedules work the same way, by updating the existing appointment rather than starting over.
-
Clinical
Check allergies before the patient walks in
Pull a patient's allergy intolerances and the matching allergens in one ask, so nothing reported at a previous visit gets missed in the room.
-
Nursing
Record a new allergy reported at intake
When a patient mentions a reaction during intake, add the allergy intolerance to Canvas Medical on the spot and correct it later if the details change.
-
Care coordination
Keep the care team current
See who is on a patient's care team, read the care plan they are working from, and update the team when a clinician joins or hands off.
-
Billing
Draft the claim after the encounter
Create the claim for a completed visit, then search for last week's claims that still need a correction and update them in place.
-
Operations
Find every appointment that needs rescheduling
Search appointments for a provider who is out next week, list the affected patients, and move each visit to a new time.
Try asking
- “Which appointments are booked for tomorrow morning?”
- “List Dr. Patel's patients with a penicillin allergy intolerance.”
- “Which claims from last week still need a correction?”
Compare
Elaichi vs Zapier MCP vs Composio for Canvas Medical
All three can connect Canvas Medical 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 Canvas Medical tools | Allow or restrict single Canvas Medical 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 Canvas Medical 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 | $15 per user per month. | 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.
AI tools
Canvas Medical tools for your AI agents
160 tools are ready to call through Elaichi's MCP endpoint the moment you connect Canvas Medical, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Canvas Medical gets you
6 screens from the product, each doing one job for your Canvas Medical account.
The agent
Ask about today's appointments in plain language.
Get answers from live Canvas Medical appointments, allergies and claims without opening a chart.
- appointments
- allergy intolerances
- care plans
- claims
Ask Elaichi to work across your apps.
Which appointments are booked for tomorrow morning?
List Dr. Patel's patients with a penicillin allergy intolerance.
Which claims from last week still need a correction?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Canvas Medical to every client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
160 Canvas Medical tools, no code to write.
Appointments, allergy intolerances, care plans, care teams and claims are covered out of the box.
- Get single Canvas Medical allergen by ID
- List all Canvas Medical allergens
- Get single Canvas Medical allergy intolerance by ID
- List all Canvas Medical allergy intolerances
Toolboxes
Each team gets its own Canvas Medical toolbox.
Front desk, clinical and billing each work from a toolbox scoped to their jobs.
- Front desk
- Clinical
- Nursing
- Care coordination
Shared connections
Teammates work through a connection, never a credential.
One person connects Canvas Medical, shares it, and nobody else sees the secret.
- Front desk
- Clinical
- Billing
- Care coordination
Audit log
Every Canvas Medical call names who made it.
When, who, what happened, and which appointment or claim, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, a person approves.
Appointments are fetched, grouped, drafted into a digest, approved, then posted back to Canvas Medical.
Canvas Medical digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Canvas Medical
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 Michael Brennan
Approve Deny -
Post the digest
Canvas Medical
Queued
Collections and dashboards
Canvas Medical numbers, refreshed on a schedule.
Appointments and claims created over 14 days, broken down by team, with no model involved.
Canvas Medical health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Allergy intolerances
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Front desk 34%
Clinical 27%
Billing 21%
Care coordination 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Canvas Medical to Claude?
Connect Canvas Medical in Elaichi first. Canvas Medical connects over OAuth, but it needs an OAuth application you register inside Canvas Medical yourself, so somebody brings a client ID and secret once and then each person signs in with their own Canvas Medical login. After that, paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add, and Canvas Medical is available in Claude.
Does Canvas Medical work with ChatGPT and Cursor as well as Claude?
Yes. The Canvas Medical connector sits behind the same endpoint, https://api.elaichi.ai/mcp, for Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Canvas Medical once in Elaichi and every client picks it up.
What can an AI agent actually do with my Canvas Medical data?
It can look up and book appointments, read and record a patient's allergy intolerances, review care plans, see and update care teams, and create or correct claims in Canvas Medical. You ask in plain language, such as which appointments are booked for tomorrow morning. Short, concrete asks tend to get better results than long paragraphs.
Does connecting Canvas Medical give the AI access to every patient record?
No. Every call to Canvas Medical runs as the person who signed in, so the AI can only reach the patients, appointments and claims that person could already open in Canvas Medical. Elaichi can narrow that further with roles and restrictions, and it never widens what Canvas Medical itself allows.
Can I stop an agent from deleting or changing things in Canvas Medical?
Yes. Restrictions in Elaichi apply per action, so you can allow reading appointments and claims in Canvas Medical while blocking creating or updating them. A restricted action is left out of the tool list the AI client sees, so it cannot be called no matter what the prompt says.
What happens to a Canvas Medical connection when someone leaves?
Offboarding that person in Elaichi ends their Canvas Medical access at once, across Claude, ChatGPT, Cursor and every other client. A connection shared with the team keeps working for everyone else. If you want Canvas Medical gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Canvas Medical MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Canvas Medical 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, 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 Canvas Medical?
Yes. Both let Claude, ChatGPT or Cursor use Canvas Medical. 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 Canvas Medical call.
How is Elaichi different from Composio for Canvas Medical?
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 Canvas Medical: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Canvas Medical in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.