MCP server for Gmail — read, triage, draft, and send across multiple accounts
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"gmail-mcp-ldraney","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
[](https://pypi.org/project/gmail-mcp-ldraney/) [](https://opensource.org/licenses/MIT) [](https://www.python.org/downloads/) # gmail-mcp MCP server for Gmail, built on [gmail-sdk](https://github.com/ldraney/gmail-sdk). Gives Claude Code (or any MCP client) full access to read, send, triage, draft, and manage email across multiple Gmail accounts through a single server instance. ## Install ```bash pip install gmail-mcp-ldraney ``` ## Run ```bash gmail-mcp-ldraney # or python -m gmail_mcp ``` ## Claude Code config Add to your `.mcp.json`: ```json { "mcpServers": { "gmail": { "command": "uvx", "args": ["gmail-mcp-ldraney"], "env": { "SECRETS_DIR": "~/secrets/google-oauth" } } } } ``` Or register via CLI: ```bash claude mcp add gmail -- uvx gmail-mcp-ldraney ``` ## Prerequisites Google OAuth credentials must be set up at `~/secrets/google-oauth/` (or the path in `SECRETS_DIR`): - `credentials.json` -- OAuth client credentials (Desktop type) - `gmail-{alias}.json` -- per-account token files (created automatically on first auth) On first use the server opens your browser for Google sign-in. After that, tokens refresh automatically. See the [Gmail API Setup Guide](docs/gmail-api-setup.md) for full details including scopes, multi-account configuration, and security. ## Multi-account support A single server instance handles multiple Gmail accounts. Every tool accepts an optional `account` parameter (alias or full email). If only one account is configured, it is selected automatically. Token files are stored per-account: `gmail-draneylucas.json`, `gmail-lucastoddraney.json`, etc. ## Available tools ### Messages - `gmail_get_profile` -- Get authenticated user's Gmail profile - `gmail_messages_list` -- List messages matching…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.