Drive Your Meetings from Claude and Cursor: the Meeting BaaS MCP Server

LLazare Rossillon

The open-source Meeting BaaS MCP server lets Claude, Cursor and any MCP client send recording bots, search transcripts, schedule calendar recordings and share meeting moments — from chat.

Drive Your Meetings from Claude and Cursor: the Meeting BaaS MCP Server
August 13, 2026

The Model Context Protocol turned AI assistants into API clients: give Claude or Cursor an MCP server and they can call real tools instead of just talking about them. Meeting BaaS ships an open-source MCP server that exposes the whole meeting stack — so "record my 3pm call and pull the action items afterwards" becomes something your assistant can actually do.

MCP server + meeting bot API = an assistant that attends meetings for you. No custom integration code — the tools are already defined.

What the server exposes

The MCP server maps the Meeting BaaS API onto tools an assistant can call:

  • Meetings: createBot sends a recording bot to any Zoom, Google Meet or Microsoft Teams URL; getMeetingData and getRecordingStatus track it
  • Transcripts: getMeetingTranscript fetches the speaker-attributed transcript; findKeyMoments locates the segments worth replaying
  • Calendars: setupCalendarOAuth, listUpcomingMeetings, scheduleRecording and cancelRecording automate recording from the calendar instead of per-meeting URLs
  • Sharing: shareableMeetingLink and shareMeetingSegments produce links to full recordings or specific moments

That's the practical difference between a chatbot that knows about your meetings and an agent that operates them.

Setup for Claude Desktop

Clone the repo, run npm install && npm run build, then register the server in claude_desktop_config.json with your API key (self-serve at auth.meetingbaas.com, first 8 recording hours free). The example below is macOS/Linux; on Windows, swap the command/args for your shell of choice (e.g. cmd /c or PowerShell) or set MEETING_BAAS_API_KEY as an environment variable instead of the header:

{
  "mcpServers": {
    "meetingbaas": {
      "command": "/bin/bash",
      "args": [
        "-c",
        "cd /path/to/meeting-mcp && (npm run build 1>&2) && export MCP_FROM_CLAUDE=true && node dist/index.js"
      ],
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Cursor and other MCP clients use the same server with their own registration syntax.

What you can build on top

  • Meeting-aware coding agents: Cursor pulls the transcript of the architecture call before writing the migration it discussed
  • Chat-driven recording: "send a bot to this meeting link" from any MCP client — no dashboard visit
  • Post-meeting workflows: assistants that fetch transcripts, extract decisions and file the follow-ups, using findKeyMoments to cite the exact timestamps
  • Speaking agents: pair with the speaking-bots-mcp server and the assistant doesn't just read meetings — it attends and talks

Under the hood

Every MCP tool calls the same meeting bot API available directly: 1 token per recorded hour with speaker diarization included, transcription from six providers, real-time streaming when the agent needs live data.

Next steps

Similar blogstutorial