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 |
| list_meeting_botsB | List all active meeting bots |
| 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 12 tools
Every tool has a clearly distinct purpose focused on specific meeting bot operations, with no overlap. For example, create_meeting_bot, get_bot_status, and remove_meeting_bot handle bot lifecycle, while get_chat_messages, send_chat_message, and get_meeting_transcript manage communication and transcription separately.
All tools follow a consistent verb_noun pattern with snake_case, such as create_meeting_bot, get_bot_status, and send_chat_message. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 12 tools, the server is well-scoped for managing meeting bots, covering creation, status monitoring, data retrieval, communication, and cleanup. Each tool serves a specific function without redundancy, making the count appropriate for the domain.
The tool set provides complete CRUD/lifecycle coverage for meeting bots, including creation (create_meeting_bot), monitoring (get_bot_status, list_meeting_bots), interaction (send_chat_message, make_bot_speak), data access (get_recording, get_meeting_transcript), and deletion (remove_meeting_bot, delete_bot_data). No obvious gaps exist for the stated purpose.