Build an Inbox-Triage Agent over MCP

To build an inbox-triage agent, give it a real mailbox over Sairaph Mail's native MCP server, then loop: read inbound, classify each message, and act - reply, escalate, or ignore. Point any MCP-capable runtime at https://mail.sairaph.com/mcp/v1/mcp with a read_write mailbox key as a Bearer token, and the mailbox's read and send actions appear as tools. Per-mailbox suppression keeps the agent from re-emailing addresses that have bounced or unsubscribed.

Get started See pricing

Last updated June 30, 2026

This guide builds the triage loop in four steps.

Step 1 - Provision the mailbox and a read_write key

Create the triage mailbox in the dashboard and issue a read_write key - the agent needs to both read inbound and send replies. Give the key an expiry so a leaked secret ages out on its own. Issuance is dashboard-only:

Shell

# Keys are issued from the dashboard, not over REST - the issuance surface is
# deliberately not agent-callable, so a leaked key can never mint or revoke
# another. To get one: Dashboard → API keys → pick the mailbox + a role
# (read / read_write / management) + an optional expiry → copy the sm_live_…
# secret (it is shown ONCE). Then set it for your agent and pass it as the
# Bearer token on every REST + MCP call:
export SAIRAPH_MAIL_KEY="sm_live_…"

Step 2 - Register the MCP server with your runtime

Any MCP-capable agent runtime connects the same way - streamable-HTTP transport, mailbox key as the Bearer token:

YAML

# Register the MCP server with your remote agent runtime.
# Transport: streamable-HTTP. Auth: a mailbox API key.
mcp_servers:
  - name: sairaph-mail
    transport: streamable-http
    url: https://mail.sairaph.com/mcp/v1/mcp
    headers:
      Authorization: "Bearer ${SAIRAPH_MAIL_KEY}"

For an MCP-capable client generally:

Shell

# Any MCP-capable client: point it at the endpoint and pass
# a mailbox API key as a Bearer token.
ENDPOINT="https://mail.sairaph.com/mcp/v1/mcp"
AUTH="Authorization: Bearer $SAIRAPH_MAIL_KEY"
# Transport is streamable-HTTP; the mailbox's actions appear as tools.

Once connected, the mailbox's actions are tools the agent can call (sending mail, and listing/reading inbound).

Step 3 - Read inbound and classify

The triage loop starts by reading inbound. Use the cache for routine sweeps and a live, on-demand fetch when you need the freshest state. Over REST the read leg is:

cURL

# Read inbound from cache, or live=true for an on-demand fetch.
curl "https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/messages?direction=inbound&live=true" \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY"

Feed each message to the model with a tight classification instruction, for example:

Text

You triage an inbox. For each inbound message, output one label:
  REPLY      - needs a direct response (draft it)
  ESCALATE   - needs a human (summarize why)
  IGNORE     - newsletter, receipt, or noise
Then take the matching action with the mailbox tools. Never email an
address that suppression reports as bounced or unsubscribed.

Because the inbox is two-way and owned, the agent has the full thread for context - not just a single webhook payload.

Step 4 - Act, and respect suppression

For REPLY, the agent sends through the same MCP tool (or REST). Idempotency keeps a retried run from double-sending:

cURL

curl https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/outbound \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["agent@acme.dev"],
    "subject": "Your verification code",
    "body_text": "Reply with APPROVE to continue."
  }'

Per-mailbox suppression is isolated to this mailbox, so a bounce or unsubscribe on the triage inbox never affects another mailbox in your tenant - important when one tenant runs many agents.

How Sairaph Mail fits a triage agent

A triage agent is only as good as the inbox behind it. Sairaph Mail gives the agent a real, owned, two-way mailbox over a native MCP server - scoped, expiring keys, per-mailbox suppression, EU-hosted by default, and a dashboard to watch every classification and reply. See the inbox-triage use case for the product framing and the MCP email server pillar for the full tool surface.

Next step: get started with a mailbox and a read_write key, then follow the quickstart and MCP docs.

Inbox Triage Agent
Learn more.
Learn more
MCP Email Server: Give Your Agent Email as Native Tools
An in-depth guide.
Learn more
MCP
Connect over the MCP server.
Learn more
Quickstart
Zero to send + receive in minutes.
Learn more

Give your agent a real mailbox

Two-way email over REST and a native MCP server, EU-resident by default.

Get started See pricing

EU data residencyPer-customer encryptionNative MCP

Build an Inbox-Triage Agent over MCP

Step 1 - Provision the mailbox and a read_write key

Step 2 - Register the MCP server with your runtime

Step 3 - Read inbound and classify

Step 4 - Act, and respect suppression

How Sairaph Mail fits a triage agent

Related

Inbox Triage Agent

MCP Email Server: Give Your Agent Email as Native Tools

MCP

Quickstart

Give your agent a real mailbox