What it is
Google runs a separate remote MCP server for each of nine Workspace products: Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, People and Classroom. Each lives at its own URL, such as https://gmailmcp.googleapis.com/mcp/v1, and uses Streamable HTTP with OAuth. As of October 2026 all of them remain in the Google Workspace Developer Preview Program, which you must join; Gmail, Drive, Calendar and Chat entered preview on 22 April 2026 and Docs, Sheets and Slides on 13 July.
Across the nine servers there are about 63 tools. Gmail has 10, including search_threads, get_thread and create_draft, but no send tool. Drive has 8 (search_files, read_file_content, create_file, copy_file), Calendar 9 (list_events, create_event, suggest_time), Chat 7 (search_messages, send_message), Sheets 6, People 3 and Classroom 16, while Docs and Slides have read and update tools that gained comment support on 1 October.
Setup is involved. You enable each product API and its MCP service in a Google Cloud project, configure an OAuth consent screen with the scopes, create a web OAuth client marked "Use this client for an AI-powered agent", and add one connector per product. From 11 November 2026 the servers reject requests from OAuth clients without that flag, and a client not flagged by 12 November cannot be changed later.
Install
https://gmailmcp.googleapis.com/mcp/v1 (one URL per product)Our review
First-party servers matter here because Workspace is where most company mail, documents and calendars live, and these run on Google's infrastructure with the user's own permissions rather than through a third party's token store. The tool design is cautious in useful ways. Gmail can search, read, label and draft but cannot send; Drive can read a file's permissions but not change them; Calendar can propose meeting times with suggest_time. For a first deployment, that restraint counts in its favour.
It remains hard to recommend broadly. Six months after the first servers entered preview, none has reached general availability, membership of the Developer Preview Program is required, and each product needs its own API, MCP service, scopes and connector, so a user wanting mail, files and calendar adds three connectors. Claude users need a Pro, Max, Team or Enterprise plan for custom connectors. Google's troubleshooting notes that clients which do not request offline access never receive a refresh token, which means signing in again about every hour.
Google's documentation is unusually direct about prompt injection: the servers "can read, modify, and delete data in your Google Account", and incoming emails or shared documents may carry hidden instructions. An inbox is the textbook untrusted input, so the missing send tool is a real mitigation, but Docs, Sheets, Calendar and Chat's send_message are still writable. Administrators can review activity through OAuth log events in the security investigation tool.
The most popular community option, taylorwilsdon/google_workspace_mcp (about 3,400 stars), covers more products from one server, including Forms and Tasks, at the price of running it yourself and holding the OAuth tokens on your own machine. Google's version has the stronger security story and the narrower toolset; in October 2026 the community server is still the one with the broader reach.
Where it earns its place
An IT lead piloting AI assistants for a 50-person Workspace company
Give staff Claude access to their mail and calendar without a third-party token broker
Create one internal OAuth client flagged for agents, publish Gmail, Calendar and Drive as three custom connectors, and review use through OAuth log events. No MCP fee is listed during preview; the cost is setup time and the risk that preview tools change.
An executive assistant working in Claude
Find a slot for a meeting with three colleagues and draft the invitation email
list_events and suggest_time in Calendar, create_event for the slot, then create_draft in Gmail for a person to review. Because Gmail cannot send, nothing leaves the outbox without a click.
A developer building an internal agent in Antigravity
Pull figures from a Sheets tracker into a weekly Docs report
get_values on the tracker and update_doc on the report, all within the user's own Drive permissions. update_values can overwrite cells, so keep approval prompts on for Sheets writes.
Before you commit
- Setup
- Join the Developer Preview Program, enable up to nine product APIs and their MCP services in a Cloud project, configure the consent screen and an agent-flagged web OAuth client, then add each server URL as a connector. Google documents Antigravity and Claude.ai/Claude Desktop.
- Integrations
- Nine servers with about 63 tools, from Gmail's 10 to Classroom's 16. Write tools include create_draft, create_file, update_doc, update_values, create_event, delete_event and Chat's send_message; Gmail has no send.
- Data and privacy
- Requests act on the signed-in user's data under normal Workspace governance, with granular scopes such as gmail.readonly plus gmail.compose and drive.file. Every server reads untrusted content, and Google explicitly warns about indirect prompt injection.
- Cost at scale
- No MCP charge is listed during preview; users need Workspace accounts. Google introduced agent usage quotas for Gmail, Calendar and Drive on 1 May 2026, but the MCP guide does not publish the numbers.
- Limits
- Preview only with no GA date; no Gmail send and no Drive sharing changes; clients that drop refresh tokens re-authenticate about hourly; nine connectors add a long tool list to every session.
What's good
- First-party servers hosted by Google, acting with the user's own permissions
- Gmail can draft but not send, which limits injection damage
- Covers nine products, including Chat, People and Classroom
- Granular scopes such as drive.file and gmail.compose
What's not
- Developer Preview only; program membership required
- A Cloud API, MCP service and connector for every product
- Hourly re-sign-in in clients that drop refresh tokens
- Agent-flagged OAuth client mandatory from 11 November 2026
Best for
Developers and IT teams in the Workspace preview who want first-party AI access to mail, files and calendars.
Alternatives
Google Workspace MCP servers: common questions
- Is Google Workspace MCP servers worth it?
- Google's own route into Gmail, Drive and Calendar, held back by preview status, a connector per product and a Gmail server that drafts but never sends. We rate it 3.8 out of 5.
- How much does Google Workspace MCP servers cost?
- No charge listed during Developer Preview; requires program membership and a Google Cloud project.
- What are the downsides of Google Workspace MCP servers?
- Developer Preview only; program membership required; a Cloud API, MCP service and connector for every product; hourly re-sign-in in clients that drop refresh tokens; agent-flagged OAuth client mandatory from 11 November 2026.
- Who is Google Workspace MCP servers best for?
- Developers and IT teams in the Workspace preview who want first-party AI access to mail, files and calendars.
- How much does Google Workspace MCP servers cost for a team or in production?
- No MCP charge is listed during preview; users need Workspace accounts. Google introduced agent usage quotas for Gmail, Calendar and Drive on 1 May 2026, but the MCP guide does not publish the numbers.
- Is Google Workspace MCP servers safe for company data?
- Requests act on the signed-in user's data under normal Workspace governance, with granular scopes such as gmail.readonly plus gmail.compose and drive.file. Every server reads untrusted content, and Google explicitly warns about indirect prompt injection.
- What are the best Google Workspace MCP servers alternatives?
- The closest alternatives we have reviewed are Zapier MCP, Notion MCP and Slack MCP Server.
Answers checked Oct 23, 2026.