Skills/npm/gmail-workspace-mcp-server

gmail-workspace-mcp-server@0.4.12

VERIFIED· startup only

Publisher claims: "MCP server for Gmail with OAuth2 (personal) and service account (Workspace) support." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher pulsemcp · publishing for 506 daysInstalls 0Last detonated 18 h ago
$claude mcp add gmail-workspace-mcp-server -- npx -y gmail-workspace-mcp-server
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
GMAIL_OAUTH_CLIENT_IDGMAIL_OAUTH_CLIENT_SECRETGMAIL_OAUTH_REFRESH_TOKENGMAIL_SERVICE_ACCOUNT_PRIVATE_KEYConfiguration, not credentials: GMAIL_ENABLED_TOOLGROUPS, GMAIL_IMPERSONATE_EMAIL, GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL
Where it talks to
no vendor host named in the codeAlso google.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names google.com as well as its own vendor. The guard injects GMAIL_OAUTH_CLIENT_ID, GMAIL_OAUTH_CLIENT_SECRET, GMAIL_OAUTH_REFRESH_TOKEN, GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y gmail-workspace-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-13 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 28 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.6sprocessdependency install exit 0
28sclaimedstartup only: exited (0) before answering · at process.processTicksAndRejections (node:internal/process/task_queues:103:5) { code: 'ERR_MODULE_NOT_FOUND' } Node.js v22.23.5
28sprocessscript backend runs setup only
28sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagebuild/index.js:105 · npx invocation of non-well-known package — may execute untrusted codeconsole.error('\n Setup: Run `npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>`');Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebuild/index.js:67 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(' npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>');Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebuild/oauth-setup.js:75 · npx invocation of non-well-known package — may execute untrusted codeconsole.error('Usage: npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>');Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebuild/oauth-setup.d.ts:5 · npx invocation of non-well-known package — may execute untrusted code* npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebuild/oauth-setup.js:5 · npx invocation of non-well-known package — may execute untrusted code* npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
LOW
Authorization escalation languageREADME.md:33 · Authorization escalation language · informational: not an instruction fileUse this for personal `@gmail.com` accounts or any Google account without Workspace admin access.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
npx invocation of non-well-known packagebuild/oauth-setup.js:78 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(' GMAIL_OAUTH_CLIENT_ID=... GMAIL_OAUTH_CLIENT_SECRET=... npx gmail-workspace-mcp-server oauth-setup');Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈61 tok
1 file · 53 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for gmail-workspace-mcp-server@0.4.12 as of 18 h ago. This is the package itself, not its dependencies.