Google Workspace (multi-account)

io.github.bakissation由 GitHub 帳號 bakissation 發布v6.2.0更新於 Nov 4, 2026

Multi-account Google Workspace MCP server: 944 tools, 29 services, discover-first, BYO OAuth.

概覽

AI 產生的概覽

本機 MCP 伺服器,把 Gmail、雲端硬碟、日曆、試算表、文件等 Google Workspace API 開放為工具,並支援多個 Google 帳號。

可以做什麼
  • 以 Markdown 讀取、寄送與回覆 Gmail 郵件,支援附件
  • 操作雲端硬碟檔案、Docs、Sheets、Slides、Forms 與聯絡人
  • 管理日曆活動、Tasks、Chat、Meet 與 Classroom
  • 查詢 Analytics(GA4)與 Search Console 資料
  • 管理 Vault 與 Admin 服務,並為其他 API 方法提供通用入口
  • 依別名切換帳號,或把一次呼叫分送到所有帳號
適用情境
適合讓助理直接在你的 Google 帳號裡工作:整理郵件、起草回覆、讀取或編輯文件與試算表、查看日曆、取得分析資料;需要同時使用多個 Google 帳號時特別有用。
執行需求
透過 npx 以 stdio 在本機執行(需 Node.js 22 以上),也可作為 Claude Desktop 擴充套件安裝。需要自建 Google Cloud OAuth 桌面用戶端:GOOGLE_CLIENT_ID、GOOGLE_CLIENT_SECRET,以及列出別名與電子郵件的 GOOGLE_ACCOUNTS。每個帳號需在瀏覽器登入授權;未設定 MASTER_KEY 時會自動產生。
安裝前請注意
需要你自己的 Google OAuth 用戶端憑證,並授予伺服器存取 Google 資料的權限;權杖在本機加密儲存。寫入預設為拒絕,但可開啟,因此可能寄信、修改或刪除內容。伺服器只與 Google 通訊,但用戶端密鑰與主密鑰須妥善保管。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Google Workspace (multi-account),將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-google-multi

The most complete local Google Workspace MCP server: Gmail, Drive, Calendar, Sheets, Docs, Slides, Forms, Contacts, Tasks, Chat, Meet, Analytics (GA4), Search Console, Classroom, Vault, Admin and more — every OAuth-reachable API method as a tool, across multiple Google accounts at once, from Claude Code or any MCP client.

[npm]

  • 🧰 Exhaustive — 944 tools across 29 services, now including Google Analytics (GA4), + an escape hatch for anything else → COVERAGE.md
  • 🔑 Multi-account — drive any number of Google accounts by alias, or fan one call out across all of them
  • 🔒 Private by design — your own OAuth app, tokens encrypted at rest (AES-256-GCM), writes deny-by-default, no telemetry, no metering — it talks only to Google
  • 🌐 Local or remote — runs locally over stdio, or self-hosted over HTTP with its own built-in OAuth 2.1 server (Claude Code's /mcp login and the claude.ai connector, zero custom UI). Pull-and-up Docker Compose with optional automatic HTTPS → remote setup
  • ✉️ Built for real work — send and read email in Markdown with attachments and one-call replies, an interactive setup wizard with a doctor self-check, and per-account scope profiles → features tour

Quick setup

New to all this? It's written for someone who just installed Claude Code and has never made an API key. Copy-paste each step; it says what you'll see. (Already technical? The Configuration reference is the terse version.)

  1. Install it. Get Node.js (the green "LTS" button, version 22 or newer), then run:

    bash
    npm install -g mcp-google-multi

    Claude Desktop user? You can skip npm entirely: download the mcp-google-multi.mcpb bundle from the latest release, double-click it (or drag it into Claude Desktop → Settings → Extensions), and fill in the values from step 2 when prompted.

  2. Make your Google key (the one manual part, a few minutes, because Google has no way to script it). Follow the step-by-step Google Cloud setup, or just ask Claude Code: "walk me through creating a Google OAuth Desktop client for mcp-google-multi." You finish with two values, a Client ID and a Client Secret. It's free and private to you.

  3. Put them in a file. In the folder you'll run from, make a file named .env and paste this, filling in your values:

    bash
    GOOGLE_CLIENT_ID=paste-your-client-idGOOGLE_CLIENT_SECRET=paste-your-client-secret# any short nickname, then your Gmail address:GOOGLE_ACCOUNTS=me:[email protected]

    No encryption key to make: the server generates and stores one for you.

  4. Sign in. A browser opens; pick your account and click Allow:

    bash
    mcp-google-multi auth --account me
  5. Add it to Claude Code, then restart Claude Code:

    bash
    claude mcp add mcp-google-multi -s user -- npx -y mcp-google-multi

Stuck at any point? Run mcp-google-multi doctor. It inspects every part and prints the exact fix for anything wrong (a missing sign-in, a Google API you still need to switch on, and so on). Once it reads all-green, just talk to Claude: "summarize my unread email."

Got more than one Google account? Add them together, like GOOGLE_ACCOUNTS=me:[email protected],work:[email protected], and run step 4 once per nickname.

On a server or from claude.ai? Advanced path: Remote / HTTP setup. Coming from v5? v6 migration guide.

Go deeper: Configuration reference · What's covered · Features tour · Remote / HTTP setup · Secrets in a vault · Local usage metrics · Migrating to v6 · Security policy · Roadmap

Agent skill

The repo and the npm package both ship an Agent Skill at skills/google-workspace/: a hand-written SKILL.md covering account selection, the discover step, incremental Gmail sweeps, keeping results small, write profiles, and the escape hatch, plus a reference/ folder with a generated argument table per service. Loading it gets an agent calling this server's tools correctly without guessing argument names.

To install it for Claude Code, copy or symlink the skills/google-workspace folder into ~/.claude/skills/ (every project) or a project's own .claude/skills/ (that project only):

bash
# from a cloned copy of this repoln -s "$(pwd)/skills/google-workspace" ~/.claude/skills/google-workspace
# from the installed npm packageln -s "$(npm root -g)/mcp-google-multi/skills/google-workspace" ~/.claude/skills/google-workspace

Maintainer, sponsor & license

Built and maintained by Abdelbaki Berkati — berkati.xyz · @bakissation. Read the case study →

Development is funded by IdeaCrafters (@IdeaCraftersHQ) — the studio that pays for this OSS to exist.

An Enterprise Edition (hosted, multi-tenant) is available: ask through berkati.xyz (email or LinkedIn there).

Thanks to contributors @obatried, @trevor-commits, and @mjreddy. The project is maintainer-led (roadmap on Milestones; bug reports welcome, feature PRs by prior agreement — see CONTRIBUTING.md). Feedback shapes the roadmap: open an issue with bugs, pain points, or what you wish it did. Security reports go to SECURITY.md, never a public issue.

Licensed under MIT.

來源:README.md,提交 45842e2

工具

0
SourceWeft 曾在隔離沙箱中以無憑證方式啟動該軟體包一次,以列出其工具,但未能完成:伺服器未能啟動。

版本歷史

5
  1. v6.2.0最新Nov 4, 2026
  2. v6.1.1Oct 26, 2026
  3. v6.1.0Oct 20, 2026
  4. v6.0.1Oct 18, 2026
  5. v6.0.0Oct 14, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分