Gmail Tidy MCP

Name: Gmail Tidy MCP
Author: imkath

by imkathversion 0.5.1i★ –iRuns on your computer

Registry nameio.github.imkath/gmail-tidy-mcp

Install

Overview

Description from the maker (original English)

Organize Gmail accounts: threads, attachments, labels, filters, drafts. Never sends or deletes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 255/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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-tidy": {
      "command": "npx",
      "args": [
        "-y",
        "gmail-tidy-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add gmail-tidy -- npx -y gmail-tidy-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gmail-tidy": {
      "command": "npx",
      "args": [
        "-y",
        "gmail-tidy-mcp"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gmail-tidy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gmail-tidy-mcp"
      ]
    }
  }
}

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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account imkath, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

More stars than 0% of the other 1855 servers in this category
Published to the registry more recently than 92% of the other 1855 servers in this category
Basic checks equal to or better than 100% of the other 1855 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Gmail Tidy MCP safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.1) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

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

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

by Vexa-aiWidely used★ 2.9KUpdated 2 months ago

Runs in the cloud✓ vexa.ai

Install

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostGrowing↓ 5.3K/wk★ 1.4KUpdated 32 days ago

Computer or cloud✓ emailmd.dev

Install

MCP WhatsApp Cloud

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

by codesparEarly↓ 63/wk★ 277Updated 5 months ago

Runs on your computer

Install

README from the maker

Open the README

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.

