Gmail MCP server for Claude CLI — API (OAuth) and SMTP/IMAP backends
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":"claude-gmail-mcp","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.
# claude-gmail-mcp [](https://pypi.org/project/claude-gmail-mcp/) A super tiny Gmail MCP server for Claude Code. Lets Claude send, search, and read Gmail on your behalf. Two backends are supported and auto-selected at startup: - **Gmail API (OAuth)** — recommended. No app password. Batch search. Direct Gmail web URLs on every result. - **SMTP/IMAP (app password)** — simpler setup. Fallback when the OAuth token isn't present. I needed something for my projects — there were a bunch around which seemed super complicated. So why not have Claude CLI build one for me :-p ## Prerequisites - [uv](https://docs.astral.sh/uv/getting-started/installation/) installed - One of: - A Google Cloud OAuth client (Desktop app) — for the API backend, OR - A Gmail [App Password](https://myaccount.google.com/apppasswords) — for the SMTP/IMAP backend ## Install (Gmail API backend — recommended) 1. In [Google Cloud Console](https://console.cloud.google.com/), create a project, enable the Gmail API, and configure the OAuth consent screen (External, add your Gmail as a test user). Create an OAuth client of type **Desktop app** and download the credentials JSON. 2. Run the auth helper, pointing at the downloaded file: ```sh uvx --from claude-gmail-mcp claude-gmail-mcp-auth /path/to/credentials.json ``` Browser opens → sign in → approve (scope: `gmail.modify`). Refresh token is saved to `~/.config/claude-gmail-mcp/token.json` (perms `600`). 3. Register the MCP server with Claude Code (no env vars needed): ```sh claude mcp add gmail --scope user -- uvx claude-gmail-mcp ``` ## Install (SMTP/IMAP backend — fallback) ```sh claude mcp add gmail --scope user \ -e GMAIL_ADDRESS=you@gmail.com \ -e GMAIL_APP_PASSWORD=your-app-password \ -- uvx claude-gmail-mcp ``` Replace `you@gmail.com` and `your-app-password` with your actual credentials. Drop `--scope user` to install only for the current project dir…
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.