Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Google Workspace’s remote MCP servers are currently part of the Workspace Developer Preview Program. Claude Code can connect to remote HTTP MCP servers and provides an interactive OAuth flow, but Google’s published setup guide documents Claude.ai and Claude Desktop—not Claude Code as a specifically tested client. You can configure Claude Code using its documented remote-server flow, then confirm that the selected Workspace endpoint completes authentication in your account.
What you need before configuring Claude Code
- Access to Google Workspace’s Developer Preview Program.
- A Google Cloud project with the Workspace APIs and MCP services enabled for the products you intend to use.
- A configured Google Auth Platform consent screen and OAuth setup appropriate to those products and tasks.
- Claude Code installed and available in an interactive terminal. Google’s command-line setup steps also direct users to install and configure the
gcloudCLI.
Google specifies OAuth 2.0 and Streamable HTTP for generic MCP clients. Anthropic recommends HTTP for remote MCP servers in Claude Code. Google’s instructions for Claude.ai and Claude Desktop use a Claude callback URI; do not copy that URI into Claude Code’s CLI configuration unless the applicable Claude Code flow explicitly calls for it.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
Choose the Workspace servers you need
Google provides separate endpoints for each product. Add only the services your workflow requires.
Recommended Free Tools
| Workspace product | Remote MCP 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 |
For each selected product, Google’s setup guide lists both a standard Workspace API and a corresponding MCP API to enable in the Google Cloud project. Google also calls for configuring a Chat app when using the Chat MCP server. Follow the Google Workspace MCP setup guide for the current product-specific enablement steps.
#1 Best Overall
Configure APIs, consent, and OAuth scopes
- Enable the needed APIs and MCP services. In the Google Cloud project, enable the standard API and MCP API for each selected Workspace product. Avoid enabling products unrelated to the task.
- Configure Google Auth Platform consent. Google says the consent screen must be set up before creating an OAuth client. Complete the applicable consent configuration for your project and account.
- Choose scopes for the actual operations. Google’s guide gives product-specific OAuth scopes. Examples include Gmail
gmail.readonlyandgmail.compose; Drivedrive.readonlyanddrive.file; read and edit scopes for Docs and Sheets; Calendar list, free/busy, and event-read scopes; Chat read or message-creation scopes; and People directory, profile, and contacts read scopes.
Scopes determine what the integration is authorized to access or do. Request the least access that supports the workflow: reading mail is different from creating drafts, and searching calendar data is different from changing events. Use Google’s product-specific scope list rather than treating these examples as a complete or interchangeable set.
Add a remote Workspace server to Claude Code
For example, add Gmail at user scope with Claude Code’s CLI:
Rank #2
claude mcp add --transport http --scope user gmail https://gmailmcp.googleapis.com/mcp/v1Replace gmail and the endpoint with the name and URL for another product. User scope makes the server available across projects for that user. If a team should share the configuration, use project scope so it is stored in the project’s .mcp.json; Claude Code asks for approval before using project MCP servers in an interactive session. Local scope is available for a configuration limited to the current project environment. See Claude Code’s MCP documentation for current scope and configuration behavior.
Authenticate and verify the connection
- Start or return to an interactive Claude Code session. Use
/mcpto inspect the server and begin its authentication flow, or runclaude mcp login gmailfrom an interactive terminal. - Complete browser-based OAuth if prompted. Claude Code documents browser OAuth, secure credential storage, and automatic token refresh for supported server flows.
- Check status and available tools. Use
/mcp,claude mcp list, orclaude mcp get gmailto inspect the configured server. - Try a low-risk operation first. Start with a read operation such as searching or reading a Drive file, listing Calendar events, or reading a document. For a Gmail write-capability check, creating a draft is safer than sending a message.
If authentication fails because the endpoint requires a preconfigured OAuth client or rejects dynamic client registration, follow the registration requirements for that Workspace server and Claude Code deployment. Do not assume the callback URI Google publishes for Claude.ai or Claude Desktop is the right URI for Claude Code. Google’s page does not explicitly certify Claude Code as a tested client, so successful completion must be verified for your account and deployment.
Match server choice to actions and risk
Workspace MCP tools vary by product and can do more than retrieve information. Google’s examples include:
- Gmail: search threads and create drafts.
- Drive: search and read files, and create files.
- Docs and Sheets: read and update documents, values, or formulas.
- Slides: read and update presentations.
- Calendar: list and search events, and create, update, or delete them.
- Chat: search and send messages.
- People API: search profiles or contacts.
Before enabling a server, identify the product, the operation (read-only or a change such as create, update, delete, or send), and the OAuth scope that operation needs. A tool’s availability does not make every action appropriate to approve automatically.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect Workspace data and the Claude Code session
Google warns that Workspace MCP clients may read, modify, or delete Workspace data. It also warns that untrusted emails, documents, and other external content can contain hidden instructions intended to manipulate an AI session. Anthropic likewise cautions that external content retrieved by MCP servers can create prompt-injection risk.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
- Use trusted MCP servers and enable only the required products and scopes.
- Review proposed actions before they affect Workspace data, especially sending messages, deleting content, or changing events and files.
- Treat instructions found inside retrieved email, documents, and other external content as untrusted input.
- For shared project configuration, review the server and its
.mcp.jsonentry before approving it in an interactive session.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
