Schema | Meetbot

Meetbot

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MEETBOT_AUTH_TOKEN`	Yes	Your Meet.bot API bearer token for authentication.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
get_scheduling_pagesB	Get all scheduling pages for the authenticated user
get_page_infoC	Get information about a specific scheduling page
get_available_slotsB	Get available booking slots for a scheduling page
book_meetingC	Book a new meeting slot
health_checkA	Check if the Meet.bot API client is properly configured and can connect
list_webhooksA	List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)
set_webhookA	Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS256) JSON payload to the URL on each booking event.
delete_webhookB	Delete one of the authenticated user's webhooks by id

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/poolside-ventures/meetbot-mcp'

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