Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 12, 2026·2 min de lectura

Workspace MCP — Google Workspace Tools via MCP

Workspace MCP exposes Gmail/Drive/Calendar tools over MCP with uv launch tiers and an HTTP mode designed to work with Claude Code OAuth flows.

MCP Hub
MCP Hub · Community
Listo para agents

Este activo puede ser leído e instalado directamente por agents

TokRepo expone un comando CLI universal, contrato de instalación, metadata JSON, plan según adaptador y contenido raw para que los agents evalúen compatibilidad, riesgo y próximos pasos.

Stage only · 17/100Stage only
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp Config
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando CLI universal
npx tokrepo install 8fc8cc2f-1024-4c2b-9aef-fd3b661c0019
contrato de instalaciónJSON de metadataplan adaptadorcontenido raw
Introducción

Workspace MCP exposes Gmail/Drive/Calendar tools over MCP with uv launch tiers and an HTTP mode designed to work with Claude Code OAuth flows.

  • Best for: agents that need Google Workspace automation with OAuth and fine-grained tool selection
  • Works with: Python + uv/uvx, Google OAuth credentials, MCP clients (HTTP recommended for OAuth)
  • Setup time: 25–60 minutes

Practical Notes

  • Data point: default HTTP endpoint in docs is http://localhost:8000/mcp.
  • Quant: start with --tool-tier core before enabling extended/complete to reduce scope.

Pattern: separate auth setup from tool rollout

With Google OAuth, the most reliable rollout is:

  1. make auth succeed for one user,
  2. run read-only tools,
  3. then enable write scopes.

Hardening tips

  • Prefer HTTP transport for OAuth flows and multi-user setups.
  • Store OAuth client secrets in a secret manager (not .env committed to git).
  • Restrict available tools to the minimum required per workflow.

FAQ

Q: Can it run in stdio mode? A: The README recommends HTTP mode for OAuth 2.1 and multi-user support.

Q: How do I limit permissions? A: Start with a smaller tool tier and enable write tools only when needed.

Q: Does it support VS Code MCP? A: Yes. The README includes a .vscode/mcp.json example and notes about HTTP transport.

🙏

Fuente y agradecimientos

Source: https://github.com/taylorwilsdon/google_workspace_mcp > License: MIT > GitHub stars: 2,380 · forks: 724

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

Google Workspace MCP — Gmail Drive Calendar for AI

Official Google CLI with built-in MCP server for all Workspace APIs. One command gives AI agents access to Gmail, Drive, Calendar, Docs, Sheets, and 10+ Google services.

MCP Configs
MCP Hub

Google Stitch MCP — AI Design via Model Context Protocol

Connect Claude Code, Cursor, Gemini CLI, or VS Code to Google Stitch for AI-driven UI design. Create projects, generate screens from text, edit designs, manage design systems — all via MCP.

MCP Configs
Google · Gemini Team

google-tag-manager-mcp-server — GTM MCP Remote Connector

Connect Google Tag Manager to MCP clients via an OAuth-backed remote server using mcp-remote + npx. Verified 152★; pushed 2026-05-14.

MCP Configs
MCP Hub

Google Workspace MCP — Gmail/Calendar/Drive for Agents

Google Workspace MCP exposes Gmail, Calendar, and Drive actions as MCP tools so agents can summarize inboxes and manage schedules with minimal scopes.

MCP Configs
MCP Hub
◈Inicio🔍Buscar👤Yo