poolside-ventures/meetbot-mcp

A Model Context Protocol (MCP) server for the Meet.bot Booking Page API, enabling AI assistants to interact with scheduling and booking functionality.
What is this?
This MCP server connects AI assistants (like Claude, ChatGPT, and others that support MCP) to your Meet.bot account, allowing them to schedule meetings on your behalf. Instead of manually copying booking links or checking your calendar, you can simply ask your AI assistant to "schedule a 30-minute meeting with John next week" and it will handle the booking through your MeetBot scheduling pages.
**How it works:**
1. Connect your MeetBot API token to the MCP server
2. Configure your AI assistant to use this MCP server
3. Ask your AI assistant to schedule meetings - it can check your availability, find time slots, and book meetings directly through your MeetBot account
This is particularly useful for busy professionals who want to automate meeting scheduling and let their AI assistant manage their calendar intelligently.
If you don't have an account, you can get one for free at https://meet.bot
Features
- **Complete API Coverage**: Implements all endpoints from the Meet.bot Booking Page API v1
- **Type Safety**: Full TypeScript support with comprehensive type definitions
- **Runtime Validation**: Zod schemas for input validation and data integrity
- **Authentication Support**: Bearer token authentication
- **Error Handling**: Robust error handling with detailed error messages
- **Health Checks**: Built-in health monitoring using the /v1/pages endpoint
- **MCP Protocol Compliance**: Full Model Context Protocol server implementation
- **Dual Mode Support**: Run locally (stdio) or remotely (HTTP/SSE)
- **Production Deployed**: Live at https://mcp.meet.bot
- **Production Ready**: Thoroughly tested and validated for production use
Installation
Quick Start
1. Install and Configure
2. Authentication
Authentication is **not** a tool—it is connection-based:
- **HTTP/SSE (remote, e.g. https://mcp.meet.bot)**: Send Authorization: Bearer in the request headers when connecting. The server uses this token for all API calls in that session.
- **Stdio (local)**: Set the MEETBOT_AUTH_TOKEN environment variable when starting the server (e.g. MEETBOT_AUTH_TOKEN=your_token npx @meetbot/mcp).
There is no configure_meetbot or similar tool; the AI uses the tools below and auth is handled by the connection.
3. Use the Available Tools
The MCP server provides the following tools:
Get Scheduling Pages
Get Page Information
Get Available Slots
Book a Meeting
Health Check
Webhooks
Get notified the moment a meeting is booked, rescheduled, or cancelled. Meet.bot POSTs a JWT-signed (HS256) JSON payload — the same contract as the partner webhook — to your URL for each event (booking_received, booking_rescheduled, booking_cancelled).
Deployment Options
The MCP server can be run in two modes:
1. Local Mode (Stdio Transport)
For local integration with AI assistants like Claude Desktop. Uses stdio transport for communication.
2. HTTP Mode (SSE Transport)
For remote deployment with HTTP/SSE transport. This allows the MCP server to be accessed over the network.
Running the HTTP Server
Server Endpoints
- **SSE Endpoint**: GET /sse - Establishes an SSE connection for MCP communication
- **Messages Endpoint**: POST /messages?sessionId= - Receives client messages
- **Health Check**: GET /health - Server health status
Authentication
All requests require a Bearer token in the Authorization header:
The same token is used to authenticate with the Meet.bot API.
Testing the HTTP Server
**Local Testing:**
**Production Testing:**
Deployment
The HTTP server can be deployed to various platforms:
- **Railway**: railway up ✅ **Live at https://mcp.meet.bot**
- **Fly.io**: fly launch && fly deploy
- **Google Cloud Run**: Container-based deployment