Schema | huddle-mcp

huddle-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

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_response` with it and proceed once answered. Does not touch the calendar.
check_responseC	Poll a ticketId. When `answered` is true, `response` holds the user's decision and you can proceed.
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_meeting`.
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 `check_response`.
list_agendaB	Overview of tickets and meetings. Optionally filter tickets by status (queued \| scheduled \| answered \| cancelled).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marcoloco23/huddle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server