MCP Catalogs
Home

google-workspace-mcp

by aaronsb·150·Score 51

A production-ready MCP server providing authenticated access to Google Workspace APIs including Gmail, Calendar, Drive, Sheets, and more.

productivitycommunicationcloud-storage
48
Forks
4
Open issues
this month
Last commit
2d ago
Indexed

Overview

The Google Workspace MCP Server is a comprehensive implementation that bridges AI agents with Google's productivity suite. It uses a manifest-driven factory approach to transform YAML configurations into functional MCP tools, enabling access to 15+ Google services with approximately 80 operations. The server stands out for its robust architecture, leveraging Google's official Workspace CLI as the underlying engine while adding domain-specific formatting and response handling optimized for AI consumption. Multi-account support with credential isolation makes it suitable for both personal and enterprise use cases.

Try asking AI

After installing, here are 6 things you can ask your AI assistant:

you:AI assistants managing email triage and calendar scheduling through natural conversation
you:Automating document workflows between Gmail, Drive, and Google Sheets
you:Personal productivity AI handling cross-account operations between personal and work Google profiles
you:What Google Workspace services are supported?
you:How are Google credentials stored and managed?
you:Can it handle multiple Google accounts simultaneously?

When to choose this

Choose this MCP server when you need comprehensive, authenticated access to Google Workspace services through AI agents, especially if you're already using Google Workspace APIs and want to leverage the manifest-driven architecture for easy expansion.

When NOT to choose this

Don't choose this if you need access to non-Google services or are concerned about vendor lock-in to Google's ecosystem, as it's specifically designed for Google Workspace APIs.

Tools this server exposes

11 tools extracted from the README
  • manage_email

    Gmail — search, read, send, reply, forward, triage, trash, labels, threads, attachments

  • manage_calendar

    Calendar — list, agenda, get, create, quickAdd, update, delete, calendars, freebusy

  • manage_drive

    Drive — search, get, upload, download, copy, rename, delete, export, permissions, comments

  • manage_sheets

    Sheets — read/write ranges, append, clear, manage tabs, copy/duplicate/rename

  • manage_docs

    Docs — get, create, append, insert text, find-and-replace

  • manage_tasks

    Tasks — list/create/update/complete tasks and task lists

  • manage_meet

    Meet — browse past conferences, participants, transcripts, recordings, smart notes

  • manage_accounts

    Multi-account lifecycle — add accounts, manage credentials and scopes

  • manage_scratchpad

    Compose/edit multi-line content, attach files, send to any target

  • manage_workspace

    File operations in the workspace sandbox

  • queue_operations

    Chain operations sequentially with result references

Comparable tools

microsoft-graph-mcpimap-mcpcalendar-mcpgmail-mcpdrive-mcp

Installation

MCPB Bundle (Recommended)

Download the .mcpb bundle for your platform from the [latest release](https://github.com/aaronsb/google-workspace-mcp/releases)

npm Installation

npm install @aaronsb/google-workspace-mcp

Claude Desktop Configuration

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "google-workspace": {
      "command": "npx",
      "args": ["@aaronsb/google-workspace-mcp"],
      "env": {
        "GOOGLE_CLIENT_ID": "your-client-id",
        "GOOGLE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Prerequisites

  1. Node.js 18+
  2. Google Cloud OAuth credentials from https://console.cloud.google.com/apis/credentials

FAQ

What Google Workspace services are supported?
The server currently supports 7 major services: Gmail, Calendar, Drive, Sheets, Docs, Tasks, and Meet, with approximately 80 operations across these services. Full API coverage is documented in docs/coverage.md.
How are Google credentials stored and managed?
Credentials follow XDG Base Directory specifications, stored per-account in ~/.local/share/google-workspace-mcp/credentials/ with standard OAuth tokens. No secrets are stored in the project directory.
Can it handle multiple Google accounts simultaneously?
Yes, it supports multi-account operations with per-account credential isolation, allowing the agent to work across personal and work accounts simultaneously.

Compare google-workspace-mcp with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.