Meet MCP server

Which servers in the official MCP registry are Meet's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Meet

Whose server it is

Registry namebot.meet/mcpverified in the MCP registry

The registry name sits under meet.bot. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools8
Server calls itselfmeetbot-mcp
Server version1.3.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 244 ms.

Tools it offers8 tools · read 2026-10-14

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 (HS256) JSON payload to the URL on each booking event.
delete_webhook
Delete one of the authenticated user's webhooks by id

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.