Meet.bot MCP Server

bot.meet/mcp

answering

Meet.bot MCP is answering right now. Last checked 15 min ago. It exposes 8 tools.

AI-native scheduling and booking: check availability, book meetings, share links.

Uptime history 41 hours of history

41 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

235 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.meet.bot

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.meet.bot"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.meet.bot"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.meet.bot"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.meet.bot"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

webhook

delete_webhook

Delete one of the authenticated user's webhooks by id

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 (HS256) JSON payload to the URL on each booking event.

available

get_available_slots

Get available booking slots for a scheduling page

book

book_meeting

Book a new meeting slot

health

health_check

Check if the Meet.bot API client is healthy and the Bearer token is valid

page

get_page_info

Get information about a specific scheduling page

scheduling

get_scheduling_pages

Get all scheduling pages for the authenticated user

webhooks

list_webhooks

List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.meet.bot	streamable-http	answering	224 ms	15 min ago

Meet.bot MCP — questions

Answers built from our own checks of this server.

What can Meet.bot MCP do?

It exposes 8 tools, read directly from the server on our last check. Among them: book_meeting, delete_webhook, get_available_slots, get_page_info, get_scheduling_pages, health_check and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Meet.bot MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 235 ms. The bar chart above shows every period we have measured.

How do I connect Meet.bot MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Meet.bot MCP need an API key?

No. Meet.bot MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Meet.bot MCP?

It answers our handshake in 235 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.