Video
Whereby MCP connector
The Whereby connector brings meeting rooms, recordings, transcriptions, and summaries into Claude, ChatGPT, Cursor, and the Elaichi Agent, so your team can set up calls and catch up on what was said, all inside the connected Whereby account's access.
-
How it connects. Connects with an API key. 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.
27 tools
How to connect
How to connect Whereby to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Whereby once
-
Open Connections, choose Add connection, and pick Whereby.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Whereby API key. One person generates a token in Whereby and pastes it once. Everyone else works through Share with, and never sees it.
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 Whereby 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 Whereby 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 Whereby 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 Whereby 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 Whereby through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Set up a customer call in seconds
Ask for a Whereby meeting room for Thursday's demo and get the link back ready to paste into the invite. No switching tabs while the prospect is still on the phone.
-
Support
Read the call before the follow-up
Pull the transcription and summary from yesterday's screen-share session and see exactly what the customer reported. Write the follow-up from what was actually said rather than from memory.
-
Customer success
Catch up on a quarterly review you missed
Request a summary of the recorded review, then ask which commitments were made and who owns them. Get the gist in two minutes instead of watching an hour of video.
-
Recruiting
Keep interview rooms tidy and on schedule
Create a Whereby room for each candidate on this week's shortlist and clear out the rooms from interviews that already happened. The list of upcoming meetings stays clean.
-
Operations
See who actually joined the room
Ask which participants attended the all-hands session and how long each stayed. Insight room data answers attendance questions without anyone exporting a spreadsheet.
-
Marketing
Put the right logo on client rooms
Update the room theme logo when the brand refreshes or when a partner event needs its own look. Every room your team hosts shows the current branding.
Try asking
- “Create a Whereby meeting for Thursday's customer review.”
- “List last week's Whereby recordings for the support team.”
- “Which participants joined yesterday's insight room sessions?”
AI tools
Whereby tools for your AI agents
27 tools are ready to call through Elaichi's MCP endpoint the moment you connect Whereby, 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 Whereby gets you
6 screens from the product, each doing one job for your Whereby account.
The agent
Ask about Whereby meetings, read live answers.
Plain language questions return answers from live Whereby meetings, sessions and recordings.
- meetings
- recordings
- participants
- transcriptions
Ask Elaichi to work across your apps.
Create a Whereby meeting for Thursday's customer review.
List last week's Whereby recordings for the support team.
Which participants joined yesterday's insight room sessions?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Whereby here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
27 Whereby tools stand ready to call.
Meetings, insight rooms, sessions, participants, recordings and transcriptions, with no custom code.
- Create a Whereby meeting
- List all Whereby meetings
- Get single Whereby meeting by ID
- Delete a Whereby meeting by ID
ElaichiToolsToolboxes
Every team gets its own Whereby toolbox.
Curate one toolbox per team, each scoped to the Whereby work it does.
- Sales
- Support
- Recruiting
- Customer Success
ElaichiToolboxesShared connections
Teammates use Whereby without seeing credentials.
Each connection shows who linked the Whereby account and which teams share it.
- Sales EMEA
- Support
- Recruiting
- Customer Success
ElaichiConnectionsAudit log
Every Whereby call is on the record.
When, who, what happened, type and resource for each meeting and recording touched.
- 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, a Whereby digest posts.
Six steps fetch sessions, group them, draft a digest, await approval, post back.
Whereby digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch meetings
Whereby
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
Whereby
Queued
Collections and dashboards
Whereby room health, counted on a schedule.
Four metrics, 14 days of meetings created and a per team breakdown, no model.
Whereby health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Recordings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Support 27%
Recruiting 21%
Customer Success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Whereby to Claude?
Connecting Whereby takes two steps. In Elaichi, choose Whereby and paste the API key from your Whereby account settings, which is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and Whereby meetings, recordings, transcriptions, and summaries are available in Claude.
Does Whereby work with ChatGPT and Cursor as well as Claude?
Yes. Once Whereby 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 Whereby once, and every client your team uses picks it up.
What can an AI agent actually do with my Whereby data?
An agent connected to Whereby can create a meeting room and hand you the link, list upcoming and past meetings, and look up a specific one. It can find recordings from a session, request a transcription or a summary of a call, and read back what was discussed, who joined an insight room, and how long they stayed. It can also delete old meetings, recordings, transcriptions, and summaries when you ask, and update a room's theme logo.
Does connecting Whereby give the AI everything in my Whereby account?
An agent working through Elaichi sees only what the connected Whereby account can see, because every request runs inside that account's own access. Elaichi can narrow that further, for example limiting a team to reading summaries and creating meetings, but it can never widen it beyond what Whereby itself allows. Each person still signs in to Elaichi as themselves, so the audit log records who made each request.
Can I stop an agent from deleting or changing things in Whereby?
Yes. Restrictions in Elaichi apply per action, so you can allow an agent to create Whereby meetings and read recordings while blocking it from deleting recordings, transcriptions, or summaries, or from changing the room theme logo. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.
What happens to a Whereby connection when someone leaves?
When you offboard someone in Elaichi, their access to Whereby through every AI client ends at once. If they were using a shared Whereby connection, it keeps working for everyone else on the team without anyone re-entering the API key. If you ever want to remove Whereby entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put Whereby in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.