This is the recipe Inboundr was built for: an agent with its own inbox that reads incoming mail and decides what to do — all through MCP tools, no email plumbing.

​
What you’ll wire up

1

Give the agent an address

On a verified domain, create an inbox for the agent. A store-only address (no endpoint) is ideal — the agent reads when it acts, so it doesn’t need a server listening for webhooks.
Now ada@yourdomain.com accepts mail and keeps it for the agent to read.
2

Connect the MCP server

Point your MCP client at Inboundr with the same inb_ key:
The agent now has list_emails, get_email, get_thread, and more as tools. See the full tool list.
3

Run the loop

Give the agent a simple operating instruction and let the tools do the rest:
Check ada@yourdomain.com for new mail. For each new message, read the thread for context and decide what it needs — file it, escalate it, or flag the sender.
Under the hood the agent will:
  1. list_emails with direction: "inbound" → find new mail
  2. get_thread → read the conversation
  3. create_shield_rule → act on what it finds — block, allow, route, or quarantine future mail like it

​
The loop, concretely

​
Design tips

Inboundr stores everything but doesn’t mark mail “handled” for you. Keep your own cursor — the newest receivedAt you’ve processed, or a set of handled email ids — so the agent doesn’t act on the same message twice.
Always get_thread before deciding. The last message alone rarely has enough context; the conversation does.
For anything consequential — a Shield rule that blocks a whole domain, say — have the agent draft it and a human approve before it’s applied.
Separate inboxes (sales@, support@, ada@) keep contexts clean and make it obvious which agent owns a conversation. Catch-all still backs them all.

​
Prefer a server?

If your agent runs behind an always-on service, route the address to a webhook endpoint instead of polling — you’ll get each message pushed as it arrives, and the rest of the loop is identical.

MCP reference

Every tool, its parameters, and connection details.