MepMail Docs

npm packages

The packages MepMail publishes on npm — @mepmail/mcp, @mepmail/cli and the n8n node — what each one does and how to install it.

MepMail publishes three npm packages. None is an SDK: the API speaks the Resend wire protocol, so sending mail means using the official Resend SDKs with your instance's base URL (SDKs). These cover what those SDKs cannot do — running MCP locally, moving an account over and wiring MepMail into n8n.

PackageSource versionNodeRole
@mepmail/mcp0.3.2>=2022 team tools and 6 mailbox tools, depending on the credential. Guide.
@mepmail/cli0.2.4>=18Account migration with plan, apply and report. Guide.
n8n-nodes-mepmailSee npmn8nWorkflows for Send and Mail. Guide.

The hosted MCP at this revision is 0.71.1, with 79 tools advertised in the server card. The additional list_teams tool appears only on all-teams grants. Scopes and permissions can reduce the effective list.

These values are generated from the package manifests and tool registries at the docs source revision. npm packages have their own release cycle: follow the registry links for the latest published version and check tools/list in your actual client for its available tools. A source release does not publish a new npm package automatically. The n8n package lives in a separate repository and installs from n8n (Settings → Community nodes).

@mepmail/mcp — the local MCP server

npx -y @mepmail/mcp

It speaks stdio, so your client launches it and the config block is the whole install:

claude_desktop_config.json
{
  "mcpServers": {
    "mepmail": {
      "command": "npx",
      "args": ["-y", "@mepmail/mcp"],
      "env": {
        "MEPMAIL_API_KEY": "ms_...",
        "MEPMAIL_BASE_URL": "https://api.mepmail.dev"
      }
    }
  }
}
VariableRequiredDefaultMeaning
MEPMAIL_API_KEYfor team tools—Team API key (ms_...) from API keys in the dashboard. The tools act with exactly this key's reach. May be omitted for a mailbox-only client.
MEPMAIL_BASE_URLnohttps://api.mepmail.devYour instance's API origin. Set it for a self-hosted deployment.
MEPMAIL_MAIL_TOKENfor mailbox tools—Mail agent key (mmb_... for one mailbox or mmt_... for the mailboxes selected by a team credential). Works without a team API key.
MEPMAIL_MAIL_ORIGINnohttps://mepmail.devDashboard origin serving Mail. Set it for your self-hosted mailbox service.

For a mailbox-only client, replace MEPMAIL_API_KEY in the configuration above with MEPMAIL_MAIL_TOKEN. Team tools call the API origin; mailbox tools call the dashboard origin. Both authenticate directly with their own scoped key — no browser OAuth step. Config for Claude Desktop, Cursor and VS Code, and the full hosted tool list, are on the MCP page.

@mepmail/cli — the migration CLI

npx @mepmail/cli migrate --from resend

That is the interactive path: it connects to Resend, lets you pick resources, shows the plan, asks for confirmation, applies it and prints a report. For CI, run the read-only plan first — exit code 2 means there is something to apply:

export RESEND_API_KEY=re_...
export MEPMAIL_API_KEY=ms_...

npx @mepmail/cli migrate plan --from resend --out plan.json
npx @mepmail/cli migrate apply plan.json --yes
VariableMeaning
RESEND_API_KEYSource key, full access. The tool only ever reads from Resend.
MEPMAIL_API_KEYMepMail key, full access.
MEPMAIL_BASE_URLAPI origin of a self-hosted instance. Unset means MepMail Cloud.

Keys are read from the environment (or stdin), never written to disk, and redacted from every log line. Every flag, the state files and the exit codes are on the CLI page.

License and releases

Both packages are MIT-licensed and released from the same repository as the server, with their own version line. Nothing in either one phones home: no telemetry, no update check.

On this page