Google Workspace runs on your own machine — the client starts it, so there is no endpoint to ping. 355 installs a week from npm. Last commit 3 Nov 2026.
Google Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more
What the code does
We read the source, 5 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 fullPath = path.join(stagingDir, filename);
const child = spawn(process.execPath, [script], {
if (isUnder(resolvedAbs, sshDir)) return { hit: true, reason: '~/.ssh/** is sensitive' };
<script src="https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js"></script>
const entries = fs.readdirSync(workspacePath, { withFileTypes: true });
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-server-google-workspace -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<GOOGLE_CLIENT_SECRET>' -e 'ACCOUNTS_PATH=<ACCOUNTS_PATH>' -e 'CREDENTIALS_PATH=<CREDENTIALS_PATH>' -- npx -y @mindstone/mcp-server-google-workspace{
"mcpServers": {
"mcp-server-google-workspace": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-google-workspace"
],
"env": {
"ACCOUNTS_PATH": "<ACCOUNTS_PATH>",
"CREDENTIALS_PATH": "<CREDENTIALS_PATH>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}[mcp_servers.mcp-server-google-workspace]
command = "npx"
args = ["-y", "@mindstone/mcp-server-google-workspace"]
env = { GOOGLE_CLIENT_ID = "<GOOGLE_CLIENT_ID>", GOOGLE_CLIENT_SECRET = "<GOOGLE_CLIENT_SECRET>", ACCOUNTS_PATH = "<ACCOUNTS_PATH>", CREDENTIALS_PATH = "<CREDENTIALS_PATH>" }{
"mcpServers": {
"mcp-server-google-workspace": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-google-workspace"
],
"env": {
"ACCOUNTS_PATH": "<ACCOUNTS_PATH>",
"CREDENTIALS_PATH": "<CREDENTIALS_PATH>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}{
"servers": {
"mcp-server-google-workspace": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-google-workspace"
],
"env": {
"ACCOUNTS_PATH": "<ACCOUNTS_PATH>",
"CREDENTIALS_PATH": "<CREDENTIALS_PATH>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}Put your own values in place of
<GOOGLE_CLIENT_ID> (Google OAuth client ID), <GOOGLE_CLIENT_SECRET> (Google OAuth client secret), <ACCOUNTS_PATH> (Path to accounts.json written by the MCP host), <CREDENTIALS_PATH> (Directory containing per-account Google OAuth token files).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GOOGLE_WORKSPACE_REQUEST_TIMEOUT_MS (Outbound Google API request timeout in milliseconds (max 300000 = 5 min)), GOOGLE_WORKSPACE_DISABLE_REFRESH (Set to 1 to disable background OAuth token refresh (tokens are only read, never refreshed)), MCP_WORKSPACE_PATH (Directory attachments and downloaded files are constrained to (defaults to a temp dir; reads/writes outside it are refused)), WORKSPACE_BASE_PATH (Legacy fallback for MCP_WORKSPACE_PATH; prefer MCP_WORKSPACE_PATH), GAUTH_FILE (Legacy fallback path to gauth.json OAuth client config; host-orchestrated setups use GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET instead).
Alternatives to Google Workspace
same job, measured the same wayGoogle Workspace MCP server for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Chat.
MCP server for Google Workspace — Sheets, Drive, Docs (HTML or Markdown), Calendar, and Gmail.
67 curated MCP tools for Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks.
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms
MCP fork of Google Workspace CLI (Gmail, Drive, Calendar, and more)
Search and work in Gmail, Calendar, Drive, Docs, Sheets and Slides across several Google accounts.
Gmail, Calendar, Drive, Sheets, Tasks and Contacts for agents, with your own Google login
Secure access to Google Drive, Docs, Sheets, Slides, and Calendar through MCP.
Google Workspace — questions
Answers built from our own checks of this server.