Skip to content

Build AI agents that
sit in live meetings.

A plain HTTP Bot API: one key from Settings, one POST to join, and a per-speaker transcript streamed back as people speak. No SDK to install.

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

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=..."

Set up with your coding agent

Run the install line, or paste the prompt into Claude Code, Cursor or Codex. Set MEETINGBURNER_API_KEY in your shell first; the prompt never asks for the key in chat.

Install (Claude Code)
claude mcp add meetingburner -e MEETINGBURNER_API_KEY="$MEETINGBURNER_API_KEY" -- npx -y meetingburner-mcp@0.1.0
Prompt for your coding agent
Set up the MeetingBurner MCP server and prove it works by joining a test meeting.

1. Install the MCP server "meetingburner" in your MCP config. It is a stdio server run with: npx -y meetingburner-mcp@0.1.0
   (Claude Code: claude mcp add meetingburner -e MEETINGBURNER_API_KEY="$MEETINGBURNER_API_KEY" -- npx -y meetingburner-mcp@0.1.0
   Cursor: add it to .cursor/mcp.json. Codex: add it under [mcp_servers.meetingburner] in ~/.codex/config.toml.)
   Use exactly that version; do not install "latest".
2. Give the server the environment variable MEETINGBURNER_API_KEY, read from my shell environment. Do not ask me to paste the key into this chat. If it is not set, stop and tell me to run: export MEETINGBURNER_API_KEY=mb_... with a key from https://meetingburner.com/settings/developer
3. Join a test meeting: call create_meeting with the name "Agent setup test" and give me the link, and tell me to open it right away, because an unused room ends after 5 minutes. If create_meeting is refused for a missing scope, ask me for a meeting link instead and use the last part of it as the room id.
4. Wait for me to join the meeting (an agent may only join while I am there), then call join_meeting with the purpose "Setup test: checking the connection".
5. Call who_is_here, post one chat message with post_chat_message saying the connection works, then call leave_meeting.
6. Tell me what happened at each step. Docs: https://meetingburner.com/developers.md and https://meetingburner.com/llms.txt

What you get with an API key.

A disclosed agent API, an MCP server, per-minute token billing, and the stack underneath.

  • 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 with one config block. Read the transcript as it happens, write decisions into the record, no server to deploy.

    MCP Setup Docs
  • Token-Based Billing

    Agent connections are metered per minute against your account balance, at a lower rate than a person’s, and an agent that only writes uses less than one that speaks. 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 the endpoint is registered in Settings with a webhook secret; a join-time webhookUrl is not signed).

    Full API Reference

Connect an MCP client to 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.

Claude Code

claude mcp add meetingburner \
  -e MEETINGBURNER_API_KEY=mb_your_key_here \
  -- npx -y meetingburner-mcp@0.1.0

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

{
  "mcpServers": {
    "meetingburner": {
      "command": "npx",
      "args": ["-y", "meetingburner-mcp@0.1.0"],
      "env": {
        "MEETINGBURNER_API_KEY": "mb_your_key_here"
      }
    }
  }
}

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

Your first AI agent in a meeting starts with an invite.

MeetingBurner is in private beta, by invite. No credit card required.