Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/aaronsb/google-workspace-mcp/google-workspacegit clone --depth 1 https://github.com/aaronsb/google-workspace-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/aaronsb/google-workspace-mcp/google-workspace)<a href="https://agentmods.dev/mcp/aaronsb/google-workspace-mcp/google-workspace"><img src="https://agentmods.dev/badge/mcp/aaronsb/google-workspace-mcp/google-workspace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-workspace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"google-workspace": {
"command": "npx",
"args": [
"-y",
"@aaronsb/google-workspace-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "",
"GOOGLE_CLIENT_SECRET": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 13 lines scan A 39b461b340a4
google-workspace is an MCP server published in the GitHub repository aaronsb/google-workspace-mcp (176 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
better-workspace-mcp
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms. Runs locally from the @n24q02m/better-workspace-mcp npm package. Needs 2 environment variables to run.
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
gws-mcp-server
Google Workspace as 39 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks. Runs locally from the gws-mcp-server npm package.
multi-account-gmail-mcp
Multi-account Gmail MCP server for AI agents. Runs locally from the multi-account-gmail-mcp Python package. Needs 3 environment variables to run.
a2cr-mcp
Local MCP workspace for AI agent handoff checkpoints, WorkStash notes, and WorkThreads. Runs locally from the a2cr-mcp Python package. Needs 1 environment variable to run.