The servers and their endpoints
For the products themselves, Google does not offer one “Workspace MCP server” but one per product, all remote, all over Streamable HTTP with OAuth 2.0:
| Product | Endpoint |
|---|---|
| Gmail | https://gmailmcp.googleapis.com/mcp/v1 |
| Google Drive | https://drivemcp.googleapis.com/mcp/v1 |
| Google Docs | https://docsmcp.googleapis.com/mcp/v1 |
| Google Sheets | https://sheetsmcp.googleapis.com/mcp/v1 |
| Google Slides | https://slidesmcp.googleapis.com/mcp/v1 |
| Google Calendar | https://calendarmcp.googleapis.com/mcp/v1 |
| Google Chat | https://chatmcp.googleapis.com/mcp/v1 |
| People API | https://people.googleapis.com/mcp/v1 |
| Google Classroom | https://classroommcp.googleapis.com/mcp/v1 |
According to Google’s announcement, Gmail covers profile access, drafting, searching and read/write; Drive covers fetching files, listing, uploading and managing permissions; Calendar finds free times and manages events; Chat finds conversations, searches messages and reads and sends replies.
Next to those, Google documents one cross-product server at https://workspacemcp.googleapis.com/mcp/v1, a Developer Preview feature that provides tools for building LLM applications across Drive, Gmail, Calendar and Chat. Its public toolset currently lists a single tool, search_corpus, and the tools/list method returns the current tool specifications, so check that list rather than a blog post before you plan around it.
Setting it up
This is more work than a one-click connector, because you bring your own OAuth app:
- Create a Google Cloud project and sign in with the gcloud CLI.
- Enable the APIs (Gmail, Drive, Calendar and so on) and the matching MCP services, such as
gmailmcp.googleapis.com. - Configure the OAuth consent screen. Choose Internal to keep it inside your organization, and add only the scopes you need. For Gmail the guide lists
gmail.readonlyandgmail.compose. - Create an OAuth client ID of type Web application and tick Use this client for an AI-powered agent. Without it, requests may be rejected.
- Add the servers to your client. In Claude, add one custom connector per product. In Google Antigravity, add them to
mcp_config.json. Any client that supports remote MCP over Streamable HTTP with OAuth 2.0 should work. - Ask for offline access (
access_type=offline), or users will be asked to sign in again about every hour.
Admins can review OAuth log events in the security investigation tool, and API access in general is managed under Security, API controls in the Admin console.
The common misunderstanding
“Read-only means safe.” Reading is exactly where the main risk with mail sits. Google’s own guide warns that untrusted emails, documents or other inputs may contain hidden instructions, and advises using only trusted clients and reviewing every action the agent takes. An AI that reads your inbox also reads every stranger’s mail in it. Give the agent compose rights only if people review drafts before they go out. More on this in is MCP safe to use in a company.
What this means for a team
The access is per user: each person signs in, and their AI sees their mailbox and the Drive files they can open. That is the right security model, but it also means nobody’s AI sees the shared picture. One colleague’s AI knows the customer thread in their inbox; another colleague’s AI knows the proposal in their Drive. Neither knows what the team decided. For setting up connections across tools, see how to connect MCP to Claude, ChatGPT, Copilot and Grok, and for the bigger pattern, how to give AI agents your company context.
Where Bombos fits
Google’s MCP servers let each person’s AI open their own mail and files; Bombos gives every AI on the team one shared memory that draws on what already sits in mail, documents and repos. It is a plugin underneath Claude, ChatGPT, Copilot, Grok, Codex, Cursor and your own agents that learns how your team works and shows with every answer what it rests on. It runs in the cloud in Europe or standalone on your own server, and one person can try it first with their own agents.
Related questions
Can the Gmail MCP server send email?
The documented Gmail scopes are gmail.readonly and gmail.compose. Google describes the Gmail tools as profile access, drafting, searching and read/write. Check the tool list in your client before you rely on any send behavior.
Do I need to be in a preview program?
Google's configuration guide says the servers are in Developer Preview, which requires membership in the Google Workspace Developer Preview Program. The Workspace Updates post called it a public developer preview available to all Workspace customers and developers.
How do I connect it to Claude?
Add a custom connector in Claude for each product (Gmail, Drive and so on), and enter your OAuth client ID and secret under Advanced settings. Use the redirect URI https://claude.ai/api/mcp/auth_callback. Google lists Claude Pro, Max, Team and Enterprise.
Why do users have to sign in every hour?
Without access_type=offline in the authorization request, no refresh token is issued and users must sign in again about every hour.
What about the community Google Workspace MCP servers?
Several open source servers exist, such as the workspace-mcp package. They are not from Google. Now that Google runs its own endpoints, check whether you still need one.
