MeetStream MCP Server
OfficialMeetStream MCP Server exposes 19 tools that give any MCP client (Claude, Cursor, etc.) full control over the MeetStream meeting-bot API — sending bots into Zoom/Google Meet/Teams calls, recording, transcribing, summarizing, interacting live, and managing calendar auto-joins — authenticated with a single MeetStream API key.
Bot lifecycle —
create_bot(immediate or scheduled viajoin_at, with video/audio options, callback webhooks, idempotency keys, retention, custom attributes),list_bots,get_bot_status,get_bot_detail,get_bot_summary(built-in AI summary),remove_bot(leave but keep data),delete_bot_data(irreversible, requiresconfirm: true).Transcription —
get_transcript(auto-resolvestranscript_id, supports polling and raw output),list_transcriptions,transcribe_audio(re-run with a different provider or language).Media & meeting data —
get_media_urls(presigned audio/video/per-participant streams/screenshots),get_participants,get_chats,get_speaker_timeline.Live meeting interaction —
send_chat_messageinto an active call,send_imageto display an image/GIF as the bot's video frame.Calendar —
list_calendar_eventsfrom a connected Google Calendar,schedule_calendar_botto schedule or unschedule a bot for an event.Reference —
webhook_events_guidereturns live-verified webhook ground truth (envelope shape, two-layerbot.stoppedmodel, streaming-provider caveats) to consult before writing handlers.Deployment — runs locally over stdio (
npx @meetstream/mcpwithMEETSTREAM_API_KEY) or remotely as a stateless Streamable HTTP endpoint athttps://mcp.meetstream.ai/mcpwith a per-request Bearer key.
Provides transcription services for meeting audio, supporting live streaming and post-meeting retranscription.
Allows listing upcoming calendar events and scheduling or removing bots for specific events.
Allows creating bots that join Google Meet meetings, with recording, transcription, and live interaction capabilities.
Allows creating bots that join Zoom meetings, with recording, transcription, and live interaction capabilities.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MeetStream MCP Server Join my 10am Google Meet, record it, and summarize."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MeetStream MCP Server
Give Claude - or any MCP-compatible client - direct access to the MeetStream meeting-bot API. Add one URL, sign in, and your assistant can run the full bot lifecycle (create, record, transcribe, summarize, interact live, manage calendar auto-join) through 19 tools.
https://mcp.meetstream.ai/mcpMeetStream hosts the server. There is nothing to install or run on your machine, and it is always the current version.
Quick start
Add
https://mcp.meetstream.ai/mcpto your AI tool. Do not add a key.Click Connect (in Claude Code: run
/mcp, then choose Authenticate). Your browser opensapp.meetstream.ai.Sign in to MeetStream, then click Allow. MeetStream creates an API key for this connection. You do not see or copy the key.
Ask your AI tool: "list my meetstream bots". A list, or an empty list, means that you are connected.
The exact steps for each tool are in Connect.
Which URL to use
URL | Use it for |
| All current clients. Streamable HTTP. The replies stream as server-sent events (SSE), so you do not need a separate SSE setting. |
| Only clients that support just the older HTTP+SSE transport (2024-11-05). The sign-in and the API key work the same way. |
Your AI tool ──HTTPS + OAuth sign-in──► mcp.meetstream.ai ──► api.meetstream.aiThe old npm package
@meetstream/mcp(npx @meetstream/mcp) is frozen at 0.3.0 and no longer maintained. It predates the currentcreate_botdefaults and fixes. Use the hosted URL instead.
Related MCP server: AI Workforce MCP Server
Connect
Add the URL with no key. Your client finds MeetStream's sign-in, opens app.meetstream.ai in your browser, and you click Allow. The dashboard creates an API key for that connection, named MCP · <app name> · <date> · <number>. To disconnect, delete that key on the API keys page.
This is the page that opens in your browser. If you are not signed in to MeetStream, you sign in first, then you see this page:
The page shows the name of the app that asked to connect. If you do not recognize the app, click Cancel. The sign-in link is valid for 15 minutes.
Claude Code
claude mcp add --transport http meetstream https://mcp.meetstream.ai/mcp
# then run /mcp in Claude Code and choose AuthenticateClaude (web and desktop)
Customize → Connectors → + → Add custom connector. Name it meetstream, set the URL to https://mcp.meetstream.ai/mcp, leave the OAuth fields blank, and click Connect.
Cursor
~/.cursor/mcp.json (or install the MeetStream Cursor plugin), then click Connect next to meetstream in Cursor Settings → MCP:
{
"mcpServers": {
"meetstream": { "url": "https://mcp.meetstream.ai/mcp" }
}
}VS Code
.vscode/mcp.json, then start the server and sign in when VS Code asks:
{
"servers": {
"meetstream": { "type": "http", "url": "https://mcp.meetstream.ai/mcp" }
}
}Windsurf
~/.codeium/windsurf/mcp_config.json. Cascade asks you to sign in on first use. If your Windsurf version cannot finish the sign-in, use an API key header (below):
{
"mcpServers": {
"meetstream": { "serverUrl": "https://mcp.meetstream.ai/mcp" }
}
}Codex
~/.codex/config.toml, then run codex mcp login meetstream:
[mcp_servers.meetstream]
url = "https://mcp.meetstream.ai/mcp"Any other MCP client
Point it at https://mcp.meetstream.ai/mcp as a remote (Streamable HTTP) server. Clients that support MCP authorization sign in by themselves: protected resource metadata (RFC 9728), authorization server metadata (RFC 8414), dynamic client registration (RFC 7591) and the authorization code flow with PKCE. Access tokens last an hour and refresh automatically.
Or use an API key
For clients without OAuth, or for scripts and CI, create a key at app.meetstream.ai/api-keys and send it as a header:
{
"mcpServers": {
"meetstream": {
"url": "https://mcp.meetstream.ai/mcp",
"headers": { "Authorization": "Bearer ms_YOUR_API_KEY" }
}
}
}Claude Code:
claude mcp add --transport http meetstream https://mcp.meetstream.ai/mcp --header "Authorization: Bearer $MEETSTREAM_API_KEY"Codex: add
bearer_token_env_var = "MEETSTREAM_API_KEY"to the[mcp_servers.meetstream]block.X-MeetStream-Api-Key: <key>works too. For connector UIs that cannot set headers,https://mcp.meetstream.ai/mcp?key=<key>. The server never logs query strings, but a key in a URL can end up in client-side history, so prefer OAuth or a header.
Older clients (HTTP+SSE)
/mcp is the main endpoint, and its replies already stream as server-sent events (text/event-stream). Clients that only speak the older 2024-11-05 HTTP+SSE transport connect to https://mcp.meetstream.ai/sse with the same sign-in or key options. The stream's first event names the per-session message endpoint; the key never appears in it.
Check it is connected
Ask your client something like "list my meetstream bots" - if it returns data (or a clean empty list) instead of an error, you are connected.
Then just ask
"Join my standup at https://meet.google.com/abc-defg-hij, record it with Deepgram transcription, and give me the transcript when it's done."
"List my bots from today and give me the AI summary of the 3pm customer call."
"Send 'we'll follow up by email' into the meeting the bot is in, then show them our logo."
"Schedule a bot for tomorrow's board meeting on my calendar."
Full capability list - 19 tools
Bot lifecycle
Tool | What it does |
| Sends (or schedules, via |
| Lists every bot on the account (paginated). |
| Current lifecycle status - one of |
| Full session metadata: platform, timings, status timeline, the canonical |
| MeetStream's built-in AI meeting summary - no external LLM call needed. |
| Makes the bot leave an active meeting immediately. Recorded data is kept. |
| Permanently deletes a bot's audio, video, and transcripts. Requires |
Transcription
Tool | What it does |
| Fetches a transcript by |
| Lists every transcription run for a bot - provider, status, and presigned download URLs (valid 1h). |
| (Re-)transcribes a bot's recorded audio with a chosen provider - useful to retry with a different provider or language after the meeting. |
Media & meeting data
Tool | What it does |
| Presigned URLs for |
| Everyone detected in the meeting - display name, full name, status, stream ids. |
| In-meeting chat messages captured during the call. |
| Who spoke and when, as a timeline of speaker segments. |
Live meeting interaction
Tool | What it does |
| Posts a chat message into the live meeting through the bot. |
| Displays an image or GIF as the bot's video frame. |
Calendar
Tool | What it does |
| Upcoming events from a connected Google Calendar. (Connecting a calendar - |
| Schedules ( |
Reference
Tool | What it does |
| Returns the webhook reference - envelope shape ( |
What makes this different from just reading the docs
Every tool description and the webhook_events_guide bake in live-verified ground truth, confirmed against real production bot runs, that the public API docs currently get wrong:
Every delivery carries
event, and most also carrybot_eventwith the specific name. Readeventto route,bot_eventfor detail.Terminals are two-layer: every ending arrives once with
event: "bot.stopped", andbot_eventsays why (bot.stopped,bot.kicked,bot.notallowed,bot.denied,bot.failed). Lobby timeouts, denials and failures carrystatus_code: 500. Branch onbot_event, notbot_status- a kick and a clean exit both reportStopped.Streaming-only transcription providers (
deepgram_streaming,assemblyai_streaming,jigsawstack_streaming,meetstream_streaming,meeting_captions) produce no post-call transcript, sotranscription.processednever fires.bot.donestill does. A post-call transcript fetch for them returns202indefinitely, so cap your polling.transcript_idis never in a webhook payload -get_transcriptresolves it for you automatically instead of making the model guess.Safe defaults everywhere:
automatic_leavetimeouts on everycreate_botcall, andrecording_permission_denied_timeoutfloored at 60 (the API rejects lower values with a 400).
How it works
The server holds no API key of its own: each request (or SSE session) carries the caller's key or an OAuth token that wraps it. A request with no credentials gets a 401 with setup instructions and a WWW-Authenticate header pointing OAuth clients at the sign-in flow. Streamable HTTP is stateless, so the service scales horizontally with no shared state; OAuth tokens are encrypted, self-contained values, so there is no token database either.
MeetStream runs the server; it is written in Go and its source is not published. This repo holds the user docs and the MCP Registry entry (server.json). To report a problem, open an issue here.
Troubleshooting
Symptom | Fix |
Sign-in page says the link has expired | Sign-in links last 15 minutes. Start the connection again from your client |
| Sign in through your client (OAuth), or send |
Tool call returns a 401 from the API | The key is invalid or revoked (for OAuth connections, the key named after the app was deleted). Reconnect, or generate a new key at app.meetstream.ai/api-keys |
| The meeting hasn't finished processing yet, or (for streaming providers) there is no post-call transcript - check |
Calendar tools return empty/errors | No calendar is connected yet - connect one via |
Your client only supports the old SSE transport | Use |
Prefer a terminal? See the MeetStream CLI. Docs: docs.meetstream.ai · API spec: openapi.json · Migrating from Recall.ai: @meetstream/migrate
Privacy and telemetry
The hosted server records anonymous counts of which tools are called and whether each call succeeded. It never records your API key, OAuth tokens, meeting URLs, transcripts, or any other content. Server logs contain the request path only, never the query string.
MIT © MeetStream.ai
Available Tools
19 toolscreate_botCreate a meeting botAInspect
Send a MeetStream bot to a Zoom / Google Meet / Microsoft Teams meeting (or schedule it with join_at). Returns bot_id and (when a transcription provider is set) transcript_id. Set callback_url to receive lifecycle webhooks.
Inputs: meeting_link (required), join_at, bot_name, language, +12 more.
delete_bot_dataDelete bot data (permanent)ADestructiveInspect
PERMANENTLY delete a bot's audio, video, and transcripts. Irreversible — fires a data_deletion webhook. Only call when the user explicitly asks to delete data.
Inputs: bot_id (required), confirm (required).
get_bot_detailGet bot detailARead-onlyInspect
Full session metadata: platform, duration, timings, status timeline, transcript_id (canonical source), caption_file (for meeting_captions provider), original request payload.
Inputs: bot_id (required).
get_bot_statusGet bot statusBRead-onlyInspect
Current bot status. Values: Joining, InWaitingRoom, InMeeting, Recording, Leaving, Stopped, NotAllowed, Denied, Error, Done.
Inputs: bot_id (required).
get_bot_summaryGet AI meeting summaryBRead-onlyInspect
MeetStream's built-in AI summary of the meeting (no external LLM needed).
Inputs: bot_id (required).
get_chatsGet in-meeting chatCRead-onlyInspect
Chat messages captured during the meeting.
Inputs: bot_id (required).
get_media_urlsGet recording URLsARead-onlyInspect
Presigned S3 URLs for recorded media. kind=audio (valid 1h), video (valid 10min), audio_streams / video_streams (per-participant; require separate_*_streams at creation), screenshots.
Inputs: bot_id (required), kind.
get_participantsGet participantsBRead-onlyInspect
Participants detected in the meeting (displayName, fullName, status, stream ids).
Inputs: bot_id (required).
get_speaker_timelineGet speaker timelineBRead-onlyInspect
Who spoke and when (chunk timeline with speaker ids/names).
Inputs: bot_id (required).
get_transcriptGet transcriptARead-onlyInspect
Fetch a bot's transcript by bot_id. Resolves transcript_id automatically (it is NOT in webhooks) via /detail → /transcriptions. Set wait=true to poll until ready (after transcription.processed fires). Segments have speaker and transcript fields.
Inputs: bot_id (required), raw, wait, timeout_seconds.
list_botsList botsARead-onlyInspect
List all bots on the account (paginated: bots[], hasNextPage, nextCursor).
Inputs: no named parameters.
list_calendar_eventsList calendar eventsCRead-onlyInspect
Upcoming events from connected Google Calendars (connect via POST /calendar/create_calendar with google_client_id/secret/refresh_token — needs OAuth credentials, usually done once from the dashboard or CLI).
Inputs: no named parameters.
list_transcriptionsList transcription runsARead-onlyInspect
All transcription runs for a bot: transcript_id, provider, status, presigned download_urls (valid 1h).
Inputs: bot_id (required).
remove_botRemove bot from meetingAInspect
Make the bot leave an active meeting now. Recorded data is KEPT (use delete_bot_data to erase).
Inputs: bot_id (required).
schedule_calendar_botSchedule / unschedule a calendar botBInspect
action=schedule sends a bot to a specific calendar event; action=unschedule removes it.
Inputs: event_id (required), action.
send_chat_messageSend chat message into the meetingAInspect
Post a chat message into the live meeting through the bot.
Inputs: bot_id (required), message (required).
send_imageShow an image in the meetingCInspect
Display an image/GIF as the bot's video frame. img_url must be PUBLIC.
Inputs: bot_id (required), img_url (required), display_duration_seconds.
transcribe_audioRun / re-run transcriptionBInspect
Start a (re-)transcription of a bot's recorded audio with a chosen post-call provider. Useful to try a different provider or language after the meeting.
Inputs: bot_id (required), language, provider, callback_url.
webhook_events_guideWebhook events guide (live-verified)ARead-onlyInspect
Authoritative reference for MeetStream webhook events — envelope shape, full event list, two-layer bot.stopped model, streaming-provider caveats. Use this before writing any webhook handler.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Each tool targets a distinct resource or action: bot lifecycle (create, status, detail, summary, remove, delete), media/transcript retrieval (transcript, transcriptions, media urls), meeting content (participants, chats, speaker timeline), and live interaction (send chat/image). There is minor overlap between get_bot_status and get_bot_detail, but the difference (current status vs full metadata) is clear.
All tool names follow a consistent verb_noun pattern in snake_case: create_bot, get_bot_status, remove_bot, list_transcriptions, send_chat_message, etc. The only slight deviation is webhook_events_guide, but it's still a noun phrase and does not break the overall convention.
19 tools is above the typical 3-15 range, but the count is justified by the breadth of features: bot lifecycle, transcripts, media, participants, chat, calendar, and webhook guidance. It feels slightly heavy but each tool covers a distinct function and none are redundant.
The core meeting bot lifecycle is well covered: create, monitor, retrieve data, leave, delete, and interact. Minor gaps exist—there is no direct tool to create/connect calendar OAuth credentials (only list and schedule against existing connections), and no update/pause/resume bot action—but these can be worked around via the dashboard/CLI or by re-creating a bot.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides 14 MCP tools for AI agent infrastructure, enabling knowledge base queries, skill search, handoffs, blueprint validation, trust scoring, identity verification, SLA validation, and compliance checks.2227 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceProvides calendar, email, meeting transcription and summarization, and weather tools via MCP, enabling users to manage schedules, handle correspondence, capture meeting insights, and check conditions through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceExposes a five-agent event operations fleet as 12 MCP tools, letting any MCP client detect scheduling conflicts, route notifications, brief executives, chase vendor SLAs, enforce GDPR, and design bespoke agent fleets via live LLM calls.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT