Docs

MCP server

Irisend's REST API is also exposed as a remote MCP server at /mcp, so a coding agent can send mail, check on it, and diagnose a bounce without glue code.

Connect

The fastest way in is the dashboard: open /mcp, choose a client, pick exactly which permissions to grant from the scope catalogue below (or a preset — send-only, read-only, or full setup), and get a one-time connection key plus ready-to-paste config.

Under the hood it authenticates the same way as the REST API — a Bearer token — but a connection key made this way carries its own explicit scopes (emails:send, domains:write, audiences:read, and so on) instead of the REST API's coarse full_access/sending_access split, and only ever works at /mcp — it is rejected everywhere else on the REST API. A regular full_access key still works here too (every scope); a sending_access key maps to just emails:send.

Claude CodecURL
claude mcp add --transport http irisend https://api.irisend.com/mcp \
  --header "Authorization: Bearer ir_xxxx"

Any other MCP client that supports Streamable HTTP takes the same URL and header in its own config format:

Generic MCP client configJSON
{
  "mcpServers": {
    "irisend": {
      "type": "http",
      "url": "https://api.irisend.com/mcp",
      "headers": { "Authorization": "Bearer ir_xxxx" }
    }
  }
}

Tools

Every tool is team-scoped and runs through the exact same guardrails (quota, domain verification, suppression checks) as the matching REST endpoint — a tool call can never bypass them. A failed call comes back as a tool error carrying the same name/message pair as the REST API's own errors (see Errors). explain_bounce's successful result is plain human-readable prose, not JSON — every other tool returns a JSON-stringified object.

ToolWhat it does
send_emailSend an email. Goes through the same validation, quota, domain-verification, and suppression handling as POST /emails. Requires the emails:send scope.
list_emailsList this team's emails, newest first. Requires emails:read.
get_emailRetrieve one email by id, including its full event timeline. Requires emails:read.
explain_bounceTranslate an email's bounce, complaint, failure, or suppression event into a plain-language explanation and a fix. Requires emails:read.
list_domainsList this team's sending domains. Requires domains:read.
get_domainRetrieve one domain by id or name — status, DNS records, reputation. Requires domains:read.
check_domain_health0-100 health score for a domain from bounce/complaint reputation and a live DNS check. Requires domains:read.
create_domainRegister a sending domain and get back the DNS records to publish. Requires domains:write.
verify_domainCheck a domain's DNS now and (re)start automatic verification. Requires domains:write.
list_received_emailsList inbound email this team has received. Requires inbound:read.
get_received_emailRetrieve one received email with attachments. Requires inbound:read.
list_audiencesList this team's contact audiences. Requires audiences:read.
create_audienceCreate a new, empty audience. Requires audiences:write.
list_contactsList every contact in one audience. Requires audiences:read.
add_contactAdd or update a contact in an audience. Requires audiences:write.
list_templatesList this team's email templates. Requires templates:read.
get_templateRetrieve one template's current content. Requires templates:read.
list_suppressionsList addresses this team can never send to. Requires suppressions:read.
add_suppressionBlock an address from receiving further email. Requires suppressions:write.