Skip to content

Whereby MCP connector

The Whereby connector brings meeting rooms, recordings, transcriptions, and summaries into Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Create a Whereby meeting for Thursday's customer review.

Working in Whereby with Elaichi

  • List all Whereby meetings
  • Get single Whereby meeting by ID
  • List all Whereby insight rooms
Ask anything…
Governance / Audit log Last 24 hours
Whereby List all Whereby insight rooms Emily Carter · ChatGPT · 9:41 AM Done
Whereby Get single Whereby meeting by ID Emily Carter · ChatGPT · 9:41 AM Done
Whereby List all Whereby meetings Emily Carter · ChatGPT · 9:41 AM Done
Whereby Create a Whereby meeting Megan Brooks · Claude · 9:38 AM Done
Whereby List all Whereby insight room sessions Ryan Hayes · Cursor · 9:35 AM Done

How to connect Whereby to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Whereby MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Whereby MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 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.

Whereby MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Whereby MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Whereby MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Whereby to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Whereby through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Whereby is logged.

  • 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?”

See all 27 Whereby tools →

What connecting Whereby gets you

6 screens from Elaichi, each doing one job for your Whereby account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Whereby meetings, read live answers.

Plain language questions return answers from live Whereby meetings, sessions and recordings.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Whereby here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Create a Whereby meeting Create Create a new transient meeting room in Whereby. Returns meetingId, roomUrl, and endDate on every call; startDate, roomName, hostRoomUrl, and viewerRoomUrl are returned optionally (hostRoomUrl and viewerRoomUrl only when requested via the fields parameter). Required: endDate.
List all Whereby meetings List List meetings in Whereby. Returns: meetingId, roomName, roomUrl, startDate, endDate, hostRoomUrl, viewerRoomUrl.
Get single Whereby meeting by ID Get Get a single Whereby meeting by id. Returns meetingId, roomUrl, and endDate on every call; startDate, roomName, hostRoomUrl, and viewerRoomUrl are returned optionally (hostRoomUrl and viewerRoomUrl only when requested via the fields parameter). Required: id.
Delete a Whereby meeting by ID Delete Delete a Whereby meeting by id. The endpoint is idempotent and will succeed even if the meeting has already been deleted. Returns an empty 204 response on success. Required: id.
List all Whereby insight rooms List List Whereby room insights summaries. Returns roomName, createdAt, endAt, firstSessionStartedAt, lastSessionStartedAt, totalParticipantMinutes, totalUniqueParticipants, totalSessions, rating, and related usage totals per room. Optionally filter by roomName or createdAt, or sort results with sortBy.

Tool catalog

27 Whereby tools stand ready to call.

Meetings, insight rooms, sessions, participants, recordings and transcriptions, with no custom code.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Whereby · customer meetings and recordings

Whereby starter 18 Mar 4, 2026

Support toolbox

Whereby · live sessions and participants

— 9 Mar 2, 2026

Recruiting toolbox

Whereby · interview meetings and links

— 24 Feb 27, 2026

Customer Success toolbox

Whereby · review calls and transcriptions

Whereby starter 6 Feb 19, 2026

Product Research toolbox

Whereby · insight rooms and sessions

— 31 Jan 30, 2026

Enablement toolbox

Whereby · recording access links

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Whereby toolbox.

Curate one toolbox per team, each scoped to the Whereby work it does.

ElaichiConnections
Connection Scope Status Access
WH

Whereby (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
WH

Whereby (Support)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
WH

Whereby (Recruiting)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
WH

Whereby (Customer Success)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
WH

Whereby (Product Research)

Connected by Ryan Hayes

Personal • Active Not shared
WH

Whereby (Enablement)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Whereby without seeing credentials.

Each connection shows who linked the Whereby account and which teams share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Whereby Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Whereby Meetings Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Whereby Meetings List Toolbox

Audit log

Every Whereby call is on the record.

When, who, what happened, type and resource for each meeting and recording touched.

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.

Whereby digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch meetings

    Whereby

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Whereby

    Queued

Automations

A schedule fires, a Whereby digest posts.

Six steps fetch sessions, group them, draft a digest, await approval, post back.

Whereby health

Refreshed 4 minutes ago · every 15 minutes · from the meetings collection

Live

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%

Collections and dashboards

Whereby room health, counted on a schedule.

Four metrics, 14 days of meetings created and a per team breakdown, no model.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Whereby

All three can connect Whereby to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Whereby, by what to check
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 Whereby tools Allow or restrict single Whereby 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 Whereby 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.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Whereby connection?

Yes. One person connects Whereby in Elaichi with the API key and shares the connection with a team, and nobody else on that team ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so when someone creates a meeting or requests a transcription, the log names that person, not the person who set up the connection.

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 restricting it from deleting recordings, transcriptions, or summaries, or from changing the room theme logo. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, and every other client together.

Does the Whereby MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Whereby 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 Whereby?

Yes. Both let Claude, ChatGPT or Cursor use Whereby. 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 Whereby call.

How is Elaichi different from Composio for Whereby?

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 Whereby: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Whereby 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