# 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. Source: https://elaichi.ai/connectors/whereby/ ## Facts | | | | --- | --- | | Application | Whereby | | Category | Video | | AI tools | 27 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Whereby is connected - 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? ## Connect Whereby in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Whereby. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Whereby tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Whereby to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Whereby to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Whereby tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Whereby through Elaichi ### Set up a customer call in seconds Sales. 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. ### Read the call before the follow-up Support. 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. ### Catch up on a quarterly review you missed Customer success. 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. ### Keep interview rooms tidy and on schedule Recruiting. 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. ### See who actually joined the room Operations. Ask which participants attended the all-hands session and how long each stayed. Insight room data answers attendance questions without anyone exporting a spreadsheet. ### Put the right logo on client rooms Marketing. 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. ## 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 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 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. ## All 27 Whereby tools Every tool below is callable through https://api.elaichi.ai/mcp once Whereby is connected, subject to the toolbox it is in and the restrictions on the caller. - **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. - **List all Whereby insight room sessions** (List). List session-level insights for a given room in Whereby. Returns: roomSessionId, roomName, startedAt, endedAt, totalParticipantMinutes, totalRecorderMinutes, totalStreamerMinutes, totalUniqueParticipants, totalUniqueRecorders, totalUniqueStreamers, rating, totalRatings. Required: roomName. - **List all Whereby insight participants** (List). List participants in a Whereby session filtered by session ID or external ID. Returns: roomSessionId, participantId, deviceId, userId, roleName, displayName, joinedAt, leftAt, externalId, rating, tags, comment. Required: roomSessionId (or externalId). - **Get single Whereby insight participant by ID** (Get). Get detailed session data for a specific participant in a Whereby session, including user agent, bandwidth, and packet loss metrics. Returns: displayName, userRole, userAgent, timeStamp, sampleRateMs, samples. Required: roomSessionId, participantId. - **List all Whereby recordings** (List). List recordings in Whereby. Returns: recordingId, roomSessionId, filename, startDate, endDate, sizeInMegaBytes. Optionally filter by roomName or sort using sortBy (e.g., roomName:asc). - **Get single Whereby recording by ID** (Get). Get metadata for a single Whereby recording by id. Returns: recordingId, roomSessionId, filename, startDate, endDate, sizeInMegaBytes. Required: id. - **Whereby recordings bulk delete** (Delete). Asynchronously delete multiple Whereby recordings at once. The endpoint schedules a background job and returns immediately; it is idempotent and safe to call even if the recordings have already been deleted or do not exist. Returns an empty 204 response on success. Required: recordingIds. - **Delete a Whereby recording by ID** (Delete). Delete a single Whereby recording by id. The endpoint is idempotent. Returns an empty 204 response on success. Required: id. - **List all Whereby recording access links** (List). Get the access link for a Whereby-hosted recording. Returns: accessLink, expires, recordingId, roomSessionId, filename, startDate, endDate, sizeInMegaBytes. Required: recording_id. Available for Whereby-hosted recordings only. - **Create a Whereby transcription** (Create). Create a transcription for a recording in Whereby by scheduling a background transcription job. Returns an empty 201 response on success. Required: recordingId. - **List all Whereby transcriptions** (List). List transcriptions in Whereby. Returns each transcription's transcriptionId, roomSessionId, roomName, createdAt, startDate, endDate, state, durationInSeconds, type, filename, and storageType. Optionally filter by roomName or sort results with sortBy. - **Get single Whereby transcription by ID** (Get). Get a single Whereby transcription by id. Returns transcription metadata including transcriptionId, roomSessionId, roomName, createdAt, startDate, endDate, state, durationInSeconds, type, filename, and storageType. Required: id. - **Whereby transcriptions bulk delete** (Delete). Bulk delete multiple Whereby transcriptions asynchronously by scheduling a background deletion job. The operation is idempotent and succeeds even if transcriptions have already been deleted or do not exist. Returns an empty 204 response on success. Required: transcriptionIds. - **Delete a Whereby transcription by ID** (Delete). Delete a Whereby transcription by id. The operation is idempotent and succeeds even if the transcription has already been deleted. Returns an empty 204 response on success. Required: id. - **List all Whereby transcription access links** (List). Get a temporary download link for a Whereby-hosted transcription. Returns: accessLink, expires, transcriptionId, roomSessionId, roomName, createdAt, startDate, endDate, state, durationInSeconds, filename, storageType. Required: transcription_id. Available for Whereby-hosted transcriptions only; the link is valid for up to 43200 seconds (default 3600). - **Create a Whereby summary** (Create). Create a new summary in Whereby for a specified transcription. Schedules a summary generation job asynchronously and returns an empty 201 response on success. Required: transcriptionId. - **List all Whereby summaries** (List). List summaries in Whereby. Returns a collection of summary records each including summaryId, transcriptionId, summary, roomSessionId, roomName, createdAt, startDate, endDate, state, modifiedAt, and template. Supports sorting via the sortBy parameter. - **Get single Whereby summary by ID** (Get). Get a single Whereby summary by id. Returns the summary record including summaryId, transcriptionId, summary, roomSessionId, roomName, createdAt, startDate, endDate, state, modifiedAt, and template. Required: id. - **Delete a Whereby summary by ID** (Delete). Delete a Whereby summary by id. The endpoint is idempotent and Returns an empty 204 response on success. Returns an empty 204 response on success. Required: id. - **Update a Whereby room theme logo by ID** (Update). Upload a logo image for a Whereby room via multipart/form-data. Accepts a PNG image (at least 400px wide recommended). Returns an empty 204 response on success. Required: room_name. - **Update a Whereby room theme token by ID** (Update). Set primary, secondary, and focus room theme colors in Whereby for a specific room. Supply custom color values via `tokens.colors` and control whether they are applied with `tokensPreset`. Returns an empty 204 response on success. Required: room_name. - **Update a Whereby room theme background by ID** (Update). Upload a custom background image for a Whereby room using multipart/form-data. Returns an empty 204 response on success. Required: room_name. - **Update a Whereby room theme knock page background by ID** (Update). Upload a custom knock page background image for a Whereby room using multipart form data. Returns an empty 204 response on success. Required: room_name.