GWS Connector
Multi-account Google Workspace MCP server — connect multiple Gmail, Google Calendar, and Google Drive accounts with smart routing.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
mcpb https://github.com/orieg/gws-connector/releases/download/v0.4.3/gws-mcp.mcpbClaude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add orieg-gws-connector -- mcpb https://github.com/orieg/gws-connector/releases/download/v0.4.3/gws-mcp.mcpbรันในเทอร์มินัล
{ "mcpServers": { "orieg-gws-connector": { "command": "mcpb", "args": [ "https://github.com/orieg/gws-connector/releases/download/v0.4.3/gws-mcp.mcpb" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดWorks with Claude Code, Gemini CLI, GitHub Copilot, Cursor, OpenAI Codex, and any MCP-compatible client.
Most AI coding assistants support a single Google account. If you use multiple Google accounts (personal + work, multiple clients, different orgs), you need to switch between them manually. This MCP server lets you connect them all at once and route requests by label, email, or domain.
work), email, or domainThere are several good Google Workspace MCP servers. GWS Connector is the one to pick when multiple accounts and operational simplicity matter:
If you only ever use a single Google account and want the widest possible tool surface (Forms, Chat, Vault, …), a single-account server like taylorwilsdon/google_workspace_mcp may fit better. GWS Connector focuses on doing multi-account Gmail / Calendar / Drive / Sheets / Docs / Contacts / Tasks / Slides cleanly and securely.
The Google Tasks tools (gws.tasks.*) are added behind one new OAuth scope
(tasks). Existing users must re-authorize each connected account so new
tokens are minted with this scope:
/gws:reauth
Before approving the browser consent screen, review what the new scope grants — full read and write access to the account's Google Tasks lists and tasks. See the scope rationale table below for details.
You must also add the tasks scope and enable the Tasks API in your GCP
project's OAuth consent screen configuration before re-auth, or the consent
screen will reject the request. Until an account is re-authorized, the
gws.tasks.* tools return an insufficient-scope error naming the reauth tool
to run.
The Contacts tools (gws.contacts.search, gws.contacts.directory_search)
add two new read-only OAuth scopes (contacts.readonly, directory.readonly).
Existing users must re-authorize each connected account so new tokens are
minted with these scopes:
/gws:reauth
Before approving the browser consent screen, review what the new scopes grant — read-only access to your Google Contacts and (for Workspace accounts) the organization directory. See the scope rationale table below for details.
You must also enable the People API and add the two new scopes in your GCP
project's OAuth consent screen configuration before re-auth, or the consent
screen will reject the request. gws.contacts.directory_search requires a
Google Workspace account — personal Gmail accounts have no organization
directory and receive a clear explanatory message instead of results.
The Slides tools (gws.slides.*) add one new OAuth scope,
https://www.googleapis.com/auth/presentations. Existing users must
re-authorize each connected account so new tokens are minted with the
Slides scope:
/gws:reauth
You must also enable the Slides API and add the presentations scope in
your GCP project's OAuth consent screen configuration before re-auth, or the
consent screen will reject the request (see Google Cloud
Setup). Until you re-authorize, gws.slides.* calls
return a scope error telling the agent to run gws.accounts.reauth; all other
tools keep working.
v0.3.0 adds native Google Sheets and Google Docs tools behind two new OAuth
scopes (spreadsheets, documents). Existing users must re-authorize
each connected account so new tokens are minted with these scopes:
/gws:reauth
Before approving the browser consent screen, review what the new scopes grant — full read and write access to every spreadsheet and document in that account's Google Drive, including files shared with the account. See the scope rationale table below for details.
You must also add the two new scopes (and enable the Sheets and Docs APIs) in your GCP project's OAuth consent screen configuration before re-auth, or the consent screen will reject the request.
1. Install the plugin — run these two commands inside Claude Code:
/plugin marketplace add orieg/gws-connector
/plugin install gws@gws-connector
2. Set up Google Cloud credentials — the interactive wizard walks you through everything:
/gws:configure
This creates a GCP project, enables APIs, and connects your first account. See Google Cloud Setup if you prefer manual steps.
3. Connect additional accounts:
/gws:add-account
Each account can use different OAuth credentials from different GCP projects.
gemini extensions install https://github.com/orieg/gws-connector
The binary is downloaded automatically on first use. Then connect accounts inside Gemini:
gws.accounts.add(label: "personal", clientId: "your-client-id", clientSecret: "your-secret")
Download a prebuilt binary or build from source:
git clone https://github.com/orieg/gws-connector && cd gws-connector && make build
Then configure your client:
Connect accounts via MCP tool call:
gws.accounts.add(label: "personal", clientId: "your-client-id", clientSecret: "your-secret")
Environment variables (all optional): GWS_GOOGLE_CLIENT_ID, GWS_GOOGLE_CLIENT_SECRET, GWS_STATE_DIR
The --use-dot-names flag uses gws.mail.search naming; without it, tools use gws_mail_search.
git clone https://github.com/orieg/gws-connector
cd gws-connector
make build
claude --plugin-dir ./
Use /reload-plugins inside the session after making changes. Run claude --debug --plugin-dir ./ to troubleshoot plugin loading.
Each release attaches a
one-click gws-mcp.mcpb bundle. Download it and open it with Claude Desktop
(Settings → Extensions → install from file), or drag it in. The bundle contains
the binaries for macOS and Linux and picks the right one for your machine
automatically. You still complete the Google Cloud setup
and connect accounts on first use.
The server is also published to the
official MCP Registry as
io.github.orieg/gws-connector, so MCP clients that browse the registry can find
and install it directly.
A multi-arch image is published to GHCR on each release:
docker run -i --rm ghcr.io/orieg/gws-connector:latest
The server speaks MCP over stdio. Interactive OAuth (accounts.add / reauth)
opens a browser and stores secrets in the OS keychain, so it needs host access —
day-to-day use is best via the native binary, the Claude Code plugin, or the
Gemini extension. The image is well suited to headless stdio integrations and to
registry/introspection checks. Persist the account registry across runs by
mounting a volume and pointing GWS_STATE_DIR at it:
docker run -i --rm -v gws-state:/state -e GWS_STATE_DIR=/state \
ghcr.io/orieg/gws-connector:latest
All gws.* tools accept an optional account parameter:
# Uses default account
gws.mail.search(q: "is:unread")
# Target by label
gws.cal.list_events(account: "work")
# Target by email
gws.drive.search(account: "[email protected]", q: "quarterly report")
Interactive workflows available in both Claude Code and Gemini CLI:
Once accounts are connected, just ask your assistant in plain language — it picks the tools and the account. Examples:
Tips:
One-time setup:
Go to Google Cloud Console and create a new project (e.g., "GWS Connector")
Enable APIs — click each link and hit "Enable":
Configure the OAuth consent screen:
Add scopes — go to Data Access:
https://www.googleapis.com/auth/gmail.modifyhttps://www.googleapis.com/auth/calendarhttps://www.googleapis.com/auth/drivehttps://www.googleapis.com/auth/spreadsheetshttps://www.googleapis.com/auth/documentshttps://www.googleapis.com/auth/contacts.readonlyhttps://www.googleapis.com/auth/directory.readonlyhttps://www.googleapis.com/auth/taskshttps://www.googleapis.com/auth/presentationshttps://www.googleapis.com/auth/userinfo.emailhttps://www.googleapis.com/auth/userinfo.profileWhy each scope is requested:
Add test users — go to Audience:
Create OAuth credentials — go to Clients:
If you connect accounts from different Google Workspace orgs, each org needs its own GCP project. Create OAuth credentials in each project and provide them when connecting:
gws.accounts.add(label: "work", clientId: "work-client-id", clientSecret: "work-secret")
gws.accounts.add(label: "personal", clientId: "personal-client-id", clientSecret: "personal-secret")
Client secrets are stored in the OS keychain. Client IDs are stored in the account registry.
gws-connector/
├── cmd/gws-mcp/ # MCP server entrypoint
├── internal/
│ ├── accounts/ # Account registry & router
│ ├── auth/ # OAuth flow, token store, client factory
│ ├── server/ # MCP tool registration & dispatch
│ └── services/ # Gmail, Calendar, Drive API wrappers
│
├── .claude-plugin/ # Claude Code plugin manifest + marketplace
├── .mcp.json # Claude Code MCP config
├── gemini-extension.json # Gemini CLI extension manifest
├── CONTEXT.md # Shared behavioral context (both agents)
├── skills/ # Slash commands (Claude Code + Gemini CLI)
├── hooks/ # Claude Code session hooks
├── agents/ # Claude Code workspace agent
│
├── .vscode/mcp.json # GitHub Copilot MCP config
├── .cursor/mcp.json # Cursor MCP config
└── codex.json # OpenAI Codex CLI config
~/.claude/channels/gws/accounts.json (contains client IDs and metadata, no secrets)make build # Build binary
make test # Run tests with race detector
make test-verbose # Run tests with verbose output
make lint # Run go vet
make release # Cross-compile for all platforms
make clean # Remove build artifacts
MIT — see LICENSE.
Multi-account Google Workspace MCP server — Gmail, Calendar, and Drive with smart routing. Plugin for Claude Code and Gemini CLI.
{ "mcpServers": { "orieg-gws-connector": { "command": "mcpb", "args": [ "https://github.com/orieg/gws-connector/releases/download/v0.4.3/gws-mcp.mcpb" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Gws Connector ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Multi-account Google Workspace MCP server — Gmail, Calendar, and Drive with smart routing. Plugin for Claude Code and Gemini CLI.