Vexa
de Vexa-ai
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Se ejecuta en la nube★ 2949Apache-2.0Actualizado hace 2 meses
Instalar
Gmail Tidy MCP
Resumen
Descripción del creador (original en inglés)
Organize Gmail accounts: threads, attachments, labels, filters, drafts. Never sends or deletes.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Chat y correo
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- El registro no indica ninguna clave que completar.
Necesitas
- npmNode.js instalado (para el comando npx)
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"gmail-tidy": {
"command": "npx",
"args": [
"-y",
"gmail-tidy-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add gmail-tidy -- npx -y gmail-tidy-mcpO copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"gmail-tidy": {
"command": "npx",
"args": [
"-y",
"gmail-tidy-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"gmail-tidy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gmail-tidy-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub imkath, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Chat y correoi
- Más estrellas que el 0% de los otros 1838 servidores de esta categoría
- Publicado en el registro más recientemente que el 93% de los otros 1838 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 1838 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Gmail Tidy MCP?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.5.1) llegó al registro ayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Vexa, emailmd, MCP WhatsApp Cloud
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
emailmd
de anypost
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Computadora o nube★ 1385MITActualizado hace 32 días
Instalar
MCP WhatsApp Cloud
de codespar
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Se ejecuta en tu computadora★ 277MITActualizado hace 5 meses
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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 withGMAIL_TIDY_KEY(64 hex characters). - Sign-in uses PKCE and a random `state`, with the redirect on
127.0.0.1only. - 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:0oropacity:0are 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_emailandget_attachmentadd 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_changesshows 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 saysallow_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,newslettersand 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/sdkandgoogleapis), 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.modifyallows. 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.jsonand make it private (chmod 600on 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-mcpAny 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 personalnpx 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 testThe 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.