Google Workspace and AI: Is there an MCP server for Google Workspace?

Google Workspace is Google’s office suite with Gmail, Drive, Calendar, Docs, Sheets and more. If you want Claude or another AI assistant to work with emails, files and events, the first question is: is there an MCP server for it?

In short

Yes. Google runs official MCP servers, one per product. They carry the status Developer Preview, so they are not generally available yet. For Claude, Anthropic also ships ready-made connectors for Gmail, Calendar and Drive.

What Google offers itself

The MCP servers. According to Google, each Workspace product has its own server. Gmail runs at https://gmailmcp.googleapis.com/mcp/v1, Drive at https://drivemcp.googleapis.com/mcp/v1 and Calendar at https://calendarmcp.googleapis.com/mcp/v1. Docs, Sheets, Slides, Chat, People and Classroom follow. The Google Cloud overview lists Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat and People, plus a Universal Search server, as Developer Preview, and the configuration page also lists Classroom. We found no general-availability notice for any of these servers; the release notes still call them Developer Preview as of 29 October 2026. Google describes the program this way: features in Developer Preview may not appear in public applications before the general availability announcement. An announcement of 1 May 2026 describes the launch as a public developer preview.

What the tools can do. The references list for Gmail, among others, searching, reading, creating drafts and setting labels. No tool for sending or deleting appears there. For Drive, the reference lists searching, reading, downloading, creating and copying, no deleting. For Calendar, it lists creating, updating, deleting and responding to events. The configuration page, however, lists only read scopes for Calendar. We could not establish which permissions writing needs.

Sign-in and setup. The servers use OAuth 2.0. According to Google, you need membership in the Developer Preview Program, a Google Cloud project, the MCP services enabled and your own OAuth client with the option “Use this client for an AI-powered agent”. From 11 November 2026, according to the release notes, the servers reject requests from OAuth clients that are not marked this way. According to Google, the assistant inherits the user’s permissions. Google warns about indirect prompt injection and advises you to review every action the assistant takes.

Who can use them. The announcement states availability for “all Google Workspace customers and developers”, with a gradual rollout from 1 May 2026. According to Google, admins need to take no action and manage API access in the Admin console under Security > API Controls. We found no restriction by plan or country. Access requires membership in the Developer Preview Program.

With Claude. Google describes setup as a custom connector in Claude.ai or Claude Desktop. According to Google, that requires a Claude Enterprise, Pro, Max or Team plan.

Anthropic’s own connectors. According to the Claude Help Center, connectors exist for Gmail, Google Calendar and Google Drive, plus Docs, Sheets and Slides. According to Anthropic, they can send emails, change events, and share, move and trash Drive files, by default after your approval. On Team and Enterprise plans, an owner must enable them first; a Google Workspace admin may also need to allow Claude as a trusted app. Limits according to Anthropic: Claude reads only metadata of Gmail attachments and only the text of Drive files, Drive files can be added only to private projects, and Google’s API quotas apply. Live editing of Docs, Sheets and Slides in the side pane works only on the web in Chrome or in Claude Desktop with the built-in browser. Separately, according to the Claude Help Center, Anthropic offers an add-on “Claude for Google Workspace” in beta for Pro, Max, Ultra, Team and Enterprise plans. It is a sidebar in Docs, Sheets and Slides. Anthropic writes that it does not train its models on the data from these connectors. Exception: if a consumer-plan user has allowed training and copies content into a chat, Anthropic says that content may be used for training.

REST APIs. REST APIs exist for Gmail, Drive and Calendar. For user data, Google names OAuth 2.0 client IDs or service accounts with domain-wide delegation.

Administration. For Gemini Enterprise, the Google help centre describes an Agent Gateway that applies policies from the Admin console to the Workspace MCP servers. It is opt-in.

AI in the product: Gemini in Workspace. Gemini is the AI feature in Gmail, Docs, Drive and other apps. According to Google, Workspace does not use customer data to train models without the customer’s prior permission or instruction. According to Google, this applies to qualifying Workspace plans.

Data location. According to Google, administrators on certain plans can have data stored in the US or in Europe, for example on Business Standard, Business Plus and the Enterprise plans. Processing is covered only by “Enterprise Data Regions” and “Assured Controls Data Regions”, for example in Enterprise Plus. The MCP references for Gmail, Drive and Calendar name only a global endpoint. The sources we read do not say whether the MCP servers follow the region choice. Google notes that Model Armor can break data residency when you use a region it does not support.

What the community offers

taylorwilsdon/google_workspace_mcp is an open-source server (MIT) for twelve Workspace services. It runs with your own OAuth client in your own Google Cloud project, locally or as your own HTTP server. It does not come from Google. The Google repository googleworkspace/cli is a command-line tool and, according to its README, not an officially supported Google product. Other community servers exist on GitHub, for example aaronsb/google-workspace-mcp (Apache 2.0). We did not review them. Zapier runs its own MCP pages for Gmail, Google Calendar and Google Drive. These pages do not show how Zapier processes data.

What this means for your company

• The Google servers are a Developer Preview. Do not plan workflows that depend on a fixed feature set.
• Decide whether you use the Claude connectors or the Google servers. Both run through your Google account and its permissions.
• The assistant reads your emails and documents. Foreign content can contain hidden instructions. Review actions before you approve them.
• What reaches the AI assistant falls under its terms, no longer under Google’s.
• ChatGPT: OpenAI’s help pages blocked our requests. We therefore have no confirmed statement on plans, regions (including the EEA), training use, or whether ChatGPT accepts the Google MCP servers as a custom connector. Check OpenAI’s help centre before you plan.