ChatterBox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATTERBOX_API_KEY | Yes | Your ChatterBox API key obtained after registration | |
| CHATTERBOX_API_ENDPOINT | No | The ChatterBox API endpoint URL | https://api.chatter-box.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| joinMeetingB | Join a Zoom, Google Meet, or Microsoft Teams meeting using the provided meeting ID and password and capture transcript and audio recording |
| getMeetingInfoC | Get information about a meeting |
| summarizeMeetingB | Generate a concise summary of a meeting's contents from its transcript |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.