Using the Meet.bot MCP (Model Context Protocol)

The Meet.bot MCP server lets AI assistants (such as Claude, ChatGPT, or any assistant supporting the Model Context Protocol) interact directly with your Meet.bot scheduling pages.

This means you can fetch availability, show booking options in conversation, and even book meetings automatically through an AI workflow, without needing to build a custom integration from scratch. The MCP is available on all plans, including the free plan.

This articles covers the use cases and high level setup. More detailed information is included in the README.md file in the npm package.

What You Can Do with the MCP

With the MCP server, an AI assistant can:

1. List Your Scheduling Pages

• Retrieve all scheduling pages linked to your account.

• Lets the AI suggest the right page type (e.g., “30‑minute intro call”).

2. Show Availability in Conversation

• Look up available slots on a scheduling page.

• Filter by date, limit results, and choose a timezone.

• Optionally return booking links to share directly in chat.

3. Book a Meeting Automatically

• Confirm a booking with guest details (name, email, chosen slot).

• Add notes that appear in the calendar invite.

4. Get Page Details Before Offering Slots

• Fetch metadata about a scheduling page (title, duration, owner, booking window).

• Ensures the right meeting type is offered to a customer.

5. Run Health Checks

• Verify that the Meet.bot API connection is live.

• Useful for testing during setup.

Authentication

Both local and remote deployments use the same Meet.bot API token:

1. Get your API token from https://meet.bot/automation
2. Use it as a Bearer token in the Authorization header
3. The same token can authenticate both the MCP server and Meet.bot API calls

Hosted Deployment

You can now connect to a hosted MCP server instead of running it locally (scroll further down for instructions to run locally).

Public endpoint

- URL: https://mcp.meet.bot
- Transport: HTTP/SSE
- Authentication: Bearer token required (your API token)

Configuration for AI Assistants

```json
{
  "mcpServers": {
    "meetbot": {
      "url": "https://mcp.meet.bot/sse",
      "headers": {
        "Authorization": "Bearer YOUR_MEETBOT_API_TOKEN"
      }
    }
  }
}
```

Local Installation

You can also install the MCP server just like any other Node.js package:

npm install @meetbot/mcp      

Or install globally for CLI usage

npm install -g @meetbot/mcp

Using as an MCP Server

You can run the server directly with npx:

npx @meetbot/mcp   

Or, if installed globally:

meetbot-mcp

The server requires configuration with your Meet.bot API endpoint and a Bearer Token.

Example: Configure with environment variables

export MEETBOT_AUTH_TOKEN="your_bearer_token"
meetbot-mcp   

This launches the MCP server, making Meet.bot scheduling functionality available to any AI assistant that supports MCP.

Using with AI Assistants

Register the Meet.bot MCP server in your assistant’s configuration. For example:

{ "mcpServers": {       
        "meetbot": {
                 "command": "npx",
                 "args": ["@meetbot/mcp"],
                 "env": {
                           "MEETBOT_AUTH_TOKEN": "your_bearer_token_here"
                 }
         }
   }   
}   

Once configured, AI assistants can call Meet.bot’s tools directly:

• get_scheduling_pages – list scheduling pages

• get_page_info – fetch details about a page

• get_available_slots – retrieve upcoming slots (with optional links)

• book_meeting – book a slot for a guest

• health_check – confirm connectivity

Example Scenarios

• Conversational Booking: A customer asks an assistant for a demo → the MCP fetches open slots → booking is completed instantly.

• Support Copilot: During a chat, an assistant suggests times and creates a booking on behalf of a support agent.

• Smart Sales Outreach: The assistant detects buying intent and shares clickable booking links inside the conversation.

Why Use the MCP?

• AI-native scheduling – Designed for use inside conversational AI tools.

• Complete API coverage – Accesses all Meet.bot scheduling & booking endpoints.

• Reliable – Supports authentication and error handling for production use.

👉 Use the MCP server if you want Meet.bot scheduling powered by AI assistants.