Meetbot
Server Configuration
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. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
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