Meet.bot
@poolside-ventures
About Meet.bot
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 "sc
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"meetbot": {
"command": "npx",
"args": [
"@meetbot/mcp"
],
"env": {
"MEETBOT_AUTH_TOKEN": "your_bearer_token_here"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Meet.bot?
Meet.bot is a Model Context Protocol (MCP) server that connects AI assistants (Claude, ChatGPT, etc.) to the Meet.bot Booking Page API, allowing them to schedule meetings directly via natural language. It is designed for busy professionals who want to automate meeting booking through their Meet.bot account.
How to use Meet.bot?
Install the npm package (npm install @meetbot/mcp) or run globally. Configure it by providing your Meet.bot API bearer token via the configure_meetbot tool or the MEETBOT_AUTH_TOKEN environment variable. Then ask your AI assistant to schedule meetings – the server will check availability, find time slots, and book them. Run locally via stdio or as an HTTP server with SSE transport.
Key features of Meet.bot
- Complete Meet.bot Booking Page API coverage
- Full TypeScript support with type definitions
- Zod schemas for input validation
- Bearer token authentication
- Dual-mode: local stdio and remote HTTP/SSE
- Production-deployed at https://mcp.meet.bot
Use cases of Meet.bot
- Automate meeting scheduling with an AI assistant
- Check available time slots across scheduling pages
- Book meetings with guest details, notes, and timezone
- Integrate scheduling into AI-powered workflows
- Deploy as a remote team scheduling service
FAQ from Meet.bot
How do I configure the Meet.bot server?
Set the MEETBOT_AUTH_TOKEN environment variable or pass an authToken parameter to the configure_meetbot tool.
What transport modes are supported?
Local stdio mode (for desktop assistants) and remote HTTP/SSE mode (for cloud deployment on Railway, Fly.io, etc.).
How do I authenticate requests?
All HTTP requests require a Bearer token in the Authorization header. The same token is used to authenticate with the Meet.bot API.
What tools does the MCP server expose?
Six tools: configure_meetbot, get_scheduling_pages, get_page_info, get_available_slots, book_meeting, and health_check.
Is there a production deployment available?
Yes, the server is live at https://mcp.meet.bot (SSE endpoint /sse, health check at /health).
More AI & Agents MCP servers
1Panel
1Panel-dev🔥 1Panel is a modern, open-source VPS control panel — and the only one with native AI agent support. Run Ollama models, deploy OpenClaw agents, and manage your entire server stack from one clean web interface.
MCP Client for Ollama (ollmcp)
joniglHarness the power of local LLMs with this TUI MCP Client for Ollama. Featuring all core MCP primitives (tools, prompts, resources), agent mode, multi-server, model switching, streaming responses, human-in-the-loop, thinking mode, model params config, system prompts, and saved pre
Gemini MCP Server
aliargunMCP server implementation for Google's Gemini API
Model Context Protocol for Unreal Engine
chongdashuEnable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
MCP-NixOS - Because Your AI Assistant Shouldn't Hallucinate About Packages
utensilsMCP-NixOS - Model Context Protocol Server for NixOS resources
Comments