Video
Whereby
Connect Whereby once and hand every teammate a governed MCP endpoint with 27 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put Whereby work on a schedule.
A trigger starts a sequence of steps: call a Whereby tool, transform the result, branch, wait, and ask a person when it matters.
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
Report on Whereby without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Whereby health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Transcriptions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
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.
create_a_whereby_meeting
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 meetings in Whereby. Returns: meetingId, roomName, roomUrl, startDate, endDate, hostRoomUrl, viewerRoomUrl.
get_single_whereby_meeting_by_id
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 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 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 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 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 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 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 metadata for a single Whereby recording by id. Returns: recordingId, roomSessionId, filename, startDate, endDate, sizeInMegaBytes. Required: id.
whereby_recordings_bulk_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 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
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 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 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 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
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 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
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 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 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 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 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
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
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
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
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.
No tools match your search.
How it works
From Whereby account to governed MCP endpoint
Connect
Link a Whereby account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Whereby tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.