/ Annuaire / Playground / google-workspace-mcp
● Communauté aaronsb ⚡ Instantané

google-workspace-mcp

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

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

google-workspace-2.replay ▶ prêt
0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : google-workspace-mcp

Triage your inbox and draft replies

👤 Anyone buried in email ⏱ ~15 min intermediate

Quand l'utiliser : Morning inbox. 200 unread. You want to know what needs a response today.

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

Résultat : 30 minutes of inbox triage in 5.

Pièges
  • 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

Quand l'utiliser : You need 45 minutes next week that works for 5 people across time zones.

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

Résultat : Meeting scheduled without the Doodle dance.

Pièges
  • 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

Quand l'utiliser : Somebody shared a sensitive folder broadly. You want to know exactly who has access.

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

Résultat : Drive posture improved in one pass.

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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'.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
Gmail: 1B units/day (most ops 5-50 units). Calendar/Drive: generous quotas.
Tokens par appel
Drive list results can be big — paginate
Monétaire
Free; Google Workspace license required for business accounts
Astuce
Cache account metadata. Gmail search is quota-heavy; scope with label/date filters.

Sécurité

Permissions, secrets, portée

Portées minimales : Gmail.readonly + Calendar + Drive — grant only what you use
Stockage des identifiants : Tokens in OS keychain (XDG-compliant); OAuth refresh handled automatically
Sortie de données : Your Google data flows through MCP to your LLM provider
Ne jamais accorder : Gmail.modify to an unsupervised agent that can also read external URLs

Dépannage

Erreurs courantes et correctifs

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.

Vérifier : 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 autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills