xbill9

Workspace MCP Claude — Communication skill for Claude Code

Communication community

Connect Claude Code to the Google Workspace remote MCP servers (Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, People).

How to install Workspace MCP Claude

This entry records only its repository, not the path inside it, so there is no exact command to give. Open xbill9/workspace-mcp-claude and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Workspace MCP Claude does

Connect Claude Code to the Google Workspace remote MCP servers (Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, People).

Alternatives in Communication

Google Workspace Groups Settings — Manage Google Groups settings 21.6k ★
Open SaaS — A 100% free modern JS SaaS boilerplate (React, NodeJS, Prisma) 14.1k ★
HolaOS — Open-source agentic workspace enterprises can make their own 10.9k ★

README

Workspace MCP

This workspace provides a set of scripts to initialize a Google Cloud project and connect **Claude Code** (and Gemini CLI) to the Google Workspace remote Model Context Protocol (MCP) servers.

Google Workspace MCP is in Developer Preview. Join the [Google Workspace Developer Preview Program](https://developers.google.com/workspace/preview) first.

Install as a Claude Code plugin

The setup is packaged as the `google-workspace-mcp` skill, so Claude Code can walk through it, check what is already done, sign in and test:

/plugin marketplace add xbill9/workspace-mcp-claude
/plugin install google-workspace-mcp@workspace-mcp-claude

Then ask Claude Code something like *"connect my Gmail and Drive to Claude Code"*. The skill lives in `plugin/skills/google-workspace-mcp/`: `SKILL.md`, the scripts in `scripts/`, and `references/` for the console steps, scopes and tools. The scripts at the repo root are wrappers around the skill's copies, so `./bootstrap.sh` and the rest work from a clone too.

Known issues: sign-in

Two limits, measured on 2026-10-04 and 2026-10-06 with Claude Code 2.1.289 and 2.1.291 and one OAuth client shared by all eight servers. Details and evidence: [`known-issues.md`](plugin/skills/google-workspace-mcp/references/known-issues.md). Every other quirk seen during setup (sign-in pages, servers, Claude Code, Cloud console, environment) is catalogued in [`quirks.md`](plugin/skills/google-workspace-mcp/references/quirks.md).

⚠️ Sign-ins last about an hour. Google issues them without a refresh token (Claude Code's authorization request has no access_type=offline), so Claude Code cannot renew them. The same sign-in with access_type=offline&prompt=consent added returns a refresh token that renews without a browser.
⚠️ Signing a working server in again revokes every server's token. Claude Code revokes the server's old token, and Google revokes the whole grant for the OAuth client the eight servers share. Revoking