Google Workspace MCP Server: Complete Setup Guide for Claude (2026)

Table of Contents

1. What Is the Google Workspace MCP Server?
2. Why One Server Beats Five Separate MCPs
3. What It Can Actually Do
4. Setup: OAuth, Scopes, and Config
5. Google Workspace MCP Options Compared
6. Security: Scoping OAuth Correctly
7. Common Errors and Fixes
8. Frequently Asked Questions

What Is the Google Workspace MCP Server?

The Google Workspace MCP server is a Model Context Protocol server that bridges an AI client and your Google account. Once connected, your assistant treats Gmail, Calendar, Drive, Sheets, and Docs as native tools — it can search your mail, read a thread, create a calendar event, open a spreadsheet, or draft a doc, all inside a single conversation.

The Model Context Protocol was published by Anthropic in late 2024 and adopted across every major AI client through 2025. By 2026 the ecosystem covers 75,000+ MCP servers indexed across Smithery, Glama, PulseMCP, LobeHub, and mcp.directory — and the Google Workspace servers are consistently among the most installed in the productivity category, because almost everyone already lives inside Google's apps all day.

Unlike a single-purpose MCP that touches just one app, a Workspace server authenticates once and exposes the whole suite. That single-login design is the reason it has become the default way to give an AI assistant access to your working day.

Why One Server Beats Five Separate MCPs

You could install separate Gmail, Drive, and Sheets MCP servers — and for a narrow workflow, that is sometimes the cleaner choice. But for most people, a single Workspace server wins on three counts:

• One OAuth flow. You authenticate a single Google Cloud project instead of granting consent five times and juggling five token files.
• Cross-app workflows. "Find the budget spreadsheet in Drive, read the Q3 tab, and email the total to my manager" touches Drive, Sheets, and Gmail in one breath. Separate servers make Claude stitch tools across processes; one server keeps the context unified.
• Simpler config. A single mcpServers entry instead of five, with one set of credentials to rotate when a token expires.

The trade-off is blast radius: one server with broad scopes can touch more of your account. We cover how to constrain that in the security section.

What It Can Actually Do

Gmail: Read, Search, Draft, Send

Search your mailbox with Gmail's native query syntax (from:boss is:unread newer_than:7d), read full threads, and either draft or send replies. The most common safe pattern is draft-first: Claude composes the reply into your Drafts folder, you review, you send. Pair it with the Gmail MCP review if email is your primary use case.

Calendar: Schedule and Reschedule

Create events, check availability across calendars, find a free slot, and move meetings. "Schedule a 30-minute sync with the design team Thursday afternoon" becomes a single tool call that respects your existing events.

Drive: Find and Read Files

Search Drive by name or content, list folders, and read the contents of Docs, Sheets, and plain files into Claude's context. This is the glue that lets the assistant pull a source document before answering a question about it.

Sheets: Query and Update Cells

Read ranges, append rows, and update cells. Useful for lightweight reporting — "add today's signups to the metrics sheet" — and for pulling structured data into an analysis without exporting CSVs. For deeper spreadsheet work see the Google Sheets MCP review.

Docs: Draft and Edit Documents

Create new documents, append sections, and edit existing ones. Combined with Gmail and Drive, this closes the loop on a full research-to-deliverable workflow: gather sources from Drive, draft the doc, email the link.

Setup: OAuth, Scopes, and Config

Setting up the Google Workspace MCP takes about ten minutes, most of it inside the Google Cloud console. The steps:

1. Create a Google Cloud project at console.cloud.google.com (free).
2. Enable the APIs you need — Gmail API, Google Calendar API, Drive API, Sheets API, Docs API.
3. Configure the OAuth consent screen. For personal use, set it to "External" and add your own email as a test user.
4. Create OAuth credentials (Desktop app type). Download the client_secret.json.
5. Add the server to your MCP config. Example for Claude Desktop:

{   "mcpServers": {     "google-workspace": {       "command": "npx",       "args": ["-y", "@taylorwilsdon/google-workspace-mcp"],       "env": { "GOOGLE_OAUTH_CREDENTIALS": "/path/to/client_secret.json" }     }   } }

1. Restart the client and authorize. On first use, a browser window opens for the Google consent flow. Approve the scopes and the server caches a refresh token.

For Claude Code, the equivalent is a single claude mcp add command pointing at the same package and credentials. The Skiln Config Generator can bundle the Workspace server with your other MCPs into one ready-to-paste config.

Google Workspace MCP Options Compared

There is no single "official" Google Workspace MCP, so you choose among well-maintained community servers. The trade-offs:

If you do everything in Google all day, the full Workspace server is the right default. If you only ever touch one app, the single-purpose MCP is lighter and narrower in scope, which is a security win.

Security: Scoping OAuth Correctly

A Workspace MCP holds the keys to your email, calendar, and files — treat its setup with the same care you would a password manager. Three rules:

1. Start read-only. Grant gmail.readonly, drive.readonly, and calendar.readonly first. Add write or send scopes only when a workflow genuinely needs them.
2. Prefer draft-first for Gmail. Letting an agent draft into your Drafts folder — instead of sending directly — eliminates the worst failure mode (a wrong email going out unreviewed).
3. Rotate and revoke. Tokens live in a local cache file. If you stop using the server, revoke its access at myaccount.google.com/permissions. If you suspect a leak, delete the OAuth client in Google Cloud and reissue.

For the broader principles that apply to every credentialed MCP, read our MCP server security guide.

Common Errors and Fixes

• "Access blocked: app not verified." Your OAuth consent screen is in testing mode and you are not listed as a test user. Add your email under the consent screen's test users.
• "Insufficient permission" on a tool call. The scope for that action was not granted. Re-run consent with the broader scope, or check that you enabled the matching API in Google Cloud.
• Token expired / refresh failed. Delete the cached token file referenced in the server's README and re-authorize. This regenerates a fresh refresh token.
• Server not appearing in the client. Check the client logs for a startup error — usually a wrong path to client_secret.json or a missing Node runtime for npx.

If you hit something not listed here, our MCP troubleshooting guide covers the general diagnostic flow for any failing server.

Frequently Asked Questions

What is the Google Workspace MCP server?

The Google Workspace MCP server is a Model Context Protocol server that connects an AI client like Claude Desktop or Claude Code to your Google account, exposing Gmail, Calendar, Drive, Sheets, and Docs as tools the assistant can call. Instead of installing five separate single-app MCPs, one Workspace server authenticates once via OAuth and covers the whole suite.

Is the Google Workspace MCP free?

Yes. The popular community Google Workspace MCP servers are free and open source. You pay nothing beyond your existing Google account. The only cost is the Google Cloud project you create to issue OAuth credentials, which is free for personal use and stays well under any billable threshold for normal API call volume.

Which OAuth scopes does it need?

It depends on which services you enable. Read-only Gmail needs gmail.readonly; sending mail needs gmail.send or gmail.modify. Calendar needs calendar.events. Drive read needs drive.readonly. Sheets needs spreadsheets. Grant only the scopes you actually use — a research workflow rarely needs send or write scopes, so start read-only and expand later.

Does it work with Claude Code and Cursor?

Yes. The Google Workspace MCP implements the standard protocol, so it works in Claude Desktop, Claude Code, Cursor, Windsurf, Cline, and Zed. The config format differs slightly per client, but the OAuth flow and the exposed tools are identical across all of them.

Can Claude send emails on my behalf?

Only if you grant a send scope. With gmail.send or gmail.modify, Claude can compose and send mail. Many users keep the server read-only or draft-only so the assistant prepares messages in your Drafts folder for you to review and send manually. That draft-first pattern is the safest way to use Gmail through an AI agent.

How is this different from the Google Workspace CLI?

The CLI is a command-line tool you run yourself, line by line. The MCP server hands those same capabilities to an AI assistant so it can decide which calls to make mid-conversation. They overlap, but the MCP is for agentic workflows while the CLI is for scripted automation. See our Google Workspace CLI review for the command-line path.

Will it read my entire inbox?

No. The server only fetches what a tool call requests — a search query, a specific thread, or recent messages. It does not bulk-download your mailbox. Each action is scoped to the query Claude issues, and you can watch every call in the client's tool log.

Where can I find Google Workspace MCP servers on Skiln?

Search the Skiln directory for 'google workspace' to see every indexed variant, or browse the productivity category. We track the maintained community servers alongside single-app Gmail, Drive, and Sheets MCPs so you can compare trust scores and pick the best-maintained option.

Last updated: June 21, 2026 · Skiln tracks MCP server releases daily across 13 source registries.