Skip to content

Summary

Send a bot into a Zoom, Google Meet or Teams call from your agent: 19 tools covering the bot lifecycle, transcripts, per-participant media, live chat and calendar scheduling.

Features

  • 19 tools covering the full meeting bot lifecycle across Zoom, Google Meet, Teams and Webex
  • Transcripts, per-participant media URLs, participant lists and a speaker timeline
  • Live in-meeting actions: send chat messages and images while the call is running
  • Calendar listing and scheduled bot dispatch
  • Hosted remote server at mcp.meetstream.ai — no install required
  • One-line Claude Code setup; works with Claude Desktop, Cursor, Windsurf and any MCP client

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "MeetStream MCP Server" tools will be available.
{
  "mcpServers": {
    "meetstream-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meetstream/mcp"
      ],
      "env": {
        "MEETSTREAM_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Description

MeetStream's meeting bot API puts a recording, streaming and speaking bot into Zoom, Google Meet, Microsoft Teams and Webex calls. This is the official MCP server for it, which means an agent can run the whole meeting lifecycle — dispatch a bot, watch it join, pull the transcript afterwards — without you writing a line of HTTP glue.

The 19 tools

Bot lifecycle — create_bot, list_bots, get_bot_status, get_bot_detail, get_bot_summary, remove_bot, delete_bot_data.

Transcription — get_transcript, list_transcriptions, transcribe_audio.

Meeting data and media — get_media_urls, get_participants, get_chats, get_speaker_timeline. The speaker timeline is the one that makes agent summaries genuinely useful: attribution by participant rather than an undifferentiated wall of text.

Live interaction — send_chat_message and send_image, so the bot can act in the meeting while it is still running rather than only reporting on it afterwards.

Calendar — list_calendar_events, schedule_calendar_bot, plus a webhook_events_guide reference tool for wiring up lifecycle callbacks.

Running it

Local via npx -y @meetstream/mcp with a MEETSTREAM_API_KEY, or hosted at https://mcp.meetstream.ai/mcp?key=... with nothing to install. Claude Code users can add it in one line: claude mcp add meetstream --env MEETSTREAM_API_KEY=... -- npx -y @meetstream/mcp. Cursor, Windsurf and any other MCP client work the same way. Keys are minted at app.meetstream.ai/api-key.

Worth knowing

Bots are billed by the hour ($0.35, prorated to the second, with $5 of free credit to start), so an agent holding this server can spend money by leaving a bot in an empty room — get_bot_status and remove_bot exist for a reason. And putting a recording bot into someone else's meeting is a consent question in most jurisdictions before it is a technical one; disclose accordingly.

Covered in the Weekly

Related MCP Servers

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

MCP: ripwire

by Red Hat

Featured

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

MCP: Graft

by Trail

Featured

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Featured

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Browse all MCP servers →