Skills/npm/google-docs-workspace-mcp-server

google-docs-workspace-mcp-server@0.1.4

VERIFIED· startup only

Publisher claims: "MCP server for Google Docs integration with OAuth2 and service account 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 google-docs-workspace-mcp-server -- npx -y google-docs-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
Needs
GOOGLE_DOCS_OAUTH_CLIENT_SECRET, GOOGLE_DOCS_OAUTH_REFRESH_TOKEN, GOOGLE_DOCS_SERVICE_ACCOUNT_PRIVATE_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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
GOOGLE_DOCS_OAUTH_CLIENT_IDGOOGLE_DOCS_OAUTH_CLIENT_SECRETGOOGLE_DOCS_OAUTH_REFRESH_TOKENGOOGLE_DOCS_SERVICE_ACCOUNT_PRIVATE_KEYConfiguration, not credentials: GOOGLE_DOCS_ENABLED_TOOLGROUPS, GOOGLE_DOCS_IMPERSONATE_EMAIL, GOOGLE_DOCS_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 GOOGLE_DOCS_OAUTH_CLIENT_ID, GOOGLE_DOCS_OAUTH_CLIENT_SECRET, GOOGLE_DOCS_OAUTH_REFRESH_TOKEN, GOOGLE_DOCS_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 google-docs-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 (it asks for GOOGLE_DOCS_OAUTH_CLIENT_SECRET, GOOGLE_DOCS_OAUTH_REFRESH_TOKEN, GOOGLE_DOCS_SERVICE_ACCOUNT_PRIVATE_KEY); 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 · 48 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.9sprocessdependency install exit 0
28sprocessrelaunched with a decoy GOOGLE_DOCS_OAUTH_CLIENT_SECRET, GOOGLE_DOCS_OAUTH_REFRESH_TOKEN, GOOGLE_DOCS_SERVICE_ACCOUNT_PRIVATE_KEY (tagged; nothing real)
48sclaimedstartup only: exited before answering, asking for GOOGLE_DOCS_OAUTH_CLIENT_SECRET, GOOGLE_DOCS_OAUTH_REFRESH_TOKEN, GOOGLE_DOCS_SERVICE_ACCOUNT_PRIVATE_KEY (a decoy value was refused)
48sprocessscript backend runs setup only
48sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagebuild/oauth-setup.js:70 · npx invocation of non-well-known package — may execute untrusted codeconsole.error('Usage: npx google-docs-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:61 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(' npx google-docs-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:38 · 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:73 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(' GOOGLE_DOCS_OAUTH_CLIENT_ID=... GOOGLE_DOCS_OAUTH_CLIENT_SECRET=... npx google-docs-workspace-mcp-server oauth-setup');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 google-docs-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:99 · npx invocation of non-well-known package — may execute untrusted codeconsole.error('\n Setup: Run `npx google-docs-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 google-docs-workspace-mcp-server oauth-setup <client_id> <client_secret>Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈65 tok
1 file · 57 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 google-docs-workspace-mcp-server@0.1.4 as of 18 h ago. This is the package itself, not its dependencies.