Engagelab Email MCP server
io.github.R1ghtHereWaiting/engagelab-email·v0.1.2Send, receive, monitor and reply to email from AI agents with threaded inbox context.
0 stars40 downloads/wk
Reviews
Write oneNobody has reviewed Engagelab Email yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Engagelab Email tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 38 days ago12/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
How Engagelab Email compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 68/100
- higher than 35% of 916 Email servers
- Downloads a week
- 40
- more than 24% of 235 Email servers with a package
Install Engagelab Email in Claude Code, Cursor or VS Code
Runs npx -y @engagelabemail/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add engagelab-email -- npx -y @engagelabemail/mcp
What the publisher says
From the Engagelab Email repository's README, as published. We do not edit it. Read it on GitHub
EngageLab Agent Email MCP Server
English | 简体中文
Official EngageLab Email project.
This repository distributes a local stdio MCP server. It does not provide a hosted OAuth or HTTP MCP endpoint; run it locally with the installation command below.
Send, receive, and reply to email from AI agents — through the Model Context Protocol.
Each agent gets its own mailbox: a real address that sends and receives, with conversations grouped into threads so your agent has context. Works with Claude Desktop, Claude Code, Cursor, Cowork, and any MCP-compatible client.
{
"mcpServers": {
"engagelab-email": {
"command": "npx",
"args": ["-y", "@engagelabemail/mcp"],
"env": { "ENGAGELAB_EMAIL_SECRET_KEY": "sk_sg_your_key" }
}
}
}Why
Most email APIs are send-only. Agents that need to have a conversation over email — support, scheduling, approvals — need an inbox.
- Send & receive — the agent owns a dedicated mailbox, not a bolted-on parse webhook
- Thread-aware — replies group into conversations, so the agent sees full history
- Sandbox mode — test agent flows without emailing real humans
- One env var — no OAuth dance for local use; region inferred from the key
Tools
Quickstart
Smithery / MCPB
For local stdio distribution, build an MCPB bundle:
npm run build:mcpbThe bundle is generated at dist/engagelab-agent-email.mcpb and can be uploaded through Smithery publishing.
Official MCP Registry
EngageLab Agent Email is also listed in the official MCP Registry. Clients that consume the Registry can find it by the server name io.github.Metaverse-Cloud/engagelab-email; the underlying npm package remains @engagelabemail/mcp.
1. Get a Secret Key. Create an EngageLab account and generate a key from the console (format sksgxxx — the prefix selects the region). Or use the CLI: engagelab-email-cli login creates one via browser.
2. Create a mailbox. In the console, create a mailbox for your agent (shared subdomain is instant; custom domains need DNS verification). Programmatic mailbox creation is on the roadmap — see Troubleshooting if list_mailboxes returns empty.
3. Register the server.
Claude Desktop — add the JSON block above to claudedesktopconfig.json.
Claude Code:
claude mcp add engagelab-email \
-e ENGAGELAB_EMAIL_SECRET_KEY=sk_sg_your_key \
-- npx -y @engagelabemail/mcpThen ask your agent:
List my mailboxes, then send an email from the first one to bob@example.com saying the invoice is approved.
A typical agent loop for a support bot:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-29downgradeB → Cscore 68: eval / new Function used
Engagelab Email: common questions
- Is Engagelab Email MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the Engagelab Email safety report
- How do I install Engagelab Email?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Engagelab Email need an API key?
- Yes. The registry entry asks for
ENGAGELAB_EMAIL_SECRET_KEY. - Is Engagelab Email maintained?
- The last commit was 46 days ago (2026-09-21). The latest release is v0.1.2.
- What can I use instead of Engagelab Email?
- Servers from other publishers that do the same job: Imap MCP server, Agenticmail MCP server and send0 MCP server.
- How does Engagelab Email compare with other Email MCP servers?
- safety score 68/100 (higher than 35% of 916 Email servers); downloads a week 40 (more than 24% of 235 Email servers with a package). Full comparison.
Alternatives to Engagelab Email
Same job from other publishers: the closest match first, then the best rated.
- ImapIMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistantsnot reviewedEstablishedA
- AgenticmailReal email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.not reviewedEstablishedB
- send0Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.not reviewedGrowingA
SentfromEmail for AI agents: inboxes, send/reply/forward, search, threads, webhooks — 21 SentFromAI tools.not reviewedGrowingA- Tmailor temporary emailReceive-only temporary email addresses for AI agents: create an inbox, wait for an email, read it.not reviewedGrowingB