Skip to main content
Glama
Sign In
enesjakozh
ChatterBox MCP Server

ChatterBox MCP Server

by ChatterBoxIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ChatterBox MCP Server

A Model Context Protocol server implementation for ChatterBox, enabling AI agents to interact with online meetings and generate meeting summaries.

Overview

The ChatterBox MCP Server provides tools for AI agents to:

  • Join online meetings (Zoom, Google Meet, or Microsoft Teams)

  • Capture transcripts and recordings

  • Generate meeting summaries

Related MCP server: Google Meet MCP Server

Installation

Installing via Smithery

To install chatterboxio-mcp-server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @OverQuotaAI/chatterboxio-mcp-server --client claude

Manual Installation

You can install the dependencies using either npm or pnpm:

# Using npm
npm install

# Using pnpm
pnpm install

Configuration

Getting API Keys

You can get your API keys for free by registering on our website at ChatterBox. After registration, you'll receive your API endpoint and key.

Environment Setup

Create a .env file in the root directory with the following variables:

CHATTERBOX_API_ENDPOINT=https://api.chatter-box.io
CHATTERBOX_API_KEY=your_api_key_here

Usage

Starting the Server

pnpm start

Available Tools

joinMeeting

Join a Zoom or Google Meet meeting and capture transcript and audio recording.

Parameters:

  • platform (string): The online conference platform ("zoom", "googlemeet", or "teams")

  • meetingId (string): The ID of the meeting

  • meetingPassword (string, optional): The password or the passcode for the meeting

  • botName (string): The name of the bot

  • webhookUrl (string, optional): URL to receive webhook events for meeting status

getMeetingInfo

Get information about a meeting, including transcript and recording.

Parameters:

  • sessionId (string): The session ID to get information for

summarizeMeeting

Generate a concise summary of a meeting's contents from its transcript.

Parameters:

  • transcript (string): The meeting transcript to summarize

Development

Prerequisites

  • Node.js 16+

  • npm or yarn

Building

pnpm run build

Debugging

To debug the MCP server using the MCP Inspector:

npx @modelcontextprotocol/inspector

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For support, please visit ChatterBox Documentation or contact support@chatter-box.io.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Available Tools

3 tools
getMeetingInfoC

Get information about a meeting

Inputs: sessionId (required).

joinMeetingB

Join a Zoom, Google Meet, or Microsoft Teams meeting using the provided meeting ID and password and capture transcript and audio recording

Inputs: platform (required), meetingId (required), botName (required), meetingPassword, +1 more.

summarizeMeetingB

Generate a concise summary of a meeting's contents from its transcript

Inputs: transcript (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getMeetingInfo retrieves meeting details, joinMeeting handles joining and recording, and summarizeMeeting processes transcripts. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency4/5

    The tools follow a consistent verb_noun pattern (getMeetingInfo, joinMeeting, summarizeMeeting), with minor deviations in capitalization (camelCase). This consistency aids readability and predictability, though the mixed case style is a slight deviation from pure snake_case.

    Tool Count3/5

    With only 3 tools, the server feels thin for a meeting management domain. While the tools cover core actions, additional operations like creating meetings, updating details, or managing participants are missing, suggesting the scope could be expanded for better utility.

    Completeness2/5

    There are significant gaps in the tool surface for meeting management. The server lacks create, update, or delete operations for meetings, and does not include tools for handling participants, scheduling, or notifications. This incompleteness will likely cause agent failures in broader workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Google Meet MCP Server

      cool-man-vk
      A
      license
      Not graded
      quality
      D
      maintenance
      The Google Meet MCP Server enables AI agents to create, manage, and retrieve Google Meet meetings. Built on the Model Context Protocol, it exposes tools for scheduling, updating, and deleting meetings, making it easy to integrate Google Meet functionalities
      11 npm
      2
      MIT

    • Zoom API MCP Server

      allisonwhilden
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP Server that enables interaction with Zoom's API through the Multi-Agent Conversation Protocol, allowing users to access and control Zoom's functionality via natural language commands.
      -