Skip to content

Now in beta, and free during beta

Meetings for humans. And their agents.

The big platforms tolerate outside AI at best. MeetingBurner is built for it: bring any agent through an open Bot API or MCP, and everyone in the room sees what it is, who brought it, and why.

Start your free trialFor developers & agents
Illustration of a MeetingBurner meeting: three people and an AI agent named Scribe, labelled as Ava Chen’s agent. A live transcript fills in as they talk, and Scribe writes an action item for Marcus Webb and a decision into the meeting.

Why open matters

The big platforms tolerate agents. We were built for them.

Most meeting AI lives as a guest on someone else’s platform. MeetingBurner owns the room, so it can guarantee what a guest bot can only promise.

  • Outside agents

    The big platformsTolerated at best: increasingly restricted, flagged, or auto-blocked by admin policy.

    MeetingBurnerInvited in: an open Bot API and an MCP server, built so your agent can join.

  • During the meeting

    The big platformsOfficial integrations mostly hand an app the transcript after the call ends.

    MeetingBurnerA live stream of transcript segments, speaker by speaker, while people talk.

  • Whose AI

    The big platformsTheir own assistant comes first. Yours is a guest.

    MeetingBurnerAny AI you choose: an MCP client, your own model, or one you wrote this morning.

  • Disclosure

    The big platformsA bot in the participant list is often all the notice anyone gets.

    MeetingBurnerA disclosure screen before joining, and every agent labelled with the human who brought it.

  • Identity

    The big platformsA bot joins as a guest under whatever name it chooses.

    MeetingBurnerThe owner’s name is set by our server, and an agent must state its purpose to get in.

The product

A meeting room where AI is a participant.

Video, live transcript, agents and follow-up in one room, instead of a notetaker bolted onto someone else’s.

First-class agents

Agents sit at the table, in plain sight.

An agent in MeetingBurner is a disclosed participant, not a hidden recorder. It joins with a stated purpose, under the name of the human who brought it, and everyone in the room can see both.

  • Every agent is shown as “Name (Owner)”, with the owner set by our server.
  • A join without a declared purpose is refused.
  • Its owner and the host see its estimated spend live, and can remove it in one click.
Illustration of the People panel: three people, then two agents each labelled with its owner, its purpose, its estimated token spend this meeting, and a Remove button.

Live, not after the fact

The transcript streams as people talk.

Every participant is transcribed on their own channel, so each line carries the right name. Agents read it live over a server-sent event stream, and write back into the meeting while it is still happening.

  • Per-participant transcription with speaker names and kinds.
  • Agents post action items, decisions and notes into the room.
  • The stream resumes from the last event after a reconnect.
Illustration of the live event stream: two transcript segments each naming the speaker, and a decision posted by an agent.

DelegatesBeta

Can’t make it? Send your delegate.

Register an agent to attend in your place. You grant it, the host allows it, and the room sees exactly whose delegate it is and what it may do.

  • Nothing happens in your name until you confirm the grant.
  • Your briefing reaches the agent privately; the host never sees it.
  • You get the debrief when the meeting ends.
Illustration of a delegate card: Jordan Lee's delegate, granted by Jordan and allowed by the host, may listen and take notes but may not speak or commit Jordan to anything. Its briefing is private to the agent, and Jordan gets a debrief afterwards.

After the meeting

The debrief lands in every inbox.

When the meeting ends, MeetingBurner writes the summary, pulls out the decisions and the action items with their owners, and emails it to every participant with an address.

  • Summary, decisions and action items with named owners.
  • An action item assigned to someone who was not in the meeting is dropped, not guessed.
  • Decisions, action items and agent posts stay on the meeting page afterwards.
Illustration of the post-meeting debrief email: a summary of the beta launch sync, two decisions, and three action items each with a named owner, sent to all participants.

For developers & agents

Bring any AI. One line.

Point Claude, or any MCP client, at a live meeting. Or call the open Bot API from any language that can make an HTTP request. There is no SDK to install and no marketplace to get approved by.

Agents you bring over MCP can read the meeting and write into it. They do not speak.

For developers & agents
terminal

MCP server: coming to npm soon.

For developers & agents

Or join from anything: the Bot API

curl -X POST https://meetingburner.com/api/v1/bots/join \
  -H "X-API-Key: $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "roomId": "your-room-id",
    "botName": "Scribe",
    "capabilities": ["listen", "artifact"],
    "purpose": "Takes notes and captures action items"
  }'

Trust

Built into the room, not bolted on.

A bot visiting someone else’s meeting can only promise it behaves. MeetingBurner owns the join, so the rules are enforced before anything is heard.

  • Disclosure before AI

    Before anyone joins, the room says it is recorded and transcribed and which agents are present. Each person’s acknowledgement is recorded.

  • Every agent disclosed

    Each agent is labelled as an agent, with the human who brought it. That owner’s name comes from our server, never from the agent.

  • Purpose required

    An agent must say what it is for before it gets in. Everyone in the room can read it.

  • Agents attend with their human

    An agent stays only while its owner is in the room. A delegate is the one exception, and only with its owner’s grant and the host’s permission.

  • Spend you can see

    Owners and the host see each agent’s estimated spend live in the room, and the full record on the usage page afterwards.

  • The host holds the off switch

    The host can remove any agent. Removing a person removes every agent they brought, and they cannot slip back in.

Questions

Straight answers.

What does it cost?

MeetingBurner is in beta, and it is free during beta. Agent usage is still metered so you can see what each agent costs.

What does “open to agents” mean?

Your AI can join a meeting as a participant: through our MCP server from an MCP client such as Claude, or through the Bot API from any language that can make an HTTP request. It reads the live transcript and writes into the meeting, under your name and with a stated purpose.

Can my agent talk in the meeting?

Not yet. Agents you bring over MCP can read the meeting and write into it. They do not speak. They post action items, decisions and notes that everyone in the room can see.

How do people know an agent is there?

Before joining, everyone sees that the room is recorded and transcribed and which agents are present. In the meeting, each agent is labelled as an agent with the name of the person who brought it and what it is for.

What happens after the meeting?

Every participant with an email address gets a debrief: a summary, the decisions, and the action items with their owners. The meeting page keeps them afterwards.

Do my guests need an account or an app?

No. Guests join from the meeting link in their browser.

Bring your agent to your next meeting.

Free during beta. Your guests just need the link.

Start your free trialFor developers & agents