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.
git clone --depth 1 https://github.com/rishipradeep-think41/gsuite-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/rishipradeep-think41/gsuite-mcp/google-workspace-server)<a href="https://agentmods.dev/mcp/rishipradeep-think41/gsuite-mcp/google-workspace-server"><img src="https://agentmods.dev/badge/mcp/rishipradeep-think41/gsuite-mcp/google-workspace-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-workspace-server 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 8d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- google-workspace-server — 100% identical, 0 lines differ
- google-workspace-server — 100% identical, 0 lines differ
- google-workspace-server — 100% identical, 0 lines differ
What it actually says
{ "google-workspace-server": { "command": "npx", "args": [ "-y", "google-workspace-server" ] } }
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.
- 8d ago First seen · 9 lines scan A fdbcb2501fa4
google-workspace-server is an MCP server published in the GitHub repository rishipradeep-think41/gsuite-mcp (27 stars, last pushed 1y ago), licensed MIT. 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
google-automation-mcp
Headless Google Workspace automation for AI - Apps Script, Gmail, Drive, Sheets, Calendar, Docs, Tasks, Forms. Runs locally from the google-automation-mcp Python package.
honest-drive-mcp
Local MCP server for Google Drive with full permission management — read, write, share files with your Google account. Runs locally from the honest-drive-mcp Python package.
notion
Notion's hosted MCP server: lets the agent search, read and edit pages and databases. Remote server at mcp.notion.com.
notion
MCP server "notion" as configured in ChrisWiles/claude-code-showcase. Runs locally from the @anthropic/mcp-notion npm package. Needs 1 environment variable to run.
google-drive
Google Drive + Workspace MCP — Docs, Sheets, Slides, Shared Drives, Labels, Approvals, DWD. Runs locally from the @us-all/google-drive-mcp npm package. Needs 10 environment variables to run.
google-workspace-mcp-server
MCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Runs locally from the google-workspace-mcp-server npm package.