What is managing-google-workspace?

A tool guide for managing Google Workspace services such as Gmail, Drive, Calendar, Docs, Sheets, and Slides. It explains how to route requests through available tools and how to set up Google access when needed.

It is for checking and managing email, files, calendars, documents, spreadsheets, presentations, and other Google Workspace data through supported tools or a command line.

It removes the need to remember which tool and parameters belong to each Google service, while also giving instructions for handling first-time login and permission problems.

managing-google-workspace — Skill for Claude Code by taylorwilsdon

About the project

Google Workspace MCP Server connects AI assistants and developer tools to Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through the Model Context Protocol. It is for people who want to control and edit Workspace services using natural-language requests, a command-line tool, or compatible AI clients. The catalogue entries extend or configure this server for agent use.

taylorwilsdon/google_workspace_mcp · 3,132 stars · on GitHub · workspacemcp.com

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.

Any agent

npx skills add taylorwilsdon/google_workspace_mcp --skill managing-google-workspace

Clone the repo

git clone --depth 1 https://github.com/taylorwilsdon/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 skill.

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/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace/github.svg)](https://agentmods.dev/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace)

Your own site

<a href="https://agentmods.dev/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace"><img src="https://agentmods.dev/badge/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace/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/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace"><img src="https://agentmods.dev/badge/skills/taylorwilsdon/google_workspace_mcp/managing-google-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 7 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Agent Snooping · line 41
Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.

Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
medium MCP Rug Pull · line 5
uvx/uv tool run commands without ==version create a rug-pull risk.

Fix: Pin the version: uvx package-name==1.2.3
medium MCP Rug Pull · line 8
uvx/uv tool run commands without ==version create a rug-pull risk.

Fix: Pin the version: uvx package-name==1.2.3
medium MCP Rug Pull · line 25
uvx/uv tool run commands without ==version create a rug-pull risk.

Fix: Pin the version: uvx package-name==1.2.3
medium MCP Rug Pull · line 305
uvx/uv tool run commands without ==version create a rug-pull risk.

Fix: Pin the version: uvx package-name==1.2.3
medium Rogue Agent · line 7
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
medium Excessive Agency · line 41
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

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.00123	$0.02756
Opus 5	$0.00062	$0.01378
Sonnet 5	$0.00025	$0.00551
Haiku 4.5	$0.00012	$0.00276

Measured 2d ago against content hash 03e151044222, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

managing-google-workspace scanned grade B with 1 finding 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Direct the user to edit `~/.claude/settings.local.json` themselves (this file is gitignored and never shared). Do not ask the user to paste secrets into the conversation. Tell them to add the following to the `env` block

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

managing-google-workspace — 94% identical, 3 lines differ
managing-google-workspace — 91% identical, 7 lines differ

skills/managing-google-workspace/SKILL.md · 306 lines

How it starts

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

Google Workspace -- Tool Router

Execution Mode

Detect which mode is available and use it.

MCP (preferred)

If MCP tools from the google-workspace server are available, call them directly. The tool names in the tables below are the base names -- prefix with the server name as needed (e.g. google-workspace:search_gmail_messages).

CLI (no MCP)

If no MCP tools are available, execute via bash:

uvx workspace-mcp --cli <tool_name> --args '{"user_google_email": "USER_EMAIL", ...}'

Before calling a tool, read the relevant reference file for exact parameter names and types. Only use parameters documented there -- do not invent parameters.

First-Time Setup

If a tool call fails with a credential error, walk the user through this setup.

1. Create OAuth credentials

Direct the user to Google Cloud Console:

Create OAuth 2.0 Client ID (Desktop application type)
Enable the Google APIs they need (Gmail, Drive, Calendar, etc.)
Copy the Client ID and Client Secret

2. Store credentials

Direct the user to edit ~/.claude/settings.local.json themselves (this file is gitignored and never shared). Do not ask the user to paste secrets into the conversation. Tell them to add the following to the env block:

{
  "env": {
    "GOOGLE_OAUTH_CLIENT_ID": "their-client-id",
    "GOOGLE_OAUTH_CLIENT_SECRET": "their-secret"
  }
}

If settings.local.json already exists, they should merge into the existing env object, not replace it. These env vars are inherited by all MCP servers and CLI processes that Claude Code spawns.

3. Authenticate

MCP mode: call start_google_auth to open the browser OAuth flow
CLI mode: run any tool -- the first invocation opens the OAuth flow
Credentials are cached in ~/.google_workspace_mcp/credentials (or as configured by WORKSPACE_MCP_CREDENTIALS_DIR) for future sessions

For server options, transport, auth modes, tool filtering, and deployment: references/server-options.md

Read the full file on GitHub · 306 lines

Files

What ships with it

17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago Changed · +1 lines 03e151044222
10d ago First seen · 305 lines · 123 tokens per session scan B e820ac1bd0c1

Subscribe to this mod's changes

managing-google-workspace is a skill published in the GitHub repository taylorwilsdon/google_workspace_mcp (3,132 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 2,756 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

LLM Productivity ai gmail google-calendar google-workspace llm-tools

managing-google-workspace