What is google-workspace-setup?

A command that sets up a Google Workspace connector for multiple accounts. Google Workspace is the collection of services such as Gmail, Calendar, and Drive.

Use it to prepare the connector, configure accounts, authorize them in a browser, and connect it to the current project.

It organizes prerequisite checks, OAuth authorization, account configuration, and project wiring in one setup process.

google-workspace-setup — Command for Claude Code by rajool

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/rajool/google-workspace-mcp

Made for: Claude Code.

Or install google-workspace-mcp, the plugin that ships this one along with the rest of its 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/rajool/google-workspace-mcp/google-workspace-setup/github.svg)](https://agentmods.dev/commands/rajool/google-workspace-mcp/google-workspace-setup)

Your own site

<a href="https://agentmods.dev/commands/rajool/google-workspace-mcp/google-workspace-setup"><img src="https://agentmods.dev/badge/commands/rajool/google-workspace-mcp/google-workspace-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rajool/google-workspace-mcp/google-workspace-setup"><img src="https://agentmods.dev/badge/commands/rajool/google-workspace-mcp/google-workspace-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 898 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.00898
Opus 5.5	$0.00016	$0.00359
Sonnet 5.5	$0.00008	$0.00180
Haiku 4.5	$0.00004	$0.00090

Measured 1mo ago against content hash 8f7c0ad166ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

google-workspace-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/google-workspace-setup.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Workspace MCP — setup

Guide the user through standing up the multi-account Google Workspace MCP server. Be concise; do the mechanical steps yourself. Never ask the user to paste secrets into chat — only to place files or click Allow.

1. Prerequisites

uv --version — if missing, point to https://docs.astral.sh/uv/ and stop.
OAuth client secret at ~/.config/google-workspace-mcp/credentials.json (honor $GWM_HOME / $GWM_CREDENTIALS / $XDG_CONFIG_HOME). If missing, walk them through Google Cloud Console (own project; enable Gmail, Calendar, Drive, Tasks APIs; OAuth consent screen / Google Auth Platform audience External; create an OAuth client → Desktop app; download and save to that path).
Publishing status — verify this even when credentials.json already exists. Google Auth Platform → Audience must read In production. An External app left in Testing is issued refresh tokens that expire after 7 days with these scopes, so every account starts failing weekly with invalid_grant: Bad Request. Have them click Publish app — no verification is required for personal use under 100 users, and the "Google hasn't verified this app" screen appears in Testing too. Tokens issued while it was in Testing keep their 7-day clock, so re-authorize each account once after publishing.
Server binary on PATH: google-workspace-mcp --help. If missing: uv tool install git+https://github.com/rajool/google-workspace-mcp (or uv tool install . from a local clone).

2. Define accounts

Pick a short slug per account. Either create ~/.config/google-workspace-mcp/accounts.json (see accounts.example.json in the repo) or plan to pass them inline via GWM_ACCOUNTS.

3. Authorize each account

The authorize CLI prints a Google consent URL and waits on a localhost redirect. The key rule: open the URL in a browser signed into the account being authorized.

For each account:

Run in the background: google-workspace-authorize <slug> (account already in the registry), or google-workspace-authorize <slug> <email> "<Display Name>" to register a new one. It prints AUTH_URL: <url>.
If the Claude in Chrome extension is connected, call list_connected_browsers, pick the browser whose name matches that account's email, select_browser it, navigate to the AUTH_URL, and click through the unverified-app warning → Continue → Select all → Continue. Otherwise hand the user the URL for the right browser/profile.
The CLI writes ~/.config/google-workspace-mcp/tokens/<slug>.json.

Read the full file on GitHub · 79 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +11 lines 8f7c0ad166ab
1mo ago First seen · 68 lines · 41 tokens per session scan A a524a773f005

Subscribe to this mod's changes

google-workspace-setup is a command published in the GitHub repository rajool/google-workspace-mcp (2 stars, last pushed 25d ago), licensed MIT. It adds 41 tokens to every session and 898 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code claude-code-plugin gmail google-calendar google-drive google-tasks

google-workspace-setup

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Google Workspace MCP — setup

1. Prerequisites

2. Define accounts

3. Authorize each account

What this file has done since we first saw it

Other commands, from other repositories

gw-setup

learn

prototype

genshijin-compress

standup

brand-generate