# MeetingBurner for developers

> 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`.

## Beta status

Sign-up is invite-only during the private beta. Ask for an invite at support@meetingburner.com, then sign up at https://meetingburner.com/signup with the invited address. An agent cannot create an account or an API key by itself today; a person makes the key in Settings → Developer.

## Quick start

```bash
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

Install the MCP server with one line (Claude Code):

```bash
claude mcp add meetingburner -e MEETINGBURNER_API_KEY="$MEETINGBURNER_API_KEY" -- npx -y meetingburner-mcp@0.1.0
```

Or paste this prompt into Claude Code, Cursor or Codex:

```text
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

### 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.

More: https://meetingburner.com/api-docs#agent-api

### 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.

More: https://meetingburner.com/developers#mcp

### 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.

More: https://meetingburner.com/api-docs#usage

### 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).

More: https://meetingburner.com/api-docs

## MCP server: 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. `MEETINGBURNER_ROOM_ID` is optional; without it, pass a room id to `join_meeting`.

Claude Code:

```bash
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:

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

Full tool list: https://meetingburner.com/api-docs.md (MCP Server section).

## Pricing and plan limits

MeetingBurner is in private beta, by invite, and nothing is charged during it. A beta
account may bring agents until the starter tokens it gets at sign-up run out, and every account with a beta
invite also gets a comped allowance of about 5 hours of agent time.
Rates for after the beta are not yet published on this site.

Free plan: no credit card. Up to
300 meeting minutes a month (people's minutes, pooled), 5 people per meeting,
3 seats, and 10 agents at a time.
At a plan limit a new join is refused. Nothing is charged automatically. Hosting a meeting needs an account. Guests join with the link and a name.
Agent time: 100 starter tokens. An agent that writes uses 1 token a
minute; an agent with a voice uses 10.

Up to 10 agents a meeting, from everyone together, with no per-person cap (a plan may set a smaller allowance).

## Rate limits

- `POST /bots/join`: 5 a minute per account.
- `POST /bots/post-artifact`: 30 a minute per account.
- `POST /bots/post-chat-message`: 10 a minute per account (the MCP `post_chat_message` tool shares this limit).
- `POST /meetings`: 2 a minute per API key, 5 a minute across all of an account's keys, and 50 per API key in any 24 hours.
- `GET /meetings`: 2 a minute per API key.
- `GET /agents/verify`: 60 a minute per caller IP address.

A refused request answers 429 with a `Retry-After` header in seconds. Wait that long, then retry.

## FAQ

### How do I get started with the MeetingBurner API?

MeetingBurner is in private beta, by invite: request one at support@meetingburner.com, then sign up at meetingburner.com/signup with the invited address, navigate to Settings > Developer, and generate your API key. There is no SDK to install — call the Bot API directly with an HTTP client. The MCP server for Claude Code and Claude Desktop, and its config block, are in the MCP section of this page.

### Does MeetingBurner support AI agents?

Yes — natively. Your agent joins through the Bot API as a real, disclosed participant: it declares a purpose at join (a join without one is refused), and every participant sees its name, purpose, and whose agent it is. It can receive per-speaker transcription and room events over a single event stream, and write decisions and action items into the meeting record. Agents are never hidden — that is the point, not a limitation.

### Do you take a cut of what I build?

No. We make money on the room — seats and usage — and a useful agent already drives that. We do not take a revenue share from agents or integrations, and we never resell model inference: bring your own provider key and pay your provider directly.

### What programming languages can I use?

Any language that can make an HTTP request and read a Server-Sent Events stream. There is no SDK to install and none is required. If you would rather connect an LLM to a live meeting than write an agent yourself, see the MCP section of this page.

### How does token-based billing work for developers?

An agent's connection time is charged in tokens to the account that owns its API key, rounded up to whole minutes: 1 token a minute for an agent that only writes, 10 for one that speaks. No per-seat licensing constraints. Nothing is charged during the beta.

## More

- API reference (markdown): https://meetingburner.com/api-docs.md
- Bring your AI voice agent (markdown): https://meetingburner.com/developers/livekit-agents.md
- Index for agents: https://meetingburner.com/llms.txt
- Everything in one file: https://meetingburner.com/llms-full.txt