Purelymail MCP

Manage your Purelymail account from any MCP client

Features • Getting started • Configuration • Tools • Security • Development

An MCP server that gives AI assistants access to the Purelymail API. Ask for what you need in plain language, and let your assistant handle mailboxes, domains and routing for you:

Which of my domains are failing DNS checks?

Create sales@example.com and forward hello@example.com to it.

How much account credit do I have left?

Features

• Full API coverage: all 19 operations, across users, password reset methods, app passwords, routing rules, domains and billing.

• Read-only mode: expose only the 7 tools that cannot change anything.

• Safety annotations: tools are marked as read-only or destructive, so clients can ask for confirmation.

• Reliable error reporting: failures are detected from the response body, because the API reports them with HTTP 200.

• Nothing to install: MCP clients run the package through npx.

Related MCP server: nice

Getting started

You need Node.js 20 or later and an API token from your Purelymail account settings.

Claude Code

claude mcp add purelymail \
  -e PURELYMAIL_API_TOKEN=your-token \
  -- npx -y @amplia-labs/purelymail-mcp

Other MCP clients

Add the server to your client's MCP configuration:

{
  "mcpServers": {
    "purelymail": {
      "command": "npx",
      "args": ["-y", "@amplia-labs/purelymail-mcp"],
      "env": { "PURELYMAIL_API_TOKEN": "your-token" }
    }
  }
}

Configuration

Tools

Tools that can lock someone out of an account, such as modify_user, are also marked as destructive.

API notes

• list_password_reset_methods returns the methods under a key named users. That name comes from the API.

• delete_password_reset_method requires target, even though the API spec marks it as optional, because the spec does not say what happens without it.

• delete_app_password needs the full password, because the API cannot list app passwords.

• Requests are never retried automatically. After a timeout, check the current state before repeating a write.

Security

Development

git clone https://github.com/amplia-labs/purelymail-mcp.git
cd purelymail-mcp
npm install
npm run build

To try a local build, use node /path/to/purelymail-mcp/dist/index.js as the command in your MCP client. Development tools require Node.js 20.19 or later.

Tests use a fake HTTP server and never call the real API.

Releasing

Releases are automated with Changesets:

1. Add a changeset to any pull request that changes the package.

2. After it merges, the publish workflow opens a Version Packages pull request.

3. Merging that pull request runs all checks and publishes to npm through trusted publishing, so no npm token is stored in the repository.