/ Directory / Playground / google-workspace-mcp
← All servers ↗ GitHub
● Community aaronsb ⚡ Instant

google-workspace-mcp

by aaronsb · aaronsb/google-workspace-mcp

Gmail + Calendar + Drive + multi-account management in one MCP, built on Google's official Workspace CLI — 287 operations across 15+ services.

aaronsb/google-workspace-mcp exposes 5 aggregated tools (manage_email, manage_calendar, manage_drive, manage_accounts, queue_operations) that together cover 287+ operations across Google Workspace. Built on Google's official gws CLI with a manifest-driven factory — it's official-adjacent without being first-party.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

google-workspace-2.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "google-workspace-2": {
      "command": "npx",
      "args": [
        "-y",
        "google-workspace-mcp"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "google-workspace-2": {
      "command": "npx",
      "args": [
        "-y",
        "google-workspace-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "google-workspace-2": {
      "command": "npx",
      "args": [
        "-y",
        "google-workspace-mcp"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "google-workspace-2": {
      "command": "npx",
      "args": [
        "-y",
        "google-workspace-mcp"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "google-workspace-2",
      "command": "npx",
      "args": [
        "-y",
        "google-workspace-mcp"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "google-workspace-2": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "google-workspace-mcp"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add google-workspace-2 -- npx -y google-workspace-mcp

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use google-workspace-mcp

Triage your inbox and draft replies

👤 Anyone buried in email ⏱ ~15 min intermediate

When to use: Morning inbox. 200 unread. You want to know what needs a response today.

Prerequisites
  • Google Cloud OAuth client — console.cloud.google.com > Credentials
Flow
  1. Authenticate
    Authenticate my Gmail account via OAuth.✓ Copied
    → OAuth flow completes
  2. Classify
    Go through unread emails from last 24h. Bucket into: urgent reply, FYI, newsletter, spam-like. Count each bucket.✓ Copied
    → Counts + sample subjects per bucket
  3. Draft replies
    For the 'urgent reply' bucket, draft short replies (don't send). Show me drafts for approval.✓ Copied
    → Drafts ready for review

Outcome: 30 minutes of inbox triage in 5.

Pitfalls
  • LLM hallucinates commitments in drafts — Never have it send directly — always draft + human review

Find a meeting slot across 5 attendees

👤 Anyone scheduling meetings ⏱ ~5 min beginner

When to use: You need 45 minutes next week that works for 5 people across time zones.

Flow
  1. Check availability
    Find a 45-min slot next week that works for me + these 4 attendees [emails]. Exclude lunch hours in each TZ.✓ Copied
    → Candidate slots
  2. Create event
    Book the best slot as 'Weekly sync' with a Google Meet link; invite all.✓ Copied
    → Event created with video link

Outcome: Meeting scheduled without the Doodle dance.

Pitfalls
  • Free/busy API only shows free/busy, not priorities — Ask each person before hard-booking optional slots

Audit a Drive folder's sharing permissions

👤 Ops / compliance ⏱ ~30 min intermediate

When to use: Somebody shared a sensitive folder broadly. You want to know exactly who has access.

Flow
  1. Enumerate
    List all files under /Shared drives/Contracts/2025 with their sharing settings. Flag anything with 'anyone with link' or 'public'.✓ Copied
    → File list with exposure flags
  2. Remediate
    For each public file, change to 'restricted' and notify the owner. Show me the diff before executing.✓ Copied
    → Per-file change plan

Outcome: Drive posture improved in one pass.

Pitfalls
  • Revoking may break active external workflows — Announce before revoking; use a grace period

Combinations

Pair with other MCPs for X10 leverage

google-workspace-2 + notion

Mirror Google Docs to Notion weekly

For each Doc created in /Shared/Team this week, export as Markdown and create Notion page in 'Team Docs'.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
manage_email action: 'search'|'read'|'send'|'reply'|'label'|..., ... Any Gmail op 1 Gmail API call
manage_calendar action: 'list'|'create'|'update'|'delete'|'freebusy'|..., ... Any Calendar op 1 Calendar API call
manage_drive action: 'search'|'upload'|'download'|'share'|'export'|..., ... Any Drive op 1 Drive API call
manage_accounts action: 'add'|'remove'|'switch'|'list' Multi-account switching free
queue_operations steps[] Chain ops that depend on each other (e.g. create doc, share it) sum of steps

Cost & Limits

What this costs to run

API quota
Gmail: 1B units/day (most ops 5-50 units). Calendar/Drive: generous quotas.
Tokens per call
Drive list results can be big — paginate
Monetary
Free; Google Workspace license required for business accounts
Tip
Cache account metadata. Gmail search is quota-heavy; scope with label/date filters.

Security

Permissions, secrets, blast radius

Minimum scopes: Gmail.readonly + Calendar + Drive — grant only what you use
Credential storage: Tokens in OS keychain (XDG-compliant); OAuth refresh handled automatically
Data egress: Your Google data flows through MCP to your LLM provider
Never grant: Gmail.modify to an unsupervised agent that can also read external URLs

Troubleshooting

Common errors and fixes

invalid_grant during OAuth

Client ID / redirect URI mismatch. Confirm the redirect URI registered in GCP matches what the MCP uses.

Quota exceeded

Backoff + batch. Gmail send has a daily cap; Drive has per-user/per-second limits.

Verify: Google Cloud Console > APIs > Quotas
Tokens expired despite refresh

Refresh token revoked — re-auth. Common when account password changed or security event triggered.

Alternatives

google-workspace-mcp vs others

AlternativeWhen to use it insteadTradeoff
Official Google Workspace MCP (when/if shipped)Google ships a first-party MCPWould be more authoritative; for now this is the strongest community option
Zapier/Composio hosted Google Workspace toolsYou want hosted + no OAuth setupMiddleware fees; less control

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills