Meet.bot
Connect to the Meet.bot MCP server at https://mcp.meet.bot using a Bearer token.
Auth
Every tool call requires Authorization: Bearer <api-key> in the HTTP header. If not configured, the server returns a clear error explaining this. Ask the user for their Meet.bot API key before proceeding.
Tools
| Tool | Purpose |
|---|---|
get_scheduling_pages |
List all the user's scheduling pages |
get_page_info |
Get details about a specific page by URL |
get_available_slots |
Find open time slots for a page |
book_meeting |
Book a slot (requires page, guest_email, guest_name, start) |
health_check |
Verify the API key is valid |
Workflows
Check availability
get_scheduling_pagesto list pages (or use URL directly if known)get_available_slotswith the page URL, date range, and user's timezone- Present slots in readable local time — not raw ISO strings
Book a meeting
- Confirm page URL, guest name, guest email, and start time with the user
book_meeting— start time must be ISO 8601 (e.g.2026-03-10T14:00:00Z)- Confirm the booking details back to the user
Share a booking link
get_available_slotswithbooking_link: true- Return the first 3–5
booking_linkURLs for the guest to self-select
Tips
- Pages with "archived" in the URL are inactive — skip them
- Always confirm before calling
book_meeting— bookings cannot be cancelled via this server get_available_slotssupportscount,start,end(YYYY-MM-DD), andtimezone(IANA)