What is the key difference between Meetbot MCP and Google Calendar MCP?

Meetbot MCP belongs to the Workplace & Productivity category with local stdio execution, while Google Calendar MCP belongs to the Workplace & Productivity category with local stdio execution.

How do I install Meetbot MCP or Google Calendar MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Meetbot MCP and Google Calendar MCP free or paid?

Meetbot MCP operates under a Freemium model (API Key required). Google Calendar MCP operates under a BYOK (Pay Provider Direct) model (OAuth 2.0).

Which MCP server has more tools and community activity?

Meetbot MCP lists 6 tools with 2 views and 1 GitHub stars. Google Calendar MCP lists 3 tools with 2 views and 59 GitHub stars.

Can I use both Meetbot MCP and Google Calendar MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Meetbot MCP vs Google Calendar MCP

In-depth architectural comparison of the Meetbot MCP and Google Calendar MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Meetbot MCP

Workplace & Productivity · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Google Calendar MCP

Workplace & Productivity · Local stdio

Quality: 55/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Meetbot MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Google Calendar MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Meetbot MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: MEETBOT_AUTH_TOKEN, PORT.
Primary tools included: Full Meet.bot Booking Page API v1 coverage, Bearer token authentication for API access, Supports local stdio and remote HTTP/SSE modes.

Explore Meetbot MCP Details

Choose Google Calendar MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
You have access to required keys: .

Feature & Specification Comparison

Specification	Meetbot MCP poolside-ventures Workplace & Productivity	Google Calendar MCP takumi0706 Workplace & Productivity
Summary	Meet.bot: scheduling for AI agents. Check real calendar availability and book meetings on connected Google/Microsoft calendars. Pay per meeting booked, not per seat.	An MCP server to interface with the Google Calendar API. Based on TypeScript.
Category & Scope	Workplace & Productivity

Tools & Capabilities Breakdown

Meetbot MCP Tools (6)

Full Meet.bot Booking Page API v1 coverage

Bearer token authentication for API access

Supports local stdio and remote HTTP/SSE modes

Webhook management with JWT-signed event payloads

Health check endpoint for API connectivity

TypeScript support with runtime input validation

Google Calendar MCP Tools (3)

event

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Meetbot MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "poolside-ventures-meetbot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meetbot/mcp"
      ],
      "env": {
        "MEETBOT_AUTH_TOKEN": "YOUR_MEETBOT_AUTH_TOKEN_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

Google Calendar MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "takumi0706-google-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@takumi0706/google-calendar-mcp@2.0.0"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "GOOGLE_REDIRECT_URI": "YOUR_GOOGLE_REDIRECT_URI_HERE",
        "TOKEN_ENCRYPTION_KEY": "YOUR_TOKEN_ENCRYPTION_KEY_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

Meetbot MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Google Calendar MCP belongs to Workplace & Productivity using local stdio subprocess. Select Meetbot MCP when you need capabilities focused on workplace & productivity and Google Calendar MCP when you require tools for workplace & productivity.

More alternatives to Meetbot MCP More alternatives to Google Calendar MCP Workplace & Productivity category hub