Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
I

imkath/gmail-tidy-mcp

Independent directory — not the official site. Details below come from the project's public repository.

Before you install: no copy-paste command · license MIT

First step: nothing runnable here yet - start from the repository: https://github.com/imkath/gmail-tidy-mcp

updated 2026-11-06
View on GitHub ↗Direct link · no redirect page

We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →

Star count
0 ★ · imkath/gmail-tidy-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository imkath/gmail-tidy-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# gmail-tidy-mcp

Excerpted from the repository README (abridged)

An MCP server that lets your AI assistant read and organize several Gmail accounts at once: search, read, label, archive, set up filters and write drafts.
It cannot send or delete email. Not "it asks first": there is no tool for it, and a test fails the build if a send or delete call ever shows up in the code.
## Why
Most Gmail MCP servers hand the model full control of your mailbox, including sending, and keep OAuth tokens in plain text on disk. That is a lot of trust to give a model that also reads emails written by strangers.
This one is built around a smaller promise: the assistant can help you get your inbox in order, but it can't send anything or delete anything.
## What it can do
| Area | Tools |
| Accounts | list_accounts, check_accounts, connect_account, finish_connect_account |
| Reading | search_emails (Gmail search syntax), search_all_accounts (one search, every account), get_email (lists attachments), get_thread (a whole conversation, oldest first, quoted history trimmed), get_attachment (text, .gz and .zip are read inline, e.g. DMARC reports; anything else, like a PDF, is saved to ~/Downloads/gmail-tidy-mcp), sender_stats (who writes most, by address and domain), newsletters (mailing lists by volume with the unsubscribe link each declares; it never unsubscribes for you) |
| Labels | list_labels, create_label (nest with Parent/Child), update_label (rename, recolor with the Gmail palette, show or hide in the sidebar) |
| Organizing | organize_emails: add or remove labels by ID or by search, up to 5,000 messages at a time. Archive = remove INBOX, mark as read = remove UNREAD |
| Filters | list_filters, create_filter, delete_filter. A filter that skips the inbox needs an explicit skip_inbox: true |
| Drafts | create_draft, optionally as a reply inside a thread and with local files attached; list_drafts; update_draft edits an existing draft (only the fields you pass change, the thread and current attachments stay). You send it yourself from Gmail |
| Settings | set_signature: changes only the signature, never how mail goes out |
| Audit | recent_changes: every change this server made, to review or undo a session |
Each account gets a short label, so you can say things like "archive every newsletter older than a month in work".
## What it will not do
Send, reply, forward or delete email, or move it to Trash or Spam.
Give the model a way to add those later: the tools are fixed in code and the model cannot call arbitrary Gmail endpoints.
Google has no scope that allows drafts but not sending, so the server asks for gmail.modify (which technically includes sending) plus gmail.settings.basic for filters. The guarantee comes from the code, and test/safety.test.js checks it on every run.
## Security
Tokens are encrypted with AES-256-GCM in ~/.config/gmail-tidy-mcp/tokens.enc (mode 600). The key lives in the macOS Keychain, the Linux Secret Service (secret-tool), or a DPAPI-protected file on Windows. You can also provide it yourself with GMAIL_TIDY_KEY (64 hex characters).
Sign-in uses PKCE and a random state, with the redirect on 127.0.0.1 only.
The signed-in account is verified. After sign-in, the server asks Gmail which address it got. If it is not the one you asked for, or Google granted different scopes, the token is revoked and nothing is saved.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/imkath-gmail-tidy-mcp/)
Source
awesome · https://github.com/imkath/gmail-tidy-mcp
Browse by field
MCP servers
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index