drive_discoverLABSCO SUMMARY
A tool for every Google Workspace API method, and almost none of them in your context at boot.
The server exposes one discover tool per service instead of listing everything, so idle context stays small and calling drive_discover is what reveals Drive's operations. Multi-account is the other half: one read call can fan out across your work and personal accounts and come back with a result per account, and one account failing does not hide the others.
What it is
A local Google Workspace MCP server covering every OAuth-reachable Workspace API method, across multiple Google accounts, through your own OAuth app.
What you get
- 872 tools across 28 services by the README's count — Gmail, Drive, Calendar, Sheets, Docs, Slides, Forms, Contacts, Tasks, Chat, Meet, Classroom, Vault and Admin — of which its docs name 14
- Multiple Google accounts by alias; read tools accept an account list, or all of them at once, returning per-account results
- Discover-first listing: a service's operations appear only after you call its discover tool, such as drive_discover
- An escape hatch for anything not covered by a named tool — google_api_search and google_api_call
- Copying or moving a file between two of your own accounts — drive_transfer
- Capped, compact responses: drive_read pages at 100k characters, gmail_read caps message bodies at 50k
- Writes deny-by-default, tokens encrypted at rest with AES-256-GCM, no telemetry and no metering
Requirements
Node.js 20 or newer, then npm install -g mcp-google-multi. You create your own free Google Cloud app for GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, name each account in GOOGLE_ACCOUNTS, and supply a MASTER_KEY that encrypts stored tokens. Sign each account in with mcp-google-multi auth --account work.
Setup effort
Follow the published steps — npm install -g mcp-google-multi
USE CASES
Working across a work and a personal Google account
Name each one with an alias and see which are signed in and healthy.
Searching every mailbox at once
Run one read call across all configured accounts and get per-account results back.
Moving a file between two accounts you own
Copy or move it server-side, with the temporary grant on the source revoked afterwards.
Reaching an API method the named tools do not cover
Find the method in Google's Discovery index and invoke it by id, under the same write policy.
14 tools
Listed in project docs. Your client may show a different list.
account_listgoogle_api_searchgoogle_api_calldrive_transferdrive_readdrive_downloaddrive_exportgmail_readgmail_read_threadgmail_download_attachmentcalendar_list_eventscalendar_list_instancescalendar_get_eventBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
- npm on PATH
- GOOGLE_CLIENT_ID in your environment
- GOOGLE_CLIENT_SECRET in your environment
- MASTER_KEY in your environment
- GOOGLE_ACCOUNTS in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Install Node.js 20 or newer, then install the server:
npm install -g mcp-google-multiCreate your (free) Google app so the server can sign in as you — follow the project's Google Cloud setup guide (https://github.com/bakissation/mcp-google-multi/blob/main/docs/google-cloud-setup.md). You come back with a Client ID and Client Secret.
Create a file named .env in the folder you'll run from, with these values:
GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>
GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>
GOOGLE_ACCOUNTS=work:<YOUR_EMAIL>,personal:<YOUR_EMAIL>
MASTER_KEY=<YOUR_MASTER_KEY>Generate the MASTER_KEY (the encryption key for stored tokens) with:
openssl rand -base64 32Sign in each account (a browser window opens; approve the permissions):
mcp-google-multi auth --account work
mcp-google-multi auth --account personalConnect it to Claude Code (any MCP client works the same way), restart your client, and check everything with mcp-google-multi config check.
MCP Clients
Claude Code — npx
claude mcp add google-multi -s user -- npx -y mcp-google-multiThe configuration on this page does not set GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, MASTER_KEY and GOOGLE_ACCOUNTS; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.