Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Minimal MCP server for downloading Gmail attachments to disk. Read-only OAuth by default.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GMAIL_MCP_CREDENTIALS, GMAIL_MCP_TOKEN, GMAIL_MCP_DEFAULT_DEST_DIR, GMAIL_MCP_SCOPESValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gmail-attachments": {
"command": "uvx",
"args": [
"gmail-attachments-mcp",
"serve"
],
"env": {
"GMAIL_MCP_CREDENTIALS": "your-value",
"GMAIL_MCP_TOKEN": "your-value",
"GMAIL_MCP_DEFAULT_DEST_DIR": "your-value",
"GMAIL_MCP_SCOPES": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gmail-attachments --env GMAIL_MCP_CREDENTIALS=your-value --env GMAIL_MCP_TOKEN=your-value --env GMAIL_MCP_DEFAULT_DEST_DIR=your-value --env GMAIL_MCP_SCOPES=your-value -- uvx gmail-attachments-mcp serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gmail-attachments": {
"command": "uvx",
"args": [
"gmail-attachments-mcp",
"serve"
],
"env": {
"GMAIL_MCP_CREDENTIALS": "your-value",
"GMAIL_MCP_TOKEN": "your-value",
"GMAIL_MCP_DEFAULT_DEST_DIR": "your-value",
"GMAIL_MCP_SCOPES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gmail-attachments": {
"type": "stdio",
"command": "uvx",
"args": [
"gmail-attachments-mcp",
"serve"
],
"env": {
"GMAIL_MCP_CREDENTIALS": "your-value",
"GMAIL_MCP_TOKEN": "your-value",
"GMAIL_MCP_DEFAULT_DEST_DIR": "your-value",
"GMAIL_MCP_SCOPES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GMAIL_MCP_CREDENTIALS envGMAIL_MCP_DEFAULT_DEST_DIR envGMAIL_MCP_SCOPES envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account zayansalman, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GMAIL_MCP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A focused Model Context Protocol server (and standalone CLI) for downloading Gmail attachments to disk. Three tools, read-only OAuth scope, no extra surface area.
Built because the hosted claude.ai Gmail connector in Claude Desktop returns attachment IDs and metadata only — not the actual bytes. This server fills that gap for any MCP client (Claude Code, Claude Desktop, Cursor, Cline, etc.), and also works as a plain CLI for cron jobs and shell scripts.
If you used @GongRzhe/Gmail-MCP-Server (1.1k★, archived 2026-03-03) for its attachment-download workflow, this is a minimal successor focused on that single capability.
gmail_search, gmail_download_thread_attachments, gmail_download_latest_matching. That's the whole API.gmail.readonly) — can't send, delete, or modify mail.GMAIL_MCP_CREDENTIALS, GMAIL_MCP_TOKEN, GMAIL_MCP_DEFAULT_DEST_DIR.pip install gmail-attachments-mcp
uv tool install gmail-attachments-mcp
You need a Google Cloud OAuth client. The server runs entirely on your machine; nothing leaves it.
gmail-attachments-mcp setup --import-credentials ~/Downloads/client_secret_*.json
A browser window opens for OAuth consent. After consent, a refresh token is cached at ~/.config/gmail-attachments-mcp/token.json (or $XDG_CONFIG_HOME/gmail-attachments-mcp/).
Verify:
gmail-attachments-mcp status
gmail-attachments-mcp search "has:attachment newer_than:7d" --max 3
See docs/setup-google-oauth.md for screenshots and troubleshooting.
claude mcp add --scope user gmail-attachments gmail-attachments-mcp -- serve
Then in any Claude Code session:
Use the gmail-attachments MCP to download the latest CV from
careers@example.comto~/CVs.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%/Claude/claude_desktop_config.json (Windows):
{
"mcpServers": { "gmail-attachments": { "command": "gmail-attachments-mcp", "args": ["serve"] } } }
Restart Claude Desktop. See docs/claude-desktop.md for details.
Any MCP client that supports stdio servers. Point it at the same gmail-attachments-mcp serve command. See docs/other-clients.md.
# Search
gmail-attachments-mcp search "from:noreply@stripe.com has:attachment newer_than:30d"
gmail-attachments-mcp thread 19db831fab15b507 --dest ~/Invoices
gmail-attachments-mcp latest "from:hr@example.com has:attachment" --dest ~/CVs --ext .pdf,.docx
Cron example — pull CV attachments hourly:
0 * * * * /usr/local/bin/gmail-attachments-mcp latest "to:careers@example.com has:attachment newer_than:2d" --dest ~/CVs --ext .pdf,.docx >> ~/.cache/gmail-attachments-mcp.log 2>&1
gmail_search(query, max_results=10)Returns thread summaries with attachment filenames. Use Gmail's standard query syntax.
[
{ "thread_id": "19db831fab15b507", "subject": "Folon Q3 2026 Quarterly Product Recap", "sender": "Manon Muhtasin Rahman ", "date": "Thu, 23 Apr 2026 08:35:00 +0600", "snippet": "Hi everyone, Attached is...", "message_count": 1, "attachment_count": 1, "attachment_filenames": ["Folon Quarterly Report Q3 2026.pdf"] } ]
gmail_download_thread_attachments(thread_id, dest_dir?, extensions?)Downloads every attachment in a thread to disk. Returns path, size_bytes, mime_type, original_filename per file.
gmail_download_latest_matching(query, dest_dir?, extensions?)Convenience: search + download from the single most recent match, in one call.
All paths can be overridden via environment variables.
| Variable | Default | What |
|---|---|---|
GMAIL_MCP_CREDENTIALS | ~/.config/gmail-attachments-mcp/credentials.json | OAuth client secret JSON |
GMAIL_MCP_TOKEN | ~/.config/gmail-attachments-mcp/token.json | Cached refresh token |
GMAIL_MCP_DEFAULT_DEST_DIR | ~/Downloads | Default download destination |
GMAIL_MCP_SCOPES | https://www.googleapis.com/auth/gmail.readonly | OAuth scopes (comma-separated) |
XDG_CONFIG_HOME | ~/.config | Standard XDG override |
~/.config/gmail-attachments-mcp/token.json with mode 0600. Anyone with shell access to your account can read your Gmail. Treat the file like a password.gmail.readonly. Cannot send, delete, or modify mail. If you change $GMAIL_MCP_SCOPES, you're on the hook for the consequences..gitignore blocks the common filenames.`No valid Gmail token` when invoked from Claude Desktop / cron The first OAuth flow requires a browser. Run gmail-attachments-mcp setup once in a terminal where a browser can open. Subsequent runs use the cached refresh token.
`Token has been expired or revoked` Refresh tokens stay valid as long as you use them at least every 6 months and don't revoke them at myaccount.google.com/permissions. Re-auth:
gmail-attachments-mcp setup --reauth
`Access blocked: This app's request is invalid` On personal Gmail, your OAuth consent screen needs your address listed under Test users. Workspace users should select Internal audience to avoid this.
`HttpError 403: Request had insufficient authentication scopes` You changed $GMAIL_MCP_SCOPES without re-authorizing. Run gmail-attachments-mcp setup --reauth.
| Server | Scope | Tools | Maintenance |
|---|---|---|---|
Anthropic hosted claude.ai Gmail | Read/write, hosted | many | Active, but no attachment bytes |
| GongRzhe/Gmail-MCP-Server | Full mailbox | 19 | Archived 2026-03-03 |
| shinzo-labs/gmail-mcp | Full mailbox | ~30 | Active |
| gmail-attachments-mcp (this) | read-only | 3 | Active |
Pick this one if you want a tiny, focused, read-only tool. Pick a fuller one if you also need to send mail, manage labels, drafts, threads, etc.
There are no API keys and no shipped secrets. The server authenticates to *your* Google account with an OAuth client *you* create, and caches a refresh token locally. The author has zero access to your data.
gmail.readonly) can't be redistributed in a shared app, and an unverified shared app is capped at 100 users. "Bring your own OAuth client" is the standard pattern for personal-data MCP servers.~/.config/gmail-attachments-mcp/token.json (mode 0600). Delete it to revoke locally; revoke fully at myaccount.google.com/permissions.Part of a small family of focused, local MCP servers for Google Workspace data the hosted connectors don't expose:
They can share one OAuth login or stay isolated — see each repo's setup.
MIT. See LICENSE.
Issues and PRs welcome. Run pytest and ruff check src tests before submitting.
git clone https://github.com/zayansalman/gmail-attachments-mcp
cd gmail-attachments-mcp pip install -e ".[dev]" pytest