Does Google Workspace have an MCP server?

Google's documented first-party route is distinct from community wrappers, because it is first-party against Google's own tenant model rather than a community project's interpretation of the Workspace APIs. A community-built alternative with the same general scope exists and pre-dates Google's server; with an official route published, treat the community build as the fallback, not the default, and note it was written before Google shipped its own and is not reviewed or supported by Google.

Gmail read, draft and search, Drive files and permissions, and Calendar availability and events together form a wide surface across a firm's communications and documents. Confirm exactly which scopes a given connection requests, keep drafting rather than auto-sending where that distinction is offered, and audit the grant as a whole rather than feature by feature.

This summary reflects Google's own documentation page as found in this review; confirm current endpoint and scope details directly, since Workspace's AI tooling has moved quickly. This is informational, not an endorsement of any specific configuration. Start with read-only scopes where supported and keep client-side approval prompts on.