Build on the video platform
built for builders

Agent API. MCP server. Token billing. Modern stack.

Get a key from Settings → Developer, then export MEETINGBURNER_API_KEY=mb_your_key_here.

Read API DocsBring Your Voice AgentGet an API Key
quick-start.sh
curl -X POST https://meetingburner.com/api/v1/bots/join \
  -H "X-API-Key: $MEETINGBURNER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "roomId": "room-abc-123",
    "purpose": "Takes notes and flags open questions",
    "capabilities": ["listen", "artifact"]
  }'

# Then read the live, per-speaker-attributed transcript
# over Server-Sent Events — no WebRTC, no SDK:
curl -N -H "X-API-Key: $MEETINGBURNER_API_KEY" \
  "https://meetingburner.com/api/v1/meetings/room-abc-123/stream?connectionId=..."

Why developers choose MeetingBurner

Four features that set us apart from every other video platform

Native Agent API

Bring your own agent into the room over a plain REST API. It joins openly and is always labelled — every participant sees its name, its purpose, and whose key it uses — then reads per-speaker transcription and real-time events.

View Agent API Docs

MCP Server

Put an LLM — Claude Code, Claude Desktop, or any MCP client — into a live meeting. Read the transcript as it happens, write decisions into the record. Coming to npm soon.

MCP Setup Docs

Token-Based Billing

Agent connections are metered per minute against your account balance — transparent, usage-based, and billed the same way as every other participant. No per-seat licensing constraints.

Balance & Usage Docs

Modern Tech Stack

Built on LiveKit (open-source WebRTC), a plain REST API, Server-Sent Events for real-time reads, and webhooks for meeting lifecycle events, signed when you configure a webhook secret.

Full API Reference

Put your LLM in a live meeting

meetingburner-mcp is an MCP server that joins a room as a disclosed agent — it reads the transcript as it happens instead of querying yesterday's notes. One config block, no server to deploy.

Coming to npm soon. The config below runs a build from source, which is not public yet.

Claude Code

cd services/meeting-mcp && npm install && npm run build

claude mcp add meetingburner \
  -e MEETINGBURNER_API_KEY=mb_your_key_here \
  -e MEETINGBURNER_ROOM_ID=your-room-id \
  -- node /absolute/path/to/services/meeting-mcp/dist/index.js

Claude Desktop, or any client reading the standard MCP JSON config

{
  "mcpServers": {
    "meetingburner": {
      "command": "node",
      "args": ["/absolute/path/to/services/meeting-mcp/dist/index.js"],
      "env": {
        "MEETINGBURNER_API_KEY": "mb_your_key_here",
        "MEETINGBURNER_ROOM_ID": "your-room-id"
      }
    }
  }
}

Get an API key at Settings → Developer — full tool reference in the API documentation.

No competitors come close

Built for developers from day one

FeatureZoomGoogle MeetMS TeamsMeetingBurner
Native Agent API⚠️1⚠️2⚠️3✅
Per-Speaker Transcription❌❌❌✅
Token-Based Billing❌❌❌✅
Open-Source Stack❌❌❌✅
Simple API Auth⚠️4⚠️5❌✅
  1. 1. Zoom, Native Agent API: RTMS streams live meeting media and Zoom hosts an MCP server, but neither joins the meeting as a labelled, in-room agent.
  2. 2. Google Meet, Native Agent API: The Media API can consume live audio, video, and participant data, but it is developer preview only.
  3. 3. MS Teams, Native Agent API: Facilitator is a built-in, visible agent, but it requires a Microsoft Copilot license and is not an open, developer-built agent.
  4. 4. Zoom, Simple API Auth: Zoom's APIs authenticate through an OAuth app (Server-to-Server or user-authorized), not a plain API key.
  5. 5. Google Meet, Simple API Auth: The Google Meet REST API needs a Google Cloud project and OAuth consent, not a plain API key.

Ready to start building?

Get your API key in under 60 seconds. No credit card required.

Get Started FreeBrowse Documentation