MeetStream MCP server

MeetStream MCP Server

Give Claude - or any MCP-compatible client - direct access to the MeetStream meeting-bot API. The server authenticates to MeetStream with your API key and exposes the full bot lifecycle (create, record, transcribe, summarize, interact live, manage calendar auto-join) as 19 callable tools.

Two ways to run it:

• Local (stdio) - the default, npx @meetstream/mcp. Your MCP client launches it as a subprocess; nothing to host.
• Remote (Streamable HTTP) - https://mcp.meetstream.ai/mcp. A hosted, multi-tenant endpoint you can add by URL, no local install. Each request authenticates with its own API key via header (see Remote server below).

Local:   Claude/MCP client ──stdio (subprocess)──► @meetstream/mcp ──HTTPS + API key──► api.meetstream.ai
Remote:  Claude/MCP client ──HTTPS + your key───► mcp.meetstream.ai ──HTTPS + your key──► api.meetstream.ai

1. Get an API key

Create one at app.meetstream.ai/api-keys. This is the credential the server uses to authenticate every request - internally it sends Authorization: Token on every call to https://api.meetstream.ai/api/v1. There's no OAuth flow, no login step, no separate MCP account: the API key is the authentication.

2. Install & configure

The server reads the key from the MEETSTREAMAPIKEY environment variable - you set it once in your MCP client's config and every tool call uses it automatically.

Claude Code (CLI)

claude mcp add meetstream --env MEETSTREAM_API_KEY=ms_XXXX -- npx -y @meetstream/mcp

Claude Desktop

Edit claudedesktopconfig.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "meetstream": {
      "command": "npx",
      "args": ["-y", "@meetstream/mcp"],
      "env": { "MEETSTREAM_API_KEY": "ms_XXXX" }
    }
  }
}

Restart Claude Desktop after saving.

Cursor

Settings → Cursor Settings → MCP → Add new global MCP server, or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "meetstream": {
      "command": "npx",
      "args": ["-y", "@meetstream/mcp"],
      "env": { "MEETSTREAM_API_KEY": "ms_XXXX" }
    }
  }
}

Windsurf

Settings (Cmd+,) → Cascade → MCP Servers → Add Server - same command/args/env as above, written to ~/.codeium/windsurf/mcp_config.json.

Any other MCP client

Point it at the stdio command npx -y @meetstream/mcp with MEETSTREAMAPIKEY set in the process environment. That's the entire integration surface - the server needs no other config.

Verify it's connected

Ask your client something like "list my meetstream bots" - if it returns data (or a clean empty list) instead of an error, auth is working. A misconfigured key surfaces as a tool error: "MEETSTREAMAPIKEY is not set..." or a 401 from the API.

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

Shortened. The full README is on GitHub.