huddle-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| request_meetingA | Queue a request for the user instead of interrupting them. Returns a ticketId; poll |
| check_responseC | Poll a ticketId. When |
| cancel_requestB | Cancel a queued ticket you no longer need (e.g. you resolved it yourself). |
| plan_meetingsA | Group all newly-queued tickets by urgency into proposed meetings (pure — books nothing). Returns every unbooked meeting with desiredWindow, durationMinutes and briefingMarkdown so you can find a slot via the calendar MCP and then call |
| confirm_meetingA | After you create the calendar event, record it here. Marks the meeting booked and its tickets scheduled. |
| get_briefingC | Return the rendered agenda for a meeting (use as the calendar event description, or to re-read at review time) plus its full tickets. |
| resolveA | Record the user's answer/decision for a ticket. Flips it to answered so the waiting worker unblocks on its next |
| list_agendaB | Overview of tickets and meetings. Optionally filter tickets by status (queued | scheduled | answered | cancelled). |
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 8 tools
Each tool serves a distinct purpose: cancel_request, check_response, confirm_meeting, get_briefing, list_agenda, plan_meetings, request_meeting, and resolve all have clearly different functions with no overlap. An agent can easily select the correct tool.
Most tools follow a verb_noun pattern (e.g., cancel_request, confirm_meeting), but 'resolve' is a single verb, slightly breaking the pattern. The naming is otherwise consistent and readable.
With 8 tools, the server covers the ticket-based meeting workflow without being too few or excessive. Each tool earns its place in the domain.
The tool set covers the full lifecycle: requesting, cancelling, planning, confirming, polling, resolving, and listing. External calendar integration is explicitly delegated, leaving no dead ends.