Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers
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.
EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD, EMAIL_IMAP_PROVIDER, EMAIL_IMAP_IMAP_HOST, EMAIL_IMAP_SMTP_HOST, EMAIL_IMAP_IMAP_PORT, EMAIL_IMAP_SMTP_PORT, EMAIL_IMAP_MAX_RECIPIENTS, EMAIL_IMAP_RATE_LIMIT_PER_HOUR, EMAIL_IMAP_RATE_LIMIT_WINDOW_MS, MCP_WORKSPACE_PATHValues 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": {
"email-imap": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "your-value",
"EMAIL_IMAP_PASSWORD": "your-value",
"EMAIL_IMAP_PROVIDER": "your-value",
"EMAIL_IMAP_IMAP_HOST": "your-value",
"EMAIL_IMAP_SMTP_HOST": "your-value",
"EMAIL_IMAP_IMAP_PORT": "your-value",
"EMAIL_IMAP_SMTP_PORT": "your-value",
"EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
"EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
"EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
"MCP_WORKSPACE_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add email-imap --env EMAIL_IMAP_EMAIL=your-value --env EMAIL_IMAP_PASSWORD=your-value --env EMAIL_IMAP_PROVIDER=your-value --env EMAIL_IMAP_IMAP_HOST=your-value --env EMAIL_IMAP_SMTP_HOST=your-value --env EMAIL_IMAP_IMAP_PORT=your-value --env EMAIL_IMAP_SMTP_PORT=your-value --env EMAIL_IMAP_MAX_RECIPIENTS=your-value --env EMAIL_IMAP_RATE_LIMIT_PER_HOUR=your-value --env EMAIL_IMAP_RATE_LIMIT_WINDOW_MS=your-value --env MCP_WORKSPACE_PATH=your-value -- npx -y @mindstone/mcp-server-email-imapFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"email-imap": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "your-value",
"EMAIL_IMAP_PASSWORD": "your-value",
"EMAIL_IMAP_PROVIDER": "your-value",
"EMAIL_IMAP_IMAP_HOST": "your-value",
"EMAIL_IMAP_SMTP_HOST": "your-value",
"EMAIL_IMAP_IMAP_PORT": "your-value",
"EMAIL_IMAP_SMTP_PORT": "your-value",
"EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
"EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
"EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
"MCP_WORKSPACE_PATH": "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": {
"email-imap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "your-value",
"EMAIL_IMAP_PASSWORD": "your-value",
"EMAIL_IMAP_PROVIDER": "your-value",
"EMAIL_IMAP_IMAP_HOST": "your-value",
"EMAIL_IMAP_SMTP_HOST": "your-value",
"EMAIL_IMAP_IMAP_PORT": "your-value",
"EMAIL_IMAP_SMTP_PORT": "your-value",
"EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
"EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
"EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
"MCP_WORKSPACE_PATH": "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.
EMAIL_IMAP_PROVIDER envEMAIL_IMAP_IMAP_HOST envEMAIL_IMAP_SMTP_HOST envEMAIL_IMAP_IMAP_PORT envEMAIL_IMAP_SMTP_PORT envEMAIL_IMAP_MAX_RECIPIENTS envEMAIL_IMAP_RATE_LIMIT_PER_HOUR envEMAIL_IMAP_RATE_LIMIT_WINDOW_MS envMCP_WORKSPACE_PATH 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 7, 2026
The registry name was verified with the GitHub account mindstone, 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: EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD
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.3.2) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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:★ 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.
Email IMAP/SMTP MCP server for Model Context Protocol hosts. Read, search, send, and manage emails through IMAP and SMTP — supports iCloud Mail, Gmail, Yahoo Mail, Outlook / Microsoft 365, and custom IMAP providers.
EMAIL_IMAP_PASSWORD)STATUS.jsonAfter clicking the button, your host will prompt you to fill: EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD, EMAIL_IMAP_IMAP_PORT, EMAIL_IMAP_SMTP_PORT, EMAIL_IMAP_MAX_RECIPIENTS, EMAIL_IMAP_RATE_LIMIT_PER_HOUR, EMAIL_IMAP_RATE_LIMIT_WINDOW_MS.
Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Email (IMAP/SMTP))
{
"mcpServers": { "Email (IMAP/SMTP)": { "command": "npx", "args": [ "-y", "@mindstone/mcp-server-email-imap" ], "env": { "EMAIL_IMAP_EMAIL": "", "EMAIL_IMAP_PASSWORD": "", "EMAIL_IMAP_IMAP_PORT": "993", "EMAIL_IMAP_SMTP_PORT": "587", "EMAIL_IMAP_MAX_RECIPIENTS": "25", "EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "50", "EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "3600000" } } } }
cd <path-to-repo>/connectors/email-imap
npm install npm run build
npx -y @mindstone/mcp-server-email-imap
node dist/index.js
EMAIL_IMAP_EMAIL — email addressEMAIL_IMAP_PASSWORD — app-specific passwordEMAIL_IMAP_PROVIDER — email provider (icloud, gmail, yahoo, outlook, or custom). When unset, the connector auto-detects the provider from the email's domain (e.g. @gmail.com → gmail, @icloud.com → icloud, @outlook.com → outlook, @yahoo.co.uk → yahoo). If the domain is not recognised, the connector refuses to start with a clear error — it will not silently fall back to a default provider.EMAIL_IMAP_IMAP_HOST — custom IMAP host (optional, for custom providers)EMAIL_IMAP_SMTP_HOST — custom SMTP host (optional, for custom providers)EMAIL_IMAP_IMAP_PORT — custom IMAP port (default: 993). Cleartext ports (imap_port=143, smtp_port=25) are allowed when configured — your host owns the plaintext decision.EMAIL_IMAP_SMTP_PORT — custom SMTP port (default: 587)MCP_WORKSPACE_PATH — workspace directory used for attachment file I/O. email_get_attachment downloads into a fresh, private email-imap-attachment-* staging directory created directly under this path (the returned path points there), and outbound attachments on email_send / email_save_draft / email_update_draft may only be read from inside it (paths outside — including via symlinks — are refused). Successful downloads keep their staging directory (it is the container of the returned file); accumulated email-imap-attachment-* directories are safe to delete once the files are no longer needed. Defaults to the system temp directory when unset.MCP_HOST_BRIDGE_STATE — optional path to a host bridge state file used for credential managementMINDSTONE_REBEL_BRIDGE_STATE — backwards-compatible alias for MCP_HOST_BRIDGE_STATEemail_send)These caps act as blast-radius circuit breakers against prompt-injection-driven mass sends. Defaults are baked into the source so a host that sets none of these still gets safe behaviour. Hosts can tighten them per deployment.
EMAIL_IMAP_MAX_RECIPIENTS — maximum combined To+CC+BCC recipients per email_send call (default: 25). Exceeding this returns a structured error with code: "RECIPIENT_LIMIT_EXCEEDED".EMAIL_IMAP_RATE_LIMIT_PER_HOUR — maximum number of email_send calls per rolling window (default: 50). Exceeding this returns a structured error with code: "RATE_LIMIT_EXCEEDED", plus resetAt (ISO-8601) and retryAfterMs so the host/LLM can back off.EMAIL_IMAP_RATE_LIMIT_WINDOW_MS — sliding-window length, in milliseconds, for the rate limit (default: 3600000 — one hour).{
"mcpServers": { "Email": { "command": "npx", "args": ["-y", "@mindstone/mcp-server-email-imap"], "env": { "EMAIL_IMAP_EMAIL": "you@icloud.com", "EMAIL_IMAP_PASSWORD": "your-app-specific-password", "EMAIL_IMAP_PROVIDER": "icloud" } } } }
{
"mcpServers": { "Email": { "command": "node", "args": [" /connectors/email-imap/dist/index.js"], "env": { "EMAIL_IMAP_EMAIL": "you@icloud.com", "EMAIL_IMAP_PASSWORD": "your-app-specific-password", "EMAIL_IMAP_PROVIDER": "icloud" } } } }
email_sendemail_send is a destructive, open-world action: it dispatches mail to arbitrary external recipients on the user's behalf. The tool is annotated with destructiveHint: true and openWorldHint: true accordingly.
Hosts MUST require explicit user confirmation before each `email_send` invocation. A user-confirmation gate is the only reliable defence against prompt-injection content (e.g., text inside an email_get_message body) coercing the LLM into sending mail without the user's intent. Do not auto-approve email_send based on tool annotations alone — surface the full recipient list, subject, and body to the user and require an affirmative click/keystroke before forwarding the call to the connector.
The connector additionally enforces:
EMAIL_IMAP_MAX_RECIPIENTS, default 25).EMAIL_IMAP_RATE_LIMIT_PER_HOUR / EMAIL_IMAP_RATE_LIMIT_WINDOW_MS, defaults 50 / 3600000ms).When either cap is exceeded the tool returns a structured error JSON ({ ok: false, code: "RECIPIENT_LIMIT_EXCEEDED" | "RATE_LIMIT_EXCEEDED", … }) without contacting the SMTP transport. Caps are env-tunable but defaults are baked into the source — hosts do not need to set any env var to get safe behaviour.
Every attacker-controlled text field the connector returns — message bodies, subjects, from/to display names, Message-IDs, attachment filenames, MIME content types and part identifiers, mailbox names and special-use values, message flag keywords (writable via email_set_flags, where keywords must match a conservative charset allowlist — letters, digits, _, $, ., - with an optional leading \ — so atom-specials like spaces, parens, quotes or CR/LF can never reach the IMAP command), draft summaries, and error text originating from the IMAP/SMTP server or vendor SDKs — is wrapped in an … envelope (with close-tag breakout escaping) so the host LLM treats it as data, not instructions. Tools that consume a previously returned value (mailbox, part, mailbox names, flag keywords) accept the enveloped form as-is and strip one envelope layer on input.
Beyond email_send, the tools annotated destructiveHint: true are email_save_draft, email_update_draft (replaces and expunges the old draft), email_create_mailbox, email_rename_mailbox, email_delete (permanent when no Trash mailbox exists; aborts with a TRASH_MOVE_FAILED error — leaving the messages in place — when the move to Trash fails, rather than silently escalating to a permanent expunge), email_move_messages (its fallback permanently expunges the source messages, and only after the copy to the destination is verified complete for every UID — otherwise it aborts with a MOVE_COPY_UNVERIFIED error), email_set_flags (\Deleted marks messages for permanent expunge on mailbox close), email_delete_draft (always permanent), and email_delete_mailbox (removes the folder and all messages inside it). Hosts should gate these behind the same explicit user confirmation as email_send.
configure_email_imap — Configure email account credentials and provideremail_list_mailboxes — List all email folders/mailboxes with message countsemail_get_mailbox_status — Get mailbox status with unread count and latest subjectsemail_create_mailbox — Create a new mailbox/folder (destructive)email_rename_mailbox — Rename a mailbox/folder (INBOX cannot be renamed; destructive)email_delete_mailbox — Permanently delete a mailbox/folder and its contents (destructive)email_search_messages — Search emails with sender/subject/unread filters, since/before date filters, and before_uid cursor pagination (returns at most 50 messages when limit is omitted; hasMore: true signals more results)email_get_message — Get full email content by UID (bodies, subjects, addresses, Message-ID, and attachment filenames/MIME metadata are returned inside envelopes)email_get_attachment — Download an attachment into the workspace sandbox (see MCP_WORKSPACE_PATH); writes are exclusive-create, so existing files are never overwrittenemail_move_messages — Move emails between folders (fallback expunge of the source is gated on a verifiedOnly the beginning is shown; read the rest in the repo