Multi-Account Google Workspace + Slack MCP for Claude Code

Give Claude Code access to Gmail, Google Drive, Calendar, Sheets, Docs, and Slack — with full support for multiple Google accounts (e.g., personal + work).

Background

Claude Desktop and Claude Cowork have built-in Google Workspace integrations — flip a toggle and you're connected. Claude Code has nothing. As of March 2026, there's no official integration, no plugin that handles multi-account, and no documentation on how to set it up.

This repo is the result of ~6 hours of research and debugging to get it working. The final solution is simple, but getting there required discovering several undocumented behaviors in Claude Code's MCP system, Google's OAuth2 implementation, and the gws CLI.

What makes this hard

It's not one problem — it's a stack of them, each undocumented:

1. Claude Code silently ignores MCP config in the wrong file. If you put mcpServers in settings.local.json (where you'd expect it), servers don't start. No error. No log. You can spend hours restarting and re-checking JSON syntax. The config must go in .mcp.json at the project root. (Claude Code Issue #24477)

2. One OAuth client for two Google accounts breaks both. Google invalidates account A's refresh token when you authenticate account B with the same OAuth client. You need separate OAuth Desktop App clients — one per account — in the same GCP project.

3. The credential file env var doesn't work. GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE is supposed to let you point the Google Workspace CLI at different credential files, but it doesn't reliably route to the right account. You have to mint fresh access tokens and pass them via GOOGLE_WORKSPACE_CLI_TOKEN (the highest-priority auth method).

4. Go binaries use single-dash flags. Both the gws CLI and slack-mcp-server are Go binaries. --transport stdio fails silently. It's -t stdio — or just omit it (stdio is the default).

5. MCP servers only start at session launch. Config changes don't take effect until you restart Claude Code entirely.

Each of these individually cost 30-120 minutes to diagnose. Together they make the setup feel broken when it's actually a solvable configuration problem.

What we tried and rejected

For the full investigation log, see docs/research-notes.md.

The Solution

The working setup uses:

• Google Workspace CLI (gws v0.7+) — Google's official CLI with built-in MCP server mode
• Separate OAuth Desktop clients — one per Google account, in the same GCP project
• A token wrapper script — mints fresh access tokens from each account's credential file, passes them via the highest-priority env var
• .mcp.json at project root — the only config location Claude Code actually reads for MCP servers
• slack-mcp-server — Go-based Slack MCP, read-only by default

What you get

Once running, Claude Code can search your email, read Drive files, check your calendar, read/write spreadsheets, and search Slack — all through natural language.

Quick Start

Prerequisites

• Claude Code installed and working
• Node.js 18+ (for npx)
• Python 3 (for token minting — uses only stdlib)
• gcloud CLI (for enabling APIs and IAM)
• A Google account with Gmail/Drive access
• (Optional) A Slack workspace where you can create an app

AI-Guided Setup

1. Clone this repo and open Claude Code in it:

   hljs language-bash

   Copy

   git clone https://github.com/YOUR_USERNAME/claude-code-google-workspace.git
   cd claude-code-google-workspace
   claude
   

2. Tell Claude Code: "Set up Google Workspace MCP for me"

   The CLAUDE.md in this repo contains machine-readable setup instructions. Claude Code will walk you through each step, prompting you only for browser-based OAuth steps that can't be automated.

3. Restart Claude Code to load the new MCP servers.

Manual Setup

If you prefer step-by-step instructions: docs/manual-setup.md.

Full Research Log

To understand every decision and failed approach: docs/research-notes.md.

Architecture

Claude Code session start
        │
        ├─── reads .mcp.json (project root)
        │
        ├─── starts gws-personal server:
        │      │
        │      ├── gws-token-wrapper.sh personal.json
        │      │     │
        │      │     ├── reads personal.json (client_id_A + refresh_token)
        │      │     ├── POST https://oauth2.googleapis.com/token → access_token
        │      │     └── exec: GOOGLE_WORKSPACE_CLI_TOKEN=<token> gws mcp -s gmail,drive,...
        │      │
        │      └── gws mcp ←→ Google APIs (Gmail, Drive, Calendar, Sheets, Docs)
        │
        ├─── starts gws-work server:
        │      │
        │      └── (same flow, different credential file with client_id_B)
        │
        └─── starts slack server:
               │
               └── npx slack-mcp-server (SLACK_MCP_XOXP_TOKEN env var)

Why the wrapper script?

The gws CLI stores one set of credentials at a time internally. For multiple accounts, we can't rely on its credential file routing (CREDENTIALS_FILE env var is unreliable). Instead, we:

1. Read the exported credential file (has client_id, client_secret, refresh_token)
2. Call Google's token endpoint directly to mint a fresh access token
3. Pass it via GOOGLE_WORKSPACE_CLI_TOKEN — the highest-priority auth method in the gws auth chain

This is 15 lines of shell + Python stdlib. No dependencies.

Why separate OAuth clients?

OAuth2 Desktop App clients have a behavior where issuing a new refresh token for account B invalidates the existing refresh token for account A — if they share the same client_id. Creating separate OAuth Desktop clients in the same GCP project gives each account its own independent token lifecycle.

Using in Your Own Projects

After setup, you need two things in any project where you want these MCP servers:

1. .mcp.json at the project root — copy from this repo's template and fill in your paths
2. ~/.config/gws/ — credential files + wrapper script (created once during setup, shared across all projects)

Or add the mcpServers config to ~/.claude.json for global access in every project.

Always gitignore .mcp.json — it contains OAuth tokens.

Known Gotchas

These are ordered by how much time they'll cost you if you hit them unaware:

Caveats

• Written March 2026 — tested with gws CLI v0.7.0 and current Claude Code
• Google and Anthropic will likely make this easier natively — this repo fills the gap until then
• GCP project + OAuth consent screen setup requires manual browser steps (can't be fully automated)
• Access tokens minted at session start expire after ~1 hour — restart for long sessions
• Tested on macOS — Linux should work, Windows untested
• The gws CLI is pre-1.0 — flags and auth behavior may change

References

• Google Workspace CLI — the core tool powering Google Workspace access
• slack-mcp-server — Slack MCP server
• Claude Code MCP docs — official MCP server documentation
• MCP Specification — the Model Context Protocol spec
• Google OAuth2 documentation — OAuth flow and token lifecycle
• Claude Code Issue #24477 — settings.local.json silent ignore bug

Contributing

Issues and PRs welcome. If you hit a new gotcha, please open an issue — every undocumented behavior we capture saves someone hours.

License

MIT