Vanta's official remote MCP server — query controls, tests, vendors, vulnerabilities and policies across SOC 2 and ISO 27001, and remediate failing tests from your agent.
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.
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,sheetsmcpandslidesmcp— 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
Attio's official hosted MCP server — search, read and write your CRM records, lists, notes, tasks, meetings and emails from any MCP client over OAuth.
Fireflies.ai's official remote MCP server — 19 tools for searching meeting transcripts and summaries, pulling action items and analytics, and cutting soundbites from recorded calls.
ClickUp's official remote MCP server — around 40 tools across tasks, search, Docs, Chat and time tracking, over OAuth 2.1 with PKCE.
