Spec Driven Development
de formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar
Google Workspace MCP
Resumen
Descripción del creador (original en inglés)
Cross-client Google Workspace admin: 2SV gaps, license waste, sharing drift, safe offboarding.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Otros
- Debes completar: GOOGLE_WORKSPACE_TOKEN, ADMIN_ACCESS_TOKEN, GOOGLE_WORKSPACE_MCP_HTTP_TOKEN
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- Debes completar tú:
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
Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Valores que debes completar
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.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Otrosi
- Más estrellas que el 0% de los otros 32484 servidores de esta categoría
- Publicado en el registro más recientemente que el 96% de los otros 32484 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 32484 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Google Workspace MCP?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
Debes completar: GOOGLE_WORKSPACE_TOKEN, ADMIN_ACCESS_TOKEN, GOOGLE_WORKSPACE_MCP_HTTP_TOKEN
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.1.5) llegó al registro ayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Recta
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Remote Desktop Commander
de desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Se ejecuta en la nube★ 211Actualizado ayer
Instalar
Recta
de RectaBuild
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Computadora o nubeActualizado hoy
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo