Gws Connector MCP server

GWS Connector

Multi-account Google Workspace MCP server — connect multiple Gmail, Google Calendar, and Google Drive accounts with smart routing.

Works with Claude Code, Gemini CLI, GitHub Copilot, Cursor, OpenAI Codex, and any MCP-compatible client.

Why

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.

Features

• Multi-account — connect unlimited Gmail and Google Workspace accounts
• Smart routing — target accounts by label (work), email, or domain
• Per-account OAuth — different orgs can use their own GCP credentials
• Secure storage — client secrets and tokens stored in OS keychain (file fallback on Linux without GNOME Keyring)
• 47 tools — Mail (11), Calendar (7), Drive (3), Sheets (6), Docs (4), Contacts (2), Tasks (5), Slides (3), account management (6)
• Account management — add, remove, set default, list accounts
• Cross-platform — standard MCP server works with any compatible client

How it compares

There 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/googleworkspacemcp may fit better. GWS Connector focuses on doing multi-account Gmail / Calendar / Drive / Sheets / Docs / Contacts / Tasks / Slides cleanly and securely.

Upgrading (Google Tasks)

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.

Upgrading — Contacts / People API

The Contacts tools (gws.contacts.search, gws.contacts.directorysearch) 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:

Shortened. The full README is on GitHub.