Coviu MCP connector
The Coviu connector brings telehealth sessions, participants, waiting room calls, intake form submissions, audio recordings and session summaries to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works with Coviu as themselves and every action is logged.
- App credentials
- Free 14-day trial
- No credit card
Create a Coviu session for tomorrow's intake clinic.
Working in Coviu with Elaichi
-
List all Coviu sessions
-
Get single Coviu session by ID
-
List all Coviu participants
How to connect Coviu to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Coviu 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.
Coviu 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.
Coviu 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.
Coviu 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.
Coviu 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 Coviu 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 Coviu through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Coviu is logged.
-
Reception
Book the consult and invite the patient
Create the Coviu session for tomorrow's appointment, add the patient and the treating clinician as participants, and fix the time if the patient calls back to move it.
-
Clinicians
Read the session summary before charting
Pull up the summary and audio recording for the consult you just finished, then ask for the main points before you write the clinical note.
-
Front desk
See who is waiting right now
Ask which patients are sitting in the Coviu waiting area and how long they have been in the queue, so nobody is left unattended while the clinic runs late.
-
Intake
Check whether the forms came back
List the intake form submissions for this week's new patients and open the attached files, so the clinician has the history before the call starts.
-
Practice management
Tidy up the week's sessions
List every session scheduled for the coming week, correct the ones with the wrong clinician or time, and remove the bookings that were cancelled by phone.
-
Quality and compliance
Answer a records request quickly
Find a specific past call, retrieve its recording and summary, and confirm exactly who was a participant when a complaint or audit lands on your desk.
Try asking
- “Create a Coviu session for tomorrow's intake clinic.”
- “List all Coviu waiting queue calls right now.”
- “Who joined yesterday's Coviu sessions as a participant?”
What connecting Coviu gets you
6 screens from Elaichi, each doing one job for your Coviu account.
Ask Elaichi to work across your apps.
Create a Coviu session for tomorrow's intake clinic.
List all Coviu waiting queue calls right now.
Who joined yesterday's Coviu sessions as a participant?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Coviu sessions, get real answers.
Plain language questions run against live Coviu sessions, participants and waiting calls.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Coviu.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
19 Coviu tools ready to call.
Sessions, participants, waiting calls and collections are covered without custom code.
Toolboxes
Every team gets its own Coviu toolbox.
Curate toolboxes per team so clinicians and support see only relevant Coviu tools.
Shared connections
Teammates run Coviu calls without credentials.
See who connected each Coviu account and how many teams and members share it.
Audit log
Every Coviu call is on the record.
When, who, what happened, type and resource, appended for each Coviu 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.
Coviu digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch sessions
Coviu
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
Coviu
Queued
Automations
A schedule fires, Coviu work finishes.
Fetch Coviu sessions, group them, draft a digest, approve, then post back.
Coviu health
Refreshed 4 minutes ago · every 15 minutes · from the sessions collection
Sessions
1,284 ↓ 12%
Participants
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Sessions created
Last 14 days
By team
Share of activity
Clinical APAC 34%
Intake desk 27%
Support 21%
Allied health 18%
Collections and dashboards
Coviu session numbers computed, not requested.
Four metrics, 14 days of sessions created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Coviu
All three can connect Coviu 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 Coviu tools | Allow or restrict single Coviu 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 Coviu 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.
Coviu tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Coviu, 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 Coviu to Claude?
Connect Coviu in Elaichi by entering your Coviu app credentials, which come straight from your Coviu account. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in as yourself and Coviu is ready to use.
Does Coviu work with ChatGPT and Cursor as well as Claude?
Yes. Once Coviu 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 Coviu once and every client you use picks it up.
What can an AI agent actually do with my Coviu data?
An agent connected to Coviu can create, look up, change and cancel telehealth sessions, and add or remove the patients and clinicians attending them. It can tell you who is in the waiting room and the waiting queue, open a specific call, and list intake form submissions with their attached files. It can also fetch the audio recording and the written summary for a finished Coviu session and answer questions about them.
Does connecting Coviu give the AI access to every clinic and every consult?
No. Each person signs in to Coviu as themselves, so the agent only sees the sessions, participants, submissions and recordings that person can already see in Coviu. Elaichi can narrow that further, for example to reading only, but it can never widen access beyond what Coviu already grants that person.
Can I stop an agent from deleting or changing things in Coviu?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Coviu sessions and waiting room calls while restricting the ability to delete a session or remove a participant. 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 Coviu connection when someone leaves?
Offboarding a person in Elaichi ends their access to Coviu through every client at once. If they set up a shared Coviu connection, it keeps working for everyone else on the team. When you want Coviu gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Coviu MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Coviu 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 Coviu?
Yes. Both let Claude, ChatGPT or Cursor use Coviu. 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 Coviu call.
How is Elaichi different from Composio for Coviu?
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 Coviu: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Coviu 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