Meeting Bot Mcp Server

@rexposadas

About Meeting Bot Mcp Server

Attendee is an open source API for meeting bots on platforms like Zoom or Google Meet. Bring meeting transcripts and recordings into your product in days instead of months.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "attendee": {
      "command": "node",
      "args": [
        "<path>/attendee-mcp/dist/index.js"
      ],
      "env": {
        "MEETING_BOT_API_URL": "<attendee-url-here>",
        "MEETING_BOT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Meeting Bot Mcp Server?

Meeting Bot Mcp Server is a Model Context Protocol (MCP) server for managing Attendee meeting bots. It lets you create, manage, and retrieve transcripts from meeting bots through Claude Desktop, integrating with Zoom, Google Meet, and Teams.

How to use Meeting Bot Mcp Server?

Clone the repository, install dependencies with npm install, build with npm run build, and set the environment variables MEETING_BOT_API_URL and MEETING_BOT_API_KEY. Configure Claude Desktop’s claude_desktop_config.json to include the attendee MCP server. Start the Attendee backend locally, then use natural language commands in Claude Desktop (e.g., “Send a bot to this meeting: ”).

Key features of Meeting Bot Mcp Server

Create and send bots to Zoom, Google Meet, or Teams meetings
Get bot status and list all active bots
Remove a bot from a meeting
Make the bot speak via text-to-speech
Send chat messages through the bot
Display images and play videos (Google Meet only)
Retrieve transcripts, chat messages, and recording download URLs
Delete all data for a bot

Use cases of Meeting Bot Mcp Server

Send a bot to automatically record and transcribe a meeting
Have the bot speak information or send chat messages during a meeting
Retrieve meeting transcripts and recordings for later review
Combine with other MCPs (e.g., Brave Search) to fetch live data and have the bot speak it

FAQ from Meeting Bot Mcp Server

How does Meeting Bot Mcp Server differ from the Attendee backend?

It provides an MCP interface to control Attendee meeting bots directly from Claude Desktop, abstracting the backend API.

What are the runtime requirements?

Node.js, npm, and a running Attendee backend service. Environment variables must be set for the API URL and API key.

Where does meeting data live?

Data is stored on the Attendee server. You can permanently delete recordings, transcripts, and other data using the delete_bot_data tool.

What are the known limitations?

Image and video display features work only on Google Meet. The “list all active bots” tool is listed as both a to-do item and an implemented tool in the README.

What transport and authentication does the server use?

It communicates with the Attendee server over HTTP, authenticated via an API key set in the MEETING_BOT_API_KEY environment variable. The MCP server runs locally as a Node.js process.

Frequently asked questions