API and MCP

MCP server and REST API

EmailPal exposes the same platform over a REST API and an MCP server (npx -y @emailpal/mcp). How to get a key, what the tools cover, and how read-only mode works.

What you can automate

Everything you can do in the dashboard has a programmatic path:

  • Domains and DNS
  • Mailboxes, including pre-warmed inventory
  • Warming
  • Unified inbox send/read
  • List verification
  • Webhooks and jobs

Base URL: https://www.emailpal.io/api/public/v1. Human reference: API documentation.

The MCP server wraps those operations as tools for Claude, Cursor, Claude Code, or any MCP client. One command:

npx -y @emailpal/mcp

with EMAILPAL_API_KEY set.

How to get an API key

  1. Sign in → API keys.
  2. Create a key. Copy it once; we store a hash, not the secret.
  3. Send it as a bearer token on REST, or as EMAILPAL_API_KEY for MCP.

Step-by-step: Create an API key. Client paste configs: Connect the MCP server.

Read-only MCP

Set EMAILPAL_MCP_READ_ONLY=true and every mutating tool disappears from the list. Use this when an agent should inspect warming or DNS but must not buy domains or claim pre-warmed inventory.

Rate limits

Each plan has an hourly API request budget (see the account payload and the docs). Jobs (provisioning, claims, DNS) are asynchronous — create, then poll /jobs.

FAQs

Is MCP a different product?

No. Same auth, same data, same prices. MCP is how an assistant calls the API without you writing glue.

Can I use this with Smartlead or Instantly?

REST/SMTP is how those tools send. MCP is for agents operating EmailPal itself (provision, warm, verify, read mail), not for driving another vendor's campaign UI.

Where is OpenAPI?

GET /api/public/v1/openapi.json and the docs site.

Need More Help?

Create an API key or open a ticket with the request id if a call returns 401/429.