Hosted MCP

A hosted Google Workspace MCP, with write access

Add one endpoint, sign in with Google, and your agent can edit the spreadsheet rather than describe it. No Google Cloud project, no OAuth client of your own, no per-product endpoints to wire up.

Google-verified since June 2026 · CASA Tier 2 assessed · Open source, self-host it if you prefer

Where the writes actually stop

Most comparisons argue about tool counts. The question that decides it is narrower: when your agent finishes thinking, can it put the answer somewhere.

Read a spreadsheetNative: yesUs: yes
Change a cell in itNative: no Sheets connectorUs: yes
Create a Google DocNative: yes, via DriveUs: yes
Write content into itNative: noUs: yes
Create a presentationNative: yes, and it arrives emptyUs: yes
Put content on the slidesNative: noUs: yes
Send an emailNative: yes, since AugustUs: yes
Work across two Google accountsNative: no, one at a timeUs: yes

The three routes, and when each one wins

Claude's native connectors

Setup:
None
Covers:
Gmail, Calendar, Drive. That is the whole Google surface.
Where it stops:
No Sheets, Docs, Slides, Contacts or Tasks connector at all. One Google account at a time.

Google's official MCP servers

Setup:
A Cloud project, sixteen service enablements, your own OAuth client
Covers:
Eight products, and they write deeply. Sheets, Docs and Slides all take batch updates.
Where it stops:
Developer Preview. Eight separate endpoints to configure. Their own Gmail server cannot send, reply or forward.

This gateway

Setup:
One URL, one Google sign-in
Covers:
Gmail, Drive, Sheets, Docs, Slides, Calendar, Contacts, Tasks, plus Jira and Confluence on the same endpoint.
Where it stops:
We are a third party in the path. No Google Chat tools. Self-host if that trade is wrong for you.

Use something else when

The long version, with every tool enumerated and dated, is in the three-way comparison.