Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Google Workspace MCP
Overview
Description from the maker (original English)
Cross-client Google Workspace admin: 2SV gaps, license waste, sharing drift, safe offboarding.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: GOOGLE_WORKSPACE_TOKEN, ADMIN_ACCESS_TOKEN, GOOGLE_WORKSPACE_MCP_HTTP_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
GOOGLE_WORKSPACE_TENANT,GOOGLE_WORKSPACE_MCP_READ_ONLY,GOOGLE_WORKSPACE_NO_LOCAL_DATA,GOOGLE_WORKSPACE_TOKEN,ADMIN_ACCESS_TOKEN,GOOGLE_WORKSPACE_MCP_HTTP_TOKEN,GOOGLE_WORKSPACE_BASE_URL,GOOGLE_WORKSPACE_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
GOOGLE_WORKSPACE_TENANTenvDefault client tenant (from google-workspace-cli tenants list) for tool calls that name no tenant, including sql, search and raw API calls. Set it when more than one tenant is registered: without it…GOOGLE_WORKSPACE_MCP_READ_ONLYenvSet to exactly 1 to hide offboard, sync, export, tenants test, tenants remove, workflow archive, the raw API execute tool, and every tool that writes the local learning store (teach, teach-pattern, t…GOOGLE_WORKSPACE_NO_LOCAL_DATAenvOptional. Set to exactly 1 to keep no local copy of Google Workspace data: reads go to the API, the response cache is off, nothing new is written to the local store, and sync and workflow archive are…- Optional single-organization OAuth access token with Admin SDK scopes, for use instead of registering client tenants. Leave blank once tenants are registered.
- Optional alternate name for GOOGLE_WORKSPACE_TOKEN. Leave blank.
- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
GOOGLE_WORKSPACE_BASE_URLenvOverrides the https://admin.googleapis.com host, for testing against a mock server. Leave blank.GOOGLE_WORKSPACE_USER_AGENTenvOverrides the User-Agent the CLI sends on Google requests. Leave blank.PRINTING_PRESS_CLIENT_PROFILEenvHas no effect for this connector (not a Google Workspace tenant). Leave blank.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32568 servers in this category
- Published to the registry more recently than 95% of the other 32568 servers in this category
- Basic checks equal to or better than 100% of the other 32568 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Google Workspace MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: GOOGLE_WORKSPACE_TOKEN, ADMIN_ACCESS_TOKEN, GOOGLE_WORKSPACE_MCP_HTTP_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.5) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
FlyDocs
by flydocs.ai
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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):
| Your AI agent | How to install the Google Workspace skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register google-workspace-mcp (no JSON editing). |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add google-workspace-mcp to mcp.json under the servers key, then pick Agent mode. |
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.
| Agent | What it takes |
|---|---|
| ChatGPT (desktop app) | Run installer, then add google-workspace-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/google-workspace/install.ps1 | iex. Then authenticate per the README and rungoogle-workspace-cli --helpto 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 | iexmacOS / 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 --versionUpgrade 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 | iexClaude 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 --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/google-workspace --forceHermes 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 theopenclaw: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:
- 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
policyprofile, 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.) - 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- 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 acmeprints them again). - Confirm Google issues a token for every scope you delegated:
google-workspace-cli tenants test acmeThe 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
| Question your MSP keeps asking | Command |
|---|---|
| Which accounts across all my clients lack 2-Step Verification, admins first? | google-workspace-cli mfa-gaps --all-tenants |
| Which Google Workspace licenses sit on suspended, never-signed-in, or idle accounts? | google-workspace-cli stale-licenses --all-tenants |
| Did our suspended leavers keep a license, groups, an admin role, OAuth tokens, or an unfinished Drive transfer? | google-workspace-cli leavers --all-tenants |
| One row per client for the QBR: 2SV coverage, admins without 2SV, stale licenses, Drive, Calendar and app-sharing setting changes | google-workspace-cli posture --all-tenants |
| Who changed Drive or Calendar settings, and how many files went external or public (with sample names) this week? | google-workspace-cli sharing-drift --all-tenants --since 7d |
| Which third-party apps hold full mail, full Drive, or admin access to client data? | google-workspace-cli oauth-apps --all-tenants --min-risk high |
| Any suspicious sign-ins, hijacked accounts, or 2SV turned off this week? | google-workspace-cli login-alerts --all-tenants --since 7d |
| What would offboarding this leaver do, step by step, before anything changes? | google-workspace-cli offboard "jane@example.com" --successor "manager@example.com" --ou "/Departed" |
| Is every client's domain-wide delegation still authorized? | `g
Only the beginning is shown; read the rest in the repo