AI-native scheduling and booking: check availability, book meetings, share links. Connect the official Meet.bot MCP MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http meet-bot-mcp https://mcp.meet.botRun in your terminal, then restart Claude Code.
Meet.bot MCP · https://mcp.meet.bot
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “get_scheduling_pages”: Get all scheduling pages for the authenticated user.”
“Use “get_page_info”: Get information about a specific scheduling page.”
“Use “get_available_slots”: Get available booking slots for a scheduling page.”
“Use “book_meeting”: Book a new meeting slot.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Meet.bot MCP holds up.
Operated by Meet.bot MCP (meet.bot) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Meet.bot MCP adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Meet.bot MCP in the gate directory. No sign-in needed.
Meet.bot MCP's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
get_scheduling_pages — Get all scheduling pages for the authenticated user
get_page_info — Get information about a specific scheduling page
get_available_slots — Get available booking slots for a scheduling page
book_meeting — Book a new meeting slot
health_check — Check if the Meet.bot API client is healthy and the Bearer token is valid
list_webhooks — List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)
set_webhook — Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS25
delete_webhook — Delete one of the authenticated user's webhooks by id
https://mcp.meet.botYes — Meet.bot MCP operates its own remote MCP server at mcp.meet.bot. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Meet.bot MCP in the directory. No account or sign-in is needed. From then on, Meet.bot MCP's tools are available in every client you've connected to gate.
No. Meet.bot MCP runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Meet.bot MCP in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Meet.bot MCP in: Claude · Claude Code · ChatGPT · Cursor · VS Code