gmail-tidy-mcp

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.
Your own OAuth client. No shared client and no third-party server. Your mail goes from Google to your machine and nowhere else.
Email content is fenced off as untrusted. Everything read from Gmail goes inside a block whose markers carry a random value per call, so an email can't close the block early. Control characters in headers are removed, and HTML is reduced to visible text (scripts, styles, and text hidden with display:none, visibility:hidden, font-size:0 or opacity:0 are dropped).
Invisible text is removed. Unicode tag characters (used to smuggle instructions that a model reads but you can't see), zero-width characters and text-direction controls are stripped from headers, bodies and attachments. Tag characters are reported, since they have no legitimate use in mail.
Security notes come from the server, not the sender. get_email and get_attachment add a short list of findings above the untrusted block: phrasing typical of prompt injection, failed SPF, DKIM or DMARC, a Reply-To that sends answers to a free webmail address when the sender didn't pass DMARC, a display name that pretends to be another address, and links that show one site but lead to another (Gmail and Outlook redirect wrappers are unwrapped first; tracking links in mailing lists are not flagged). They are tuned to stay quiet on normal mail, so a note means something.
Lookalike senders are flagged. A sender whose domain is one or two letters away from one of your connected accounts (or uses letters from other scripts that look Latin) gets a note; for Gmail and other webmail the mailbox name is compared instead. Mail between your own accounts is never flagged.
Drafts only attach files from your user folders. Attachments must live under Downloads, Desktop or Documents (or the folders in GMAIL_TIDY_ATTACH_DIRS), never in a hidden folder and never this server's own config. Links are resolved before the check, so a shortcut can't point at ~/.ssh. That way a model steered by a malicious email can't slip a private key or token into a draft for you to send.
Every change is logged locally. Labels, archiving, filters, drafts, signature changes and saved files are appended to ~/.config/gmail-tidy-mcp/audit.log (mode 600), without message bodies, draft text or the signature itself. recent_changes shows them, so if something odd happened in a session you can see exactly what and undo it.
Dangerous attachments are not saved. Executables and scripts, disguised names (factura.pdf.exe, right-to-left override tricks), files whose bytes don't match their extension, and archives that contain any of those are refused unless the call says allow_risky: true. Password-protected archives, macro-enabled Office files and PDFs with JavaScript or auto-run actions are flagged. Saved files never overwrite anything, can't be written outside the downloads folder, and on macOS get the quarantine flag so Gatekeeper checks them before they open.
Drafts can't smuggle headers. Line breaks in To, Cc, Subject or the reply headers are rejected, so nobody can sneak in a hidden Bcc.
Arguments are validated before anything reaches Gmail, and the tools that change things carry MCP annotations (destructiveHint) so clients can ask you before running them.
Big scans respect Gmail's quota. sender_stats, newsletters and searches fetch a few messages at a time and back off when Gmail asks, so a large mailbox slows the scan down instead of breaking it.
Two runtime dependencies (@modelcontextprotocol/sdk and googleapis), pinned to exact versions, none with install scripts.

What could still go wrong

No server can make prompt injection impossible, and the security notes are heuristics: they catch common tricks, not every one, and a clean result proves nothing. If a malicious email convinces the model, it could still:

relabel or archive mail (you can undo this),
create a filter that hides new mail from the inbox (only with skip_inbox: true, and your client can ask you first),
delete one of your filters (filters can't be recovered),
write a misleading draft. It is never sent unless you send it,
rename or recolor a label, change your signature, or rewrite one of your drafts (all reversible: the audit log keeps what changed),
save an attachment flagged as dangerous, if it also sets allow_risky: true; opening it is still up to you.

Two more things worth knowing:

The token itself can send mail. The "never send" guarantee is in this code, not in the token. If someone steals the token and the key, they get what gmail.modify allows. Keep your machine and keyring locked.
On macOS, the Keychain item trusts `/usr/bin/security`, which means any process running as you can read the key without a prompt. That still keeps the key off the disk, but it is not a barrier against malware running under your user.

Setup

Requires Node.js 22 or newer.

1. Create your Google OAuth client (once)

In Google Cloud Console, create a project and enable the Gmail API.
In Google Auth Platform, set up the app as External, add your email as the support and contact address, and publish it (Audience → Publish app). Unverified apps in production keep their refresh tokens. In testing mode they expire after 7 days.
Under Clients, create a client of type Desktop app and download the JSON.
Save it as ~/.config/gmail-tidy-mcp/oauth-client.json and make it private (chmod 600 on macOS and Linux).

When you connect an account, Google warns that the app is unverified. That is expected: the app is yours. Continue through Advanced.

2. Register it with your MCP client

Claude Code:

claude mcp add -s user gmail-tidy -- npx -y gmail-tidy-mcp

Any other MCP client: run npx -y gmail-tidy-mcp over stdio.

Prefer to run it from source? Clone the repo, run npm ci --ignore-scripts, and point your client at node /path/to/gmail-tidy-mcp/bin/gmail-tidy-mcp.js.

On Linux, install libsecret-tools first so the key can go into your keyring.

3. Connect accounts

Ask your assistant to connect an account. It opens Google's sign-in page in your browser. Or do it from the terminal:

npx gmail-tidy-mcp add you@gmail.com personal

npx gmail-tidy-mcp list npx gmail-tidy-mcp remove you@gmail.com

Removing an account deletes its token locally. To revoke access on Google's side too, go to myaccount.google.com/permissions.

Google Workspace accounts may need an admin to allow unverified apps.

Development

npm test

The tests cover the safety guarantee (no send or delete calls, no Trash or Spam, filter actions limited to labels), token encryption and key handling, the sign-in callback (state, errors, timeouts), the post-login checks, draft headers and body decoding. CI runs them on Linux, macOS and Windows, including the real DPAPI path on Windows.

Credits

This started from gx-55/multi-gmail-mcp (MIT) by Rogers Xie. Some of its building blocks remain: the label-or-address account lookup, the message search and header helpers, the reply threading and the token-error detection. The storage, sign-in flow, tool set and safety model were redesigned.

License

MIT. See LICENSE.

Gmail Tidy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

gmail-tidy-mcp

Why

What it can do

What it will not do

Security

What could still go wrong

Setup

1. Create your Google OAuth client (once)

2. Register it with your MCP client

3. Connect accounts

Development

Credits

License