Skip to main content
Glama
ChatterBox MCP Server

ChatterBox MCP Server

by ChatterBoxIO

ChatterBox MCP 服务器

铁匠徽章

ChatterBox 的模型上下文协议服务器实现,使 AI 代理能够与在线会议进行交互并生成会议摘要。

概述

ChatterBox MCP 服务器为 AI 代理提供以下工具:

  • 加入在线会议(Zoom 和 Google Meet)

  • 捕获文字记录和录音

  • 生成会议摘要

Related MCP server: Google Meet MCP Server

安装

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 chatterboxio-mcp-server:

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

手动安装

您可以使用 npm 或 pnpm 安装依赖项:

# Using npm
npm install

# Using pnpm
pnpm install

配置

获取 API 密钥

您可以在我们的网站ChatterBox上注册,免费获取 API 密钥。注册后,您将收到 API 端点和密钥。

环境设置

在根目录中创建一个.env文件,其中包含以下变量:

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

用法

启动服务器

npm start

可用工具

加入会议

加入 Zoom 或 Google Meet 会议并获取文字记录和录音。

参数:

  • platform (字符串):在线会议平台(“zoom”或“googlemeet”)

  • meetingId (字符串):会议的ID

  • meetingPassword (字符串,可选):会议密码

  • botName (字符串):机器人的名称

  • webhookUrl (字符串,可选):用于接收会议状态的 webhook 事件的 URL

获取会议信息

获取有关会议的信息,包括会议记录和录音。

参数:

  • sessionId (字符串):获取信息的会话 ID

总结会议

根据会议记录生成会议内容的简明摘要。

参数:

  • transcript (字符串):需要总结的会议记录

发展

先决条件

  • Node.js 16+

  • npm 或 yarn

建筑

npm run build

执照

该项目根据 MIT 许可证获得许可 - 有关详细信息,请参阅LICENSE文件。

支持

如需支持,请访问ChatterBox 文档或联系support@chatter-box.io 。

贡献

欢迎贡献代码!欢迎提交 Pull 请求。

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…

    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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers