Video
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 and the Elaichi Agent, so each person works with Coviu as themselves and every action is logged.
-
How it connects. App credentials. 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.
19 tools
How to connect
How to connect Coviu to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Coviu once
-
Open Connections, choose Add connection, and pick Coviu.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Coviu app credentials. Coviu authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
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.
Connect Coviu to 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.
Connect Coviu to 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.
Connect Coviu to 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 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.
Use cases
What teams do with Coviu through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
AI tools
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.
See it in Elaichi
What connecting Coviu gets you
6 screens from the product, each doing one job for your Coviu account.
The agent
Ask about Coviu sessions, get real answers.
Plain language questions run against live Coviu sessions, participants and waiting calls.
- sessions
- participants
- waiting calls
- collections
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Coviu.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
19 Coviu tools ready to call.
Sessions, participants, waiting calls and collections are covered without custom code.
- Create a Coviu session
- List all Coviu sessions
- Get single Coviu session by ID
- Update a Coviu session by ID
ElaichiToolsToolboxes
Every team gets its own Coviu toolbox.
Curate toolboxes per team so clinicians and support see only relevant Coviu tools.
- Clinical
- Intake
- Support
- Operations
ElaichiToolboxesShared connections
Teammates run Coviu calls without credentials.
See who connected each Coviu account and how many teams and members share it.
- Clinical APAC
- Intake desk
- Support
- Allied health
ElaichiConnectionsAudit log
Every Coviu call is on the record.
When, who, what happened, type and resource, appended for each Coviu request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 fires, Coviu work finishes.
Fetch Coviu sessions, group them, draft a digest, approve, then post back.
Coviu digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Coviu
Queued
Collections and dashboards
Coviu session numbers computed, not requested.
Four metrics, 14 days of sessions created and a team breakdown, refreshed on schedule.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking the ability to delete a session or remove a participant. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.
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 and every other client together.
Put Coviu in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.