Skip to main content
Glama
README.md
# mcp-google-multi

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

[![npm](https://img.shields.io/npm/v/mcp-google-multi?label=npm&color=cb3837)](https://www.npmjs.com/package/mcp-google-multi)

- ๐Ÿงฐ **Exhaustive** โ€” 872 tools across 28 services + an escape hatch for anything else โ†’ [COVERAGE.md](./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

## Quick setup

You don't need to know anything about MCP or OAuth โ€” five steps, all copy-paste:

1. **Install [Node.js](https://nodejs.org) 20 or newer**, then install the server:

   ```bash
   npm install -g mcp-google-multi
   ```

2. **Create your (free) Google app** so the server can sign in as you โ€” one-time, ~2 minutes: follow [Google Cloud setup](./docs/google-cloud-setup.md). You come back with a **Client ID** and **Client Secret**.

3. **Create a file named `.env`** in the folder you'll run from, and fill in your values:

   ```bash
   GOOGLE_CLIENT_ID=paste-your-client-id
   GOOGLE_CLIENT_SECRET=paste-your-client-secret
   # name each Google account with a short alias:
   GOOGLE_ACCOUNTS=work:you@company.com,personal:you@gmail.com
   # encryption key for stored tokens โ€” generate one with: openssl rand -base64 32
   MASTER_KEY=paste-the-generated-key
   ```

4. **Sign in each account** (a browser window opens; approve the permissions):

   ```bash
   mcp-google-multi auth --account work
   mcp-google-multi auth --account personal
   ```

5. **Connect it to Claude Code** (any MCP client works the same way):

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

Restart your client and the tools appear. Check everything with `mcp-google-multi config check`.

**Go deeper:** [Configuration reference](./docs/configuration.md) ยท [What's covered](./COVERAGE.md) ยท [Features tour](./docs/features.md) ยท [Secrets in a vault](./docs/secrets.md) ยท [Upgrading from v4](./docs/upgrading-v4.md) ยท [Security policy](./SECURITY.md) ยท [Roadmap](https://github.com/bakissation/mcp-google-multi/milestones)

## Maintainer & credits

Built and maintained by **Abdelbaki Berkati** โ€” [berkati.xyz](https://berkati.xyz) ยท [@bakissation](https://github.com/bakissation). [Read the case study โ†’](https://berkati.xyz/case-studies/mcp-google-multi/)

Development is **funded by [IdeaCrafters](https://ideacrafters.com)** ([@IdeaCraftersHQ](https://github.com/IdeaCraftersHQ)) โ€” the studio that pays for this OSS to exist.

Thanks to contributors [@obatried](https://github.com/obatried), [@trevor-commits](https://github.com/trevor-commits), and [@mjreddy](https://github.com/mjreddy). The project is maintainer-led (roadmap on [Milestones](https://github.com/bakissation/mcp-google-multi/milestones); bug reports welcome, feature PRs by prior agreement โ€” see [CONTRIBUTING.md](./CONTRIBUTING.md)). **v5 is complete and in a feedback period: [open an issue](https://github.com/bakissation/mcp-google-multi/issues/new/choose) with bugs, pain points, or what you wish it did โ€” it directly shapes the v6 roadmap.** Security reports go to [SECURITY.md](./SECURITY.md), never a public issue.

## License

[MIT](./LICENSE)

TDQS

A4.4/5.0

Scored across 13 tools

Disambiguation5/5

Each visible tool has a clearly distinct purpose: one discover tool per Google service, plus generic API search/call and account list. There is no overlap or ambiguity among the 13 top-level tools.

Naming Consistency5/5

All tool names follow a consistent object_verb pattern using lowercase and underscores: gmail_discover, drive_discover, google_api_search, google_api_call, account_list. The naming convention is uniform and predictable.

Tool Count5/5

13 tools is well within the optimal range for a multi-service server. Each discover tool serves a distinct Google API, and the generic search/call tools provide a compact escape hatch, so every tool earns its place.

Completeness5/5

The discover tools expose comprehensive operation lists for major Workspace services, and google_api_search/google_api_call cover any REST method across a wider API set. Account management is also included, making the surface effectively complete with no dead ends.

Maintenance

ActivityActive
ResponsivenessResponsive