Skip to content
Agent Search Engine.
Submit a tool
Menu

Record · google-worksMCP serverCosts not checkedRecord checked Sep 23, 2026

Google Workspace MCP Server

Natural-language control of Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Tasks, Contacts and Chat.

Visit Google Workspace MCP Server →View repository

Sources and review

Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.

Best for

Assistants that need to read and act across a whole Google Workspace, or a team hosting one shared server.

Avoid if

You can't create Google OAuth client credentials; the server requires a client ID and secret.

About Google Workspace MCP Server

This community Google Workspace MCP server covers Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts and Chat, with fine-grained editing tools and tool tiers to limit how many tools load. It supports OAuth 2.1 with multi-user and stateless deployment for central hosting, works with free Google accounts and Workspace plans, and includes a CLI.

Google Workspace MCP Server is listed in this index written primarily in Python, with 3.5k stars on GitHub. Its latest recorded repository push was in October 2026; that is not an ASE editorial review date.

Before connecting: access and data

This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.

  • List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
  • Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
  • Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
  • Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.

Read the setup guide →

Add Google Workspace MCP Server to your MCP client

Generated from the launch command in the project's README. Your client starts the server on demand. Replace <client-id> and <client-secret> with your own values first.

Claude CodeRun in your terminal
claude mcp add google-workspace-mcp -e 'GOOGLE_OAUTH_CLIENT_ID=<client-id>' -e 'GOOGLE_OAUTH_CLIENT_SECRET=<client-secret>' -- uvx workspace-mcp --tool-tier core
Cursor~/.cursor/mcp.json or .cursor/mcp.json
{
  "mcpServers": {
    "google-workspace-mcp": {
      "command": "uvx",
      "args": ["workspace-mcp", "--tool-tier", "core"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_ID": "<client-id>",
        "GOOGLE_OAUTH_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "google-workspace-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["workspace-mcp", "--tool-tier", "core"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_ID": "<client-id>",
        "GOOGLE_OAUTH_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "google-workspace-mcp": {
      "command": "uvx",
      "args": ["workspace-mcp", "--tool-tier", "core"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_ID": "<client-id>",
        "GOOGLE_OAUTH_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.google-workspace-mcp]
command = "uvx"
args = ["workspace-mcp", "--tool-tier", "core"]
env = { GOOGLE_OAUTH_CLIENT_ID = "<client-id>", GOOGLE_OAUTH_CLIENT_SECRET = "<client-secret>" }

Check the project's README for required accounts, keys and permissions before connecting. Setup guide for each client →

For agent buildersMake your product part of the discovery.Explore advertising