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

Google Workspace 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 Google Workspace 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 Google Workspace MCP and Google Calendar MCP free or paid?

Google Workspace MCP operates under a Free / Open Source model (OAuth 2.0). Google Calendar MCP operates under a BYOK (Pay Provider Direct) model (OAuth 2.0).

Which MCP server has more tools and community activity?

Google Workspace MCP lists 123 tools with 1 views and 3,179 GitHub stars. Google Calendar MCP lists 3 tools with 2 views and 59 GitHub stars.

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

Google Workspace MCP vs Google Calendar MCP

In-depth architectural comparison of the Google Workspace 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

Google Workspace MCP

Workplace & Productivity · Local stdio

Quality: 67/100 (Great) | Auth: OAuth 2.0

Google Calendar MCP

Workplace & Productivity · Local stdio

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

Verdict Summary: Choose Google Workspace 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 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.
Primary tools included: start_google_auth, search_gmail_messages, get_gmail_message_content.

Explore Google Workspace 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)).

Feature & Specification Comparison

Specification	Google Workspace MCP taylorwilsdon Workplace & Productivity	Google Calendar MCP takumi0706 Workplace & Productivity
Summary	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.	An MCP server to interface with the Google Calendar API. Based on TypeScript.
Category & Scope

Tools & Capabilities Breakdown

Google Workspace MCP Tools (123)

start_google_auth

Manually initiate Google OAuth authentication flow. NOTE: This is a legacy OAuth 2.0 tool and is disabled when OAuth 2.1 is enabled. The authentication system automatically handles credential checks and prompts for authentication when needed. Only use this tool if: 1. You need to re-authenticate with different credentials 2. You want to proactively authenticate before using other tools 3. The automatic authentication flow failed and you need to retry In most cases, simply try calling the Google Workspace tool you need - it will automatically handle authentication if required.

search_gmail_messages

Searches messages in a user's Gmail account based on a query. Returns both Message IDs and Thread IDs for each found message, along with Gmail web interface links for manual verification. Supports pagination via page_token parameter.

get_gmail_message_content

Retrieves the full content (subject, sender, recipients, body) of a specific Gmail message. Bodies are returned inline and truncated at 20,000 characters. Set full=True to get the complete, untruncated message instead: it is exported to disk and the response carries a short-lived download URL (HTTP transport) or file path (stdio transport) rather than the body, so large messages never stream through the model context. Stateless deployments have no file storage, so there full=True returns the untruncated body inline.

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).

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"
      }
    }
  }
}

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

Google Workspace 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 Google Workspace MCP when you need capabilities focused on workplace & productivity and Google Calendar MCP when you require tools for workplace & productivity.

More alternatives to Google Workspace MCP More alternatives to Google Calendar MCP Workplace & Productivity category hub Canonical compare URL