MeetingBurner

io.github.phoneburnerPublished by GitHub account phoneburnerv0.1.0Updated Oct 31, 2026

Join a live MeetingBurner meeting as a disclosed agent: read it as it happens and add to it.

The publisher's own server: Meeting.ai

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

MeetingBurner MCP lets an assistant join a live MeetingBurner meeting as a disclosed agent, reading the meeting as it happens and adding to it.

What you can do
  • Join a live MeetingBurner meeting as a disclosed agent.
  • Read the meeting as it happens.
  • Add contributions to the meeting.
  • No individual tools are listed in the manifest, so the exact actions are not documented here.
When to use it
Use it when you want an assistant to sit in on an active MeetingBurner session, follow what is being said, and contribute during the meeting rather than afterwards.
Requirements
Runs as a local process over stdio, installed from the npm package meetingburner-mcp, so a Node.js environment is needed. Requires a MeetingBurner API key supplied in the MEETINGBURNER_API_KEY environment variable, created in MeetingBurner Settings under Developer. An optional MEETINGBURNER_ROOM_ID can set a default meeting to join. Desktop only.
Before you install
The API key in MEETINGBURNER_API_KEY is a secret and grants access to your MeetingBurner account; keep it out of shared configuration. The server can add to a live meeting, so its output is visible to other participants. Joining is described as disclosed, but confirm participants know an agent is present.

Installation

In SourceWeft

  1. Open MeetingBurner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.0LatestOct 31, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Meeting integrations