Engagelab Email

io.github.R1ghtHereWaitingPublished by GitHub account R1ghtHereWaitingv0.1.2Updated Oct 24, 2026

Send, receive, monitor and reply to email from AI agents with threaded inbox context.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that gives an AI agent its own EngageLab mailbox to send, receive, monitor and reply to email with thread context.

What you can do
List mailboxes and pick the one an agent should use, since mailbox IDs are needed first and mailboxes are created in the EngageLab console rather than by the agent. Send new email with text or HTML bodies, cc/bcc, attachments and a sandbox mode, or reply to a message so recipients and threading are inferred. Read inbound mail by listing messages with mailbox or keyword filters, fetching full details by UID, or polling once for new mail. Browse conversations through thread listing, thread details and per-thread messages, so replies stay grouped with their history.
When to use it
Useful when an agent needs a real two-way inbox rather than send-only email, for example a support bot, scheduling assistant or approval flow that must read a reply and answer in the same thread. Sandbox mode lets you test such flows without emailing real people.
Requirements
Runs locally over stdio, typically via npx with the npm package. Needs an EngageLab account and a Secret Key supplied in ENGAGELAB_EMAIL_SECRET_KEY; the key prefix selects the region. At least one mailbox must already exist in the EngageLab console. ENGAGELAB_EMAIL_BASE_URL is optional and overrides the inferred API endpoint.
Before you install
The Secret Key is a credential passed in an environment variable and grants access to the account's mailboxes; keep it out of shared configs. The server sends real email to real recipients and can read inbound mail, so review what an agent is allowed to send. Attachments are base64-encoded in tool calls, up to 10 files or 10MB per message. Mail content and attachments go to EngageLab's API.

Installation

In SourceWeft

  1. Open Engagelab Email in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

EngageLab Agent Email MCP Server

[npm] [License: MIT] [Node]

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.

json
{  "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

ToolWhat it does
Discoverlist_mailboxesList mailboxes; call this first to get IDs
Sendsend_emailNew email (text/html, cc/bcc, attachments, sandbox)
reply_emailReply to a message — recipients & thread inferred
Receivelist_inbound_messagesInbound mail, filter by mailbox/keyword
get_messageFull message details by UID
check_new_messagesOne-shot poll for new mail
Threadslist_threads / get_thread / list_thread_messagesBrowse conversations

Quickstart

Smithery / MCPB

For local stdio distribution, build an MCPB bundle:

bash
npm run build:mcpb

The 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 sk_sg_xxx — 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 claude_desktop_config.json.

Claude Code:

bash
claude mcp add engagelab-email \  -e ENGAGELAB_EMAIL_SECRET_KEY=sk_sg_your_key \  -- npx -y @engagelabemail/mcp

Then ask your agent:

List my mailboxes, then send an email from the first one to [email protected] saying the invoice is approved.

A typical agent loop for a support bot:

check_new_messages()            → [messageUids]get_message(uid)                → body, attachmentslist_thread_messages(threadId)  → full conversation contextreply_email(uid, { text: ... }) → response lands in the same thread

Configuration

Environment variableRequiredDescription
ENGAGELAB_EMAIL_SECRET_KEYYesSecret Key starting with sk_
ENGAGELAB_EMAIL_BASE_URLNoOverride the API base URL. Inferred from the key region: sg → Singapore, tr → Türkiye

Limits: up to 10 attachments / 10MB total per message (base64-encoded in the tool schema).

Troubleshooting

  • list_mailboxes returns an empty list — your account has no mailbox yet. Create one in the EngageLab console (see Quickstart step 2). Agents cannot self-provision mailboxes yet.
  • 401 / code 100101 — the Secret Key is wrong or revoked. Check ENGAGELAB_EMAIL_SECRET_KEY and that the key's region prefix (sk_sg_ / sk_tr_) matches the endpoint you use.
  • Could not determine API base URL — the key's region prefix isn't recognized. Set ENGAGELAB_EMAIL_BASE_URL explicitly.
  • Reply shows up as a new conversation — use reply_email (not send_email) so In-Reply-To headers and threading stay intact.

Roadmap

  • Hosted MCP (OAuth) for zero-config remote use
  • Programmatic mailbox creation via Secret Key
  • Webhook push (no polling) for check_new_messages
  • URL-based attachment references (no base64 in context)

Run from source

bash
git clone https://github.com/Metaverse-Cloud/engagelab-email-mcpcd engagelab-email-mcpnpm install && npm run buildENGAGELAB_EMAIL_SECRET_KEY=sk_sg_xxx node dist/index.cjs

Related

License

MIT

Source: README.md at commit 1a1b1c0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts