API and MCP

MCP server and REST API

EmailPal exposes the send-to-close loop over a REST API and an MCP server (npx -y @emailpal/mcp): workspaces, domains, mailboxes, warming, campaigns, leads, replies and the pipeline. How to get a key, how one key works across your workspaces, what is covered, what is not, the webhook events, and how read-only mode works.

The Prospects and intent leads API (Scale plan)

On the Scale plan, the REST API can describe, preview, build and page intent audiences, save them to prospect lists, and search and reveal the Prospects table. Who can use it, the endpoints, and the fair-use limits: up to 5,000,000 audience contacts a day and per-minute and per-hour limits on searches.

Create an API key

How to create an EmailPal API key, pick its scope, why we only show it once, how to use it with REST and MCP, and how one key can work across every workspace on your bill.

Connect the MCP server

Point Claude Desktop or Cursor at npx -y @emailpal/mcp with an API key. 75 tools cover domains, mailboxes, warming, the inbox, campaigns, leads, replies and the pipeline. Read-only mode hides every mutating tool.