Attendee MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_meeting_botC | Create a bot to join a meeting and record/transcribe it |
| get_bot_statusC | Get the current status of a meeting bot |
| get_meeting_transcriptC | Get the transcript from a meeting bot |
| remove_meeting_botC | Remove a bot from a meeting |
| make_bot_speakC | Make a bot speak text during a meeting using text-to-speech |
| send_chat_messageC | Send a chat message from the bot to the meeting |
| get_chat_messagesC | Get chat messages from the meeting |
| get_recordingC | Get the recording URL for a bot |
| send_image_to_meetingC | Send an image to the meeting through the bot (Google Meet only) |
| send_video_to_meetingC | Send a video to the meeting through the bot (Google Meet only) |
| delete_bot_dataC | Delete all data associated with a bot (recordings, transcripts, etc.) |
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 11 tools
Every tool has a clearly distinct purpose focused on specific meeting bot operations. There is no overlap between actions like creating bots, deleting data, getting status/transcripts/recordings, controlling bot speech/chat, or sending media. The descriptions make each tool's unique function immediately apparent.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is perfectly uniform, using clear action verbs like create, delete, get, make, remove, and send paired with specific nouns describing the operation's target.
With 11 tools, the server provides comprehensive coverage for meeting bot management without being overwhelming. This count is well-scoped for the domain, offering a complete set of operations for bot lifecycle, data retrieval, and interaction capabilities.
The toolset offers complete CRUD/lifecycle coverage for meeting bots: creation, status monitoring, data retrieval (transcripts, recordings, chats), interaction (speaking, messaging, media sharing), and removal/deletion. There are no obvious gaps, and agents can perform all essential meeting bot workflows seamlessly.