Google Workspace (multi-account) runs on your own machine — the client starts it, so there is no endpoint to ping. 952 installs a week from npm. Last commit 21 Oct 2026.
Multi-account Google Workspace MCP server: 942 tools, 29 services, discover-first, BYO OAuth.
What the code does
We read the source, 3 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const filePath = path.join(dir, fileName);
const child = spawn(cmd, args, { detached: true, stdio: 'ignore' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-google-multi -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<GOOGLE_CLIENT_SECRET>' -e 'GOOGLE_ACCOUNTS=<GOOGLE_ACCOUNTS>' -- npx -y mcp-google-multi{
"mcpServers": {
"mcp-google-multi": {
"command": "npx",
"args": [
"-y",
"mcp-google-multi"
],
"env": {
"GOOGLE_ACCOUNTS": "<GOOGLE_ACCOUNTS>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}[mcp_servers.mcp-google-multi]
command = "npx"
args = ["-y", "mcp-google-multi"]
env = { GOOGLE_CLIENT_ID = "<GOOGLE_CLIENT_ID>", GOOGLE_CLIENT_SECRET = "<GOOGLE_CLIENT_SECRET>", GOOGLE_ACCOUNTS = "<GOOGLE_ACCOUNTS>" }{
"mcpServers": {
"mcp-google-multi": {
"command": "npx",
"args": [
"-y",
"mcp-google-multi"
],
"env": {
"GOOGLE_ACCOUNTS": "<GOOGLE_ACCOUNTS>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}{
"servers": {
"mcp-google-multi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-google-multi"
],
"env": {
"GOOGLE_ACCOUNTS": "<GOOGLE_ACCOUNTS>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}Put your own values in place of
<GOOGLE_CLIENT_ID> (OAuth 2.0 Desktop client ID from your own Google Cloud project (docs/google-cloud-setup.md)), <GOOGLE_CLIENT_SECRET> (OAuth 2.0 Desktop client secret paired with GOOGLE_CLIENT_ID), <GOOGLE_ACCOUNTS> (Comma-separated alias:email pairs, e.g. work:[email protected],personal:[email protected]).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
MASTER_KEY (Base64 32-byte key encrypting the local token store; auto-generated and stored for you when unset).
Alternatives to Google Workspace (multi-account)
same job, measured the same wayAn MCP server for Google Workspaces.
An MCP server for Google Workspaces.
Full Google Sheets MCP: 26 tools + run_sheets_script escape hatch. User OAuth, no service account.
MCP server for Google Docs integration with OAuth2 and service account support.
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Google Ads MCP server: 35 read tools, 13 opt-in preview-first writes.
Multi-account Google Workspace MCP — Gmail, Calendar, Drive, Sheets, Docs with smart routing.
67 curated MCP tools for Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks.
Google Workspace (multi-account) — questions
Answers built from our own checks of this server.