mcp server
Meet.bot MCP
AI-native scheduling and booking: check availability, book meetings, share links.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
slowing — Registry entry last updated 2026-03-05.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
book_meeting(page, notes, start, guest_name, guest_email)- Book a new meeting slot Required: page, guest_email, guest_name, start.
delete_webhook(id)- Delete one of the authenticated user's webhooks by id Required: id.
get_available_slots(end, page, count, start, timezone, booking_link)- Get available booking slots for a scheduling page Required: page.
get_page_info(page)- Get information about a specific scheduling page Required: page.
get_scheduling_pages- Get all scheduling pages for the authenticated user
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(id, pages, scope, coverage, is_active, description, webhook_url)- 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.
Last successful function declaration observed on . Source: https://mcp.meet.bot. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.meet.bot.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.meet.bot | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | mcp.meet.bot |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json