meetbot / docs
AI Tools

MCP Server (Cursor, Claude Code, Windsurf)

Plug meetbot into your AI coding assistant. The @meetbot/mcp-server npm package exposes 17 tools — dispatch bots, fetch recordings, control live bots, verify webhooks — over the Model Context Protocol.

Prefer the CLI? See /docs/ai-tools/cli. MCP is the alternative for IDE-embedded agents (Cursor, Windsurf, Cline) that speak Model Context Protocol natively but don't shell out. For most backend / scripting / Claude.ai use cases the CLI is friendlier.

The meetbot MCP server lets your AI coding assistant operate the meetbot API on your behalf. Once installed, you can ask Cursor or Claude Code things like:

  • "Send a meetbot to this Meet URL to record our standup."
  • "List all bots that are currently in a meeting."
  • "Get the recording manifest for the last bot we dispatched."
  • "Have the bot post a 'recording is on' message in the chat."
  • "Verify this incoming webhook signature against my secret."

The package is MIT-licensed and lives at github.com/meetbot-dev/mcp-server (the meetbot GitHub org is taken; we publish under meetbot-dev). The npm name is @meetbot/mcp-server.

Install

You don't actually install anything. MCP clients spawn the server with npx, so all you do is point them at the right command + pass an API key.

Get an API key first at /account/keys. New accounts get $5 of free credit.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-repo):

.cursor/mcp.json
{
  "mcpServers": {
    "meetbot": {
      "command": "npx",
      "args": ["-y", "@meetbot/mcp-server"],
      "env": {
        "MEETBOT_API_KEY": "mb_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Restart Cursor. The 17 meetbot tools appear in Settings → MCP.

Claude Code

Add to ~/.claude.json (global) or .mcp.json (per-project):

.mcp.json
{
  "mcpServers": {
    "meetbot": {
      "command": "npx",
      "args": ["-y", "@meetbot/mcp-server"],
      "env": {
        "MEETBOT_API_KEY": "mb_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Or use the CLI:

claude mcp add meetbot --env MEETBOT_API_KEY=mb_live_xxx -- npx -y @meetbot/mcp-server

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

mcp_config.json
{
  "mcpServers": {
    "meetbot": {
      "command": "npx",
      "args": ["-y", "@meetbot/mcp-server"],
      "env": {
        "MEETBOT_API_KEY": "mb_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Cline (VS Code)

Open the Cline panel → MCP Servers → Edit Configuration and add:

cline_mcp_settings.json
{
  "mcpServers": {
    "meetbot": {
      "command": "npx",
      "args": ["-y", "@meetbot/mcp-server"],
      "env": {
        "MEETBOT_API_KEY": "mb_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Tools exposed

ToolPurpose
dispatch_botSend a bot to record a meeting (Meet/Teams/Zoom).
get_botFetch one bot's status + metadata + manifest URL.
list_botsList bots, filterable by status/platform.
leave_botTell a bot to finalize and leave the meeting.
pause_recordingPause an in-progress recording.
resume_recordingResume a paused recording.
stop_recordingStop recording without leaving the meeting.
send_chat_messagePost a chat message into the meeting.
get_recordingGet the manifest + per-track media URLs.
get_transcriptGet the post-meeting transcript (M6.1+).
list_jobsAlias of list_bots.
get_jobAlias of get_bot.
delete_jobCancel a job (force-stops in-flight bots).
verify_webhook_signatureLocally verify an incoming webhook (no API call).
get_consumerRead the consumer (account) the API key is bound to.
list_recordingsList recent recordings.
delete_recordingPermanently delete a recording (GDPR).

Tool descriptions are written to be picked up correctly by the LLM on the first try. If your assistant chooses the wrong tool for a clear request, open an issue.

Configuration

env varrequireddefaultpurpose
MEETBOT_API_KEYyesYour meetbot API key (get one at /account/keys).
MEETBOT_API_BASE_URLnohttps://api.meetbot.devOverride for self-hosted orchestrators or staging.
MEETBOT_API_TIMEOUT_MSno30000Per-request timeout.

See also

On this page