Meet.bot is a remote MCP server that gives an AI agent 8 tools, among them book_meeting, delete_webhook, get_available_slots. It answers at https://mcp.meet.bot over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
AI-native scheduling and booking: check availability, book meetings, share links.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
book_meeting | Book a new meeting slot Inputs: page, guest_email, guest_name, notes, start |
delete_webhook | Delete one of the authenticated user's webhooks by id Inputs: id |
get_available_slots | Get available booking slots for a scheduling page Inputs: page, count, start, end, timezone, booking_link |
get_page_info | Get information about a specific scheduling page Inputs: 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 | 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. Inputs: id, webhook_url, description, coverage, scope, pages |
Every block below points at https://mcp.meet.bot. Pick your client and copy.
claude mcp add --transport http meet-bot https://mcp.meet.bot
{
"mcpServers": {
"meet-bot": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.meet.bot"]
}
}
}{
"mcpServers": {
"meet-bot": {
"url": "https://mcp.meet.bot"
}
}
}{
"servers": {
"meet-bot": {
"type": "http",
"url": "https://mcp.meet.bot"
}
}
}{
"context_servers": {
"meet-bot": {
"url": "https://mcp.meet.bot"
}
}
}{
"mcpServers": {
"meet-bot": {
"serverUrl": "https://mcp.meet.bot"
}
}
}{
"mcpServers": {
"meet-bot": {
"url": "https://mcp.meet.bot"
}
}
}name: Meet.bot
version: 0.0.1
schema: v1
mcpServers:
- name: Meet.bot
type: streamable-http
url: https://mcp.meet.bot{
"mcpServers": {
"meet-bot": {
"httpUrl": "https://mcp.meet.bot"
}
}
}{
"mcpServers": {
"meet-bot": {
"type": "http",
"url": "https://mcp.meet.bot"
}
}
}{
"mcpServers": {
"meet-bot": {
"url": "https://mcp.meet.bot"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.meet.bot&type=streamable_http&id=meet-bot&name=Meet.bot
It answered our last check on 17 October 2026 in 223 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by meet.bot and served from mcp.meet.bot, the vendor's own domain: https://mcp.meet.bot.
8, as returned by the server's own tools/list on 9 September 2026: book_meeting, delete_webhook, get_available_slots, get_page_info, get_scheduling_pages, health_check, list_webhooks, set_webhook.
It answered our last check on 17 October 2026 in 223 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.meet.bot. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: bot.meet. Endpoint host: mcp.meet.bot. ARD identifier: urn:air:bot.meet:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.