Google Workspace MCP

googleworkspacegmaildrivecalendardocssheetsoauthremote

Summary

Google's own remote MCP endpoints for Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat and People — OAuth 2.0, hosted by Google, no server to run.

Features

Hosted by Google — remote HTTP endpoints, nothing to deploy or patch
Separate endpoint per product so OAuth grants stay narrowly scoped
Gmail: profile, drafting, search, and message read/write
Drive: fetch, list, upload and manage permissions
Docs, Sheets and Slides read/write
Calendar availability lookup and event management
Chat conversation search and reply, plus People contacts
OAuth 2.0 with your own Google Cloud client ID and secret

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

Open your agent's MCP configuration file.
Merge the snippet below into it.
Restart the agent — the "Google Workspace MCP" tools will be available.

{
  "mcpServers": {
    "google-workspace-mcp": {
      "command": "remote",
      "args": [
        "https://gmailmcp.googleapis.com/mcp/v1"
      ]
    }
  }
}

Claude Code

Add the server with a single CLI command.

claude mcp add google-workspace-mcp -- remote https://gmailmcp.googleapis.com/mcp/v1

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

{
  "mcpServers": {
    "google-workspace-mcp": {
      "command": "remote",
      "args": [
        "https://gmailmcp.googleapis.com/mcp/v1"
      ]
    }
  }
}

Gmail. Add as a remote MCP server with OAuth clientId/clientSecret from your Google Cloud Web application credential. Scopes: gmail.readonly, gmail.compose.

{
  "command": "remote",
  "args": [
    "https://gmailmcp.googleapis.com/mcp/v1"
  ]
}

Google Drive — file fetching, listing, uploading and permissions.

{
  "command": "remote",
  "args": [
    "https://drivemcp.googleapis.com/mcp/v1"
  ]
}

Google Calendar — find available times and manage events.

{
  "command": "remote",
  "args": [
    "https://calendarmcp.googleapis.com/mcp/v1"
  ]
}

Google Docs. Sheets and Slides follow the same pattern at sheetsmcp and slidesmcp.

{
  "command": "remote",
  "args": [
    "https://docsmcp.googleapis.com/mcp/v1"
  ]
}

Google Chat — find conversations, search messages, read and send replies.

{
  "command": "remote",
  "args": [
    "https://chatmcp.googleapis.com/mcp/v1"
  ]
}

People API — contacts and profile information.

{
  "command": "remote",
  "args": [
    "https://people.googleapis.com/mcp/v1"
  ]
}

Description

Google Workspace MCP is Google's first-party answer to the many community Workspace bridges: a set of remote MCP servers that Google hosts and operates, announced at Cloud Next '26 and rolling out from 1 May 2026 as a public developer preview.

Rather than one monolithic server, each Workspace product gets a dedicated endpoint under googleapis.com, so you connect only what an agent actually needs and scope its OAuth grant accordingly:

Gmail — https://gmailmcp.googleapis.com/mcp/v1 — profile access, drafting, searching, and read/write on messages
Drive — https://drivemcp.googleapis.com/mcp/v1 — fetching files, listing, uploading, and managing permissions
Docs, Sheets and Slides — docsmcp, sheetsmcp and slidesmcp — read and write documents, spreadsheets and decks
Calendar — https://calendarmcp.googleapis.com/mcp/v1 — find available times and manage events
Chat — https://chatmcp.googleapis.com/mcp/v1 — find conversations, search messages, read and send replies
People — https://people.googleapis.com/mcp/v1 — contacts and profile information

Because the servers are hosted, there is nothing to deploy, patch or keep credentialled on a laptop, and the per-service split means a scheduling agent granted calendar cannot quietly read the inbox. Authentication is standard OAuth 2.0 with your own Google Cloud OAuth client: you register a Web application credential with the redirect URI your client expects (https://claude.ai/api/mcp/auth_callback for Claude, https://antigravity.google/oauth-callback for Antigravity), then grant only the scopes each server needs — Gmail, for instance, uses gmail.readonly and gmail.compose.

Documented clients are Google Antigravity (2.0, IDE and CLI) and Claude on Enterprise, Pro, Max and Team plans; anything speaking MCP over HTTP transport can connect. Access is via the Google Workspace Developer Preview Program, and it is available to Workspace customers and developers without an edition restriction. Existing Cloud projects keep their current quotas, with updated quotas applying to new projects from 1 May 2026.

The trade-off worth weighing against the community alternatives: you get Google's own maintenance, scoping and reliability, but you also inherit preview-programme enrolment and the need to run your own OAuth client rather than pasting an API key.

Related MCP Servers

MCP: Zapier MCP

by Zapier

New

Zapier's official hosted MCP server, exposing actions across 8,000+ connected apps as agent tools — with you choosing exactly which actions each server may perform.

Productivity