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

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

How do I install Meetbot MCP or Google Workspace 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 Workspace MCP free or paid?

Meetbot MCP operates under a Freemium model (API Key required). Google Workspace MCP operates under a Free / Open Source 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 Workspace MCP lists 6 tools with 1 views and 3,145 GitHub stars.

Can I use both Meetbot MCP and Google Workspace 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 Workspace MCP

In-depth architectural comparison of the Meetbot MCP and Google Workspace 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: 51/100 (Good) | Auth: API Key required

Google Workspace MCP

Workplace & Productivity · Local stdio

Quality: 59/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 Workspace 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 Workspace 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 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI, WORKSPACE_MCP_LOG_LEVEL, WORKSPACE_MCP_PORT, WORKSPACE_MCP_HOST.

Feature & Specification Comparison

Specification	Meetbot MCP poolside-ventures Workplace & Productivity	Google Workspace MCP taylorwilsdon 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.	Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.
Category & Scope

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 Workspace MCP Tools (6)

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 Workspace MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "taylorwilsdon-google-workspace-mcp": {
      "command": "uvx",
      "args": [
        "workspace-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "GOOGLE_OAUTH_REDIRECT_URI": "YOUR_GOOGLE_OAUTH_REDIRECT_URI_HERE",
        "WORKSPACE_MCP_LOG_LEVEL": "YOUR_WORKSPACE_MCP_LOG_LEVEL_HERE",
        "WORKSPACE_MCP_PORT": "YOUR_WORKSPACE_MCP_PORT_HERE",
        "WORKSPACE_MCP_HOST": "YOUR_WORKSPACE_MCP_HOST_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

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