Workspace MCP adds full Google Workspace control for AI tools

Workspace MCP is a new open source server that gives AI assistants and developer tools control over Google Workspace services including Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts and Chat. The project says it supports OAuth 2.1, multi-user deployments, stateless mode and central hosting for organizations.

Workspace MCP adds full Google Workspace control for AI tools

Workspace MCP is an open source server that connects AI assistants and developer tools to Google Workspace, the project’s author said. It supports natural-language control over Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts and Chat through MCP clients, along with a CLI and a Code Mode for tools such as Claude Code and Codex.

The project bills itself as the most feature-complete Google Workspace MCP server. According to the repository description, it can do more than the Google tooling and built-in integrations available in Claude and ChatGPT, and it covers 12 services in total, including Apps Script and Google Search.

⚡ New to this?

This news is about a bridge between AI tools and Google Workspace. MCP, or Model Context Protocol, is a standard that lets an AI assistant talk to apps and services through one common interface instead of custom one-off integrations.

For non-experts, the main point is that this project turns Google services like Gmail and Drive into things an AI agent can manage directly. That matters because it changes how teams might automate email, documents, calendars and internal workflows.

🦞 OpenClaw angle

If you build self-hosted agents, this is a strong example of how to structure a tool server: support OAuth, separate read-only from write access, and make permissions selectable per service. If you are exposing Google Workspace to agents, mirror the project’s tiered model so you can ship a minimal tool set first and only enable broader access for trusted workflows.

Also, treat stateless mode and no-telemetry defaults as requirements, not extras. For internal automation, keep credentials in your own environment, run behind your reverse proxy or VPC, and prefer narrow scopes for each agent instead of handing out full Workspace access by default.

MCP stands for Model Context Protocol, a way for AI apps to connect to external tools through a standard interface. In this case, Workspace MCP exposes Google Workspace actions such as searching mail, managing files, creating documents and handling calendar events so an AI agent can call them directly.

The author says the server supports both local and remote use. It can run with streamable HTTP transport for modern MCP clients, or in legacy stdio mode as a fallback, and the CLI can talk to both local and remote instances.

Authentication is a major part of the project’s pitch. The server supports native OAuth 2.1, remote OAuth 2.1 multi-user support, stateless mode and external auth server support, which the author says makes it possible to host centrally for an entire organization.

The project also claims security controls that may matter to IT teams. According to the documentation, the server sends data only to Google’s APIs using the authenticated user’s own OAuth client credentials, with no telemetry, analytics, usage reporting, license server or SaaS dependency.

The repository says the project is fully open source and MIT licensed. It also says there is no dual licensing, no commercial feature gating and no contributor license agreement.

Workspace MCP supports both free Google accounts and Google Workspace plans, including Starter, Standard, Plus, Enterprise and Non Profit. The project says it also includes expanded app options like Chat and Spaces.

For deployment, the author points users to a quick start flow that starts with Google Cloud OAuth credentials, then choosing a launch command and connecting a client. The documentation includes examples for running the server locally, selecting tool tiers, enabling read-only mode and configuring granular permissions by service.

The project also offers a private managed cloud instance for people who want one, according to the page. The author says Workspace MCP is available with a full CLI toolset, encrypted token caching for repeated use, and support for modern clients like Claude Desktop, Claude Code, VS Code and LM Studio.

Source: r/LocalLLaMA ↗

More from OpenClaw News