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/cunicopia-dev/gmail-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/cunicopia-dev/gmail-mcp/multi-account-gmail-mcp)<a href="https://agentmods.dev/mcp/cunicopia-dev/gmail-mcp/multi-account-gmail-mcp"><img src="https://agentmods.dev/badge/mcp/cunicopia-dev/gmail-mcp/multi-account-gmail-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cunicopia-dev/gmail-mcp/multi-account-gmail-mcp"><img src="https://agentmods.dev/badge/mcp/cunicopia-dev/gmail-mcp/multi-account-gmail-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
multi-account-gmail-mcp 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 1mo 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
{
"multi-account-gmail-mcp": {
"command": "uvx",
"args": [
"multi-account-gmail-mcp"
],
"env": {
"GMAIL_MCP_CLIENT_SECRET": "",
"GMAIL_MCP_DB": "",
"GMAIL_MCP_OAUTH_PORT": ""
}
}
}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.
- 1mo ago First seen · 13 lines scan A 7bf1f3800a66
multi-account-gmail-mcp is an MCP server published in the GitHub repository cunicopia-dev/gmail-mcp (5 stars, last pushed 1mo 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-31.
Other mcp servers, from other repositories
multi-gmail-mcp
Manage multiple Gmail accounts in Claude Desktop — search, send, reply, draft, and organize. Runs locally from the multi-gmail-mcp npm package. Needs 2 environment variables to run.
mailwarden
Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze. Runs locally from the mailwarden npm package. Needs 4 environment variables to run.
gmail-mcp-local
MCP server "gmail-mcp-local" as configured in alexpekach/gmail-mcp-local. Runs locally from the @alepek/gmail-mcp-local npm package.
calendar-mcp
MCP server "calendar-mcp" as configured in deciduus/calendar-mcp. Runs locally from the calendar-mcp-server Python package. Needs 3 environment variables to run.
google-accounts-mcp
Multi-account Google MCP server: Gmail, Calendar, Drive, Tasks, and Contacts. Runs locally from the google-accounts-mcp Python package.
personal-gmail-mcp
Model Context Protocol server for a personal Gmail (consumer Google account) inbox and calendar, via the Gmail and Google Calendar APIs. Stdio transport, loopback OAuth, OS-keyring token cache. Runs locally from the @jaingxyz/personal-gmail-mcp npm package.