Google Workspace MCP

What it is

Google Workspace MCP is Google's own set of remote Model Context Protocol servers for Google Workspace data. Instead of one server, Google runs a dedicated server for each product: Gmail, Google Drive, Google Docs, Google Sheets, Google Slides, Google Calendar, Google Chat, the People API and Google Classroom. An AI client such as Claude or Google Antigravity connects to each endpoint over Streamable HTTP with OAuth 2.0 and acts with the signed-in user's own permissions.

Google describes three jobs for the servers: read data (search emails, retrieve files, list calendar events), take action (create draft emails, upload files, schedule meetings) and respect security by inheriting the same permissions and data governance controls as the user.

Everything here is a Developer Preview. You must be a member of the Google Workspace Developer Preview Program, and the program terms say preview features may not be included in public applications before general availability.

Endpoints

Tools it exposes

• Gmail: search_threads, get_thread, get_message, create_draft, list_drafts, list_labels, label_message, label_thread, unlabel_message, unlabel_thread. There is no send tool: the agent writes a draft and you send it from Gmail.
• Drive: search_files, read_file_content, download_file_content, get_file_metadata, get_file_permissions, list_recent_files, create_file, copy_file
• Docs: read_doc, update_doc
• Sheets: get_spreadsheet, get_values, update_values, update_formulas, update_spreadsheet, insert_dimension
• Slides: read_presentation, update_presentation
• Calendar: list_calendars, list_events, search_events, get_event, create_event, update_event, delete_event, respond_to_event, suggest_time
• Chat: search_conversations, list_messages, search_messages, send_message, mark_as_read, mark_as_unread, list_memberships, get_notification_settings, update_notification_settings
• People: get_user_profile, search_contacts, search_directory_people
• Classroom: course, roster, announcement, coursework, rubric and topic tools such as list_course_summaries and create_announcement

Setup

1. Join the Google Workspace Developer Preview Program and create a Google Cloud project.
2. Enable the product APIs (for example gmail.googleapis.com and drive.googleapis.com) and the matching MCP services (gmailmcp.googleapis.com, drivemcp.googleapis.com and so on) with gcloud services enable or in the Cloud console.
3. Configure the OAuth consent screen and add the scopes for each server you plan to use, such as gmail.readonly and gmail.compose for Gmail or drive.readonly and drive.file for Drive. The Chat server also needs a Chat app configured in the project.
4. Create a Web application OAuth client and select Use this client for an AI-powered agent. Google says requests are rejected when that option is not selected.

Claude (claude.ai or Claude Desktop): Google says you need a Claude Enterprise, Pro, Max or Team plan. Add https://claude.ai/api/mcp/auth_callback as a redirect URI on the OAuth client, open Settings (or Admin settings) > Connectors > Add custom connector, enter a name and one of the URLs above, and put the OAuth client ID and secret under Advanced settings. Repeat this for each product you want.

Google Antigravity: add the redirect URI https://antigravity.google/oauth-callback, list each server in ~/.gemini/config/mcp_config.json, then authenticate each one from Settings or from the /mcp panel in Antigravity CLI:

{
  "mcpServers": {
    "gmail": {
      "serverUrl": "https://gmailmcp.googleapis.com/mcp/v1",
      "oauth": { "clientId": "OAUTH_CLIENT_ID", "clientSecret": "OAUTH_CLIENT_SECRET" }
    }
  }
}

Other clients: enter the server URL, Streamable HTTP as the transport and OAuth 2.0 as the authentication method. Google notes that a client only gets a refresh token when its authorization request includes access_type=offline; without it, users sign in again about every hour. Because these are hosted endpoints with nothing to install, they sit with other remote MCP server options.

Security

Google's security guide says you must screen prompts and responses for malicious content or prompt injection, either with Google Cloud's Model Armor or with your own solution that you document so users can accept the risk. Model Armor floor settings can inspect and block traffic to Google MCP servers across a project. Google warns that with logging turned on Model Armor logs the entire payload, and that in regions Model Armor does not support, routing can differ and may break data residency compliance. The setup guide adds that a connected client can read, modify and delete data in your Google Account, so review every action it takes. Read what to check before installing an MCP server before you connect a work mailbox.

Limits

• Developer Preview only, and program membership is required.
• One server, scope set and connector per product, so a full setup means up to nine connections.
• Gmail has no send tool, and Docs and Slides each expose one read tool and one update tool.
• Service accounts with domain-wide delegation and the default Apps Script OAuth client cannot select the AI agent option. Google documents workarounds for both.

Who it is for

Teams on Google Workspace who want Claude or another agent to search mail, summarize Drive files, update Sheets or find meeting times, and developers building agents on Workspace data who can accept preview terms.

Pricing

As of October 2026, Google does not list a separate price for the Workspace MCP servers on the pages we checked. You need a Google Workspace account accepted into the Developer Preview Program and a Google Cloud project. Model Armor is a separate Google Cloud service.

Alternatives

• Gmail MCP server for a community Gmail server you run yourself (its repository is archived).
• Google Drive MCP server for the archived reference Drive server.
• Zapier MCP if you want Google apps and many other apps behind one connector.

What we could not verify

• The official MCP Registry search on 2026-10-27 returned no entry for these servers, only a separate Google Workspace developer documentation server.
• Google does not say when the servers will leave Developer Preview.
• The setup page lists only read-only and free/busy scopes for Calendar, while the Calendar server also has write tools such as create_event. Check the Calendar MCP reference before you rely on writes.

Sources

• Configure the Google Workspace MCP servers: https://developers.google.com/workspace/guides/configure-mcp-servers
• Configure security for Google Workspace MCP servers: https://developers.google.com/workspace/guides/configure-mcp-security
• Google Workspace Developer Preview Program: https://developers.google.com/workspace/preview
• Gmail MCP reference: https://developers.google.com/workspace/gmail/api/reference/mcp