Google Workspace MCP

Google Workspace + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Google Workspace

API. Not affiliated with, endorsed by, or sponsored by Google LLC.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Cross-client Google Workspace admin: 2SV gaps, license waste, sharing drift, safe offboarding. Works with the AI you already use - Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot, no code required - plus the ChatGPT desktop app and Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners.

Works with your agent

The agents MSP owners use most (self-serve, works today):

Also for ChatGPT and the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Google Workspace MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. Client tenants are registered with the CLI (tenants add is CLI-only), so install it too (Path B below). (Browse every Google Workspace release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install google-workspace@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Google Workspace Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.ps1 | iex. Then authenticate per the README and run google-workspace-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.sh)

The installer drops both google-workspace-cli (the CLI) and google-workspace-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

google-workspace-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update google-workspace@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/google-workspace --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/google-workspace --force

Hermes speaks MCP natively, so it can also use the google-workspace-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the google-workspace skill from https://github.com/servosity/msp-skills/tree/main/skills/google-workspace. The skill defines how its required CLI (google-workspace-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Each client is a tenant: a Google Cloud service account with domain-wide delegation that impersonates that client's super admin. Set one up per client:

1. In a Google Cloud project, enable the Admin SDK API and the Enterprise License Manager API (plus the Cloud Identity API if you will use the policy profile, and the Google Workspace Reseller API for your reseller domain), create a service account, and download its JSON key. (Google Cloud organizations created since May 2024 block key creation by default; an org admin has to allow it for that project.)
2. Register the client. The key is copied into the CLI's config directory with owner-only permissions (mode 0600 on macOS and Linux; on Windows the file inherits the config folder's permissions), so delete the downloaded original afterwards:

   google-workspace-cli tenants add acme --domain example.com --admin admin@example.com --key ./acme-sa.json

1. Paste the printed Client ID and scopes into the client's Admin console > Security > Access and data control > API controls > Domain-wide delegation (google-workspace-cli tenants scopes acme prints them again).
2. Confirm Google issues a token for every scope you delegated:

   google-workspace-cli tenants test acme

The default read scope profile covers every report. Profiles combine with commas, and only full includes read: use --scopes full for offboarding writes (it also authorizes every user write, including deleting users and granting super admin), --scopes read,policy (or full,policy) to add the current 2SV, Drive sharing, and Gmail forwarding policy to posture, and register your own reseller domain with --reseller --scopes reseller (it is excluded from --all-tenants). --scopes policy on its own replaces read and leaves the reports nothing to read. Pick a client per command with --tenant (or GOOGLE_WORKSPACE_TENANT), or fan out with --all-tenants.

Managing a single organization? Set GOOGLE_WORKSPACE_TOKEN to an OAuth access token that carries the Admin SDK scopes instead of registering tenants; the reports then run against that one organization. Once tenants are registered the token is no longer used: a command run without --tenant (when more than one tenant is registered) refuses instead of acting on the token's organization.

google-workspace-cli tenants test --all-tenants is the real credential check: it mints a token per scope for every registered client, reads each client's customer record and domains, and exits non-zero when any delegation is missing. It cannot tell you whether the License Manager or Cloud Identity APIs are enabled (the first report that needs them will), and with no tenants registered it has nothing to check. doctor probes one real read endpoint with the selected tenant's token (--tenant , or the only registered tenant) or the single-org token and reports a rejected or wrong-host credential as ERROR, but it exits 0 unless you pass --fail-on error.

What this skill does

| Is every client's domain-wide delegation still authorized? | `g