Google Workspace logo

Google Workspace

Connects AI agents to Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet, and Contacts through one MCP server.

Install Google Workspace

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-workspace-2": {
      "command": "npx",
      "args": [
        "-y",
        "@aaronsb/google-workspace-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @aaronsb/google-workspace-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 8d ago.

Overview

Google Workspace MCP server connects AI agents to Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet, and Contacts through Google APIs. It uses OAuth credentials and stores account tokens locally, supporting multiple Google accounts with per-account routing and optional read-only access. Reach for it when an agent needs to search, read, create, update, or move Workspace data through conversation, including workflows that span several services.

Use cases

  • Search Gmail and save an attachment to Drive
  • Create a Calendar event and check participant availability
  • Draft documents and update spreadsheet ranges
  • Create Tasks from information found in email
  • Manage personal and work Google accounts separately

Key features

  • Access to eight Google Workspace services
  • Multi-account OAuth handling
  • Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet, and Contacts tools
  • Bulk operation chaining and batch requests
  • Local workspace sandbox for files and exports
  • Scratchpad support for multiline and structured content

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14h ago via OSV.dev · @aaronsb/google-workspace-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars192Stargazers on the source repository.
npm downloads6.5kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Workspace works

What the Google Workspace MCP server does

The Google Workspace MCP server gives an MCP-compatible agent access to eight Google services through a single local process. It can work with Gmail, Calendar, Drive, Sheets, Docs, Tasks, Meet, and Contacts. Operations include reading and writing data, managing files and permissions, creating meetings, editing documents, handling tasks, and working with contacts.

The server also provides account management, a scratchpad for composing structured or multiline content, a workspace sandbox for files, and bulk operations. Responses include guidance about available next steps, helping an agent continue a multi-stage task without having to infer every possible follow-up action.

How it works

The agent sends tool calls to the local server over MCP. The server selects the relevant Google account, builds the corresponding API request, and returns data shaped for agent use. OAuth tokens remain on the user's machine, and requests are made to Google on behalf of the authenticated account. Multiple personal or work accounts can be configured and used side by side.

Bulk execution supports two patterns: chaining different operations while passing earlier results into later steps, or applying one operation to multiple resources in a single Google request where the API supports it. The documented batch cases include Gmail trash and label changes, plus contact create, update, delete, and get operations.

Setup and configuration

Install the Google Workspace MCP server with Node.js 22.12 or newer, or use the packaged .mcpb bundle for Claude Desktop. Google OAuth 2.0 credentials are required: create a Desktop application client, enable the Google APIs needed for the services you plan to use, and provide the client ID and secret.

For Claude Code, the documented setup uses claude mcp add with GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, launching the package through npx. Other MCP clients can use the same stdio command and environment variables in their MCP configuration. Claude Desktop's bundle also accepts an optional workspace directory for attachments, downloads, and exports; otherwise, it uses a default directory under the user's local data path.

Tools and capabilities

The server exposes these tool areas:

  • manage_email: Search, read, send, reply, forward, triage, label, draft, trash, and handle Gmail threads and attachments.
  • manage_calendar: List calendars and events, inspect agendas, create or update events, delete events, use quick-add, and check free/busy status.
  • manage_drive: Search, upload, download, copy, move, rename, delete, export, comment on, and manage permissions for Drive files.
  • manage_sheets and manage_docs: Read and edit spreadsheet ranges, manage tabs, create or append document content, and perform text replacement.
  • manage_tasks, manage_meet, and manage_contacts: Manage task lists, meeting spaces and conference records, and saved or directory contacts.
  • manage_accounts, manage_scratchpad, and manage_workspace: Configure accounts, prepare content and attachments, and manage files in the local sandbox.
  • bulk_operations: Chain calls or apply supported operations across multiple resources.

Limitations and notes

Google OAuth setup is required before use, and each desired Google service may require its API to be enabled in the Google Cloud console. Contacts use Google's People API. The packaged installation is specifically documented for Claude Desktop; other clients require an MCP configuration entry. The workspace directory should be dedicated rather than pointing at a home, Documents, Desktop, or Google Drive folder.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Workspace

Google Workspace is an MCP server that connects an AI agent to Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet, and Contacts. Its main tools manage email, calendars, files, spreadsheets, documents, tasks, meetings, contacts, accounts, scratchpad content, workspace files, and bulk operations.

Install it with Node.js 22.12 or newer, configure Google OAuth credentials, and add the package as an MCP stdio server. Claude Desktop users can install the `.mcpb` release bundle, while Claude Code users can run the documented `claude mcp add` command.

It needs a Google OAuth 2.0 Client ID and Client Secret for a Desktop application. Enable the Google APIs for the services you plan to use, then provide `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` to the server.

Yes, it supports multiple Google accounts and keeps an OAuth token for each account on the local machine. The account management tools handle account setup and scopes, while the server routes requests to the selected account.

Yes, `bulk_operations` can chain different actions and pass results between them, or apply one supported operation to multiple resources. Documented batch cases include Gmail trash and label changes and several contact operations.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Workspace AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-workspace-2?style=directory)](https://allmcps.com/mcp/google-workspace-2)
HTML Embed
<a href="https://allmcps.com/mcp/google-workspace-2"><img src="https://allmcps.com/api/badge/google-workspace-2?style=directory" alt="Google Workspace on AllMCPs" /></a>