Inboxr is the MCP server that lets an agent spin up a real mailbox, receive the verification email, and pull the OTP or magic link — on its own, mid-task. One config block in Claude, Cursor, or Claude Code and your agent can sign up, confirm, and log in like a human. REST, SMTP, and webhooks are there too when you want them.
Paste one block into Claude, Cursor, or Claude Code and the agent can create inboxes, wait for mail, and pull OTPs on its own. Prefer to wire it yourself? The same surface is one SDK import, one Python call, or one curl away.
// 1. Add the MCP server to your agent (claude_desktop_config.json,
// .cursor/mcp.json, or .claude/settings.json):
{
"mcpServers": {
"inboxr": {
"command": "npx",
"args": ["-y", "@jassra25/inboxr-mcp"],
"env": { "INBOXR_API_KEY": "inb_live_..." }
}
}
}
// 2. Now just ask the agent — it drives the tools itself:
//
// "Sign up for the app at staging.example.com with a fresh
// inbox, click the verification link, and tell me the
// dashboard URL you land on."
//
// Under the hood the agent calls:
// create_inbox() -> a real mailbox, instantly
// wait_for_message() -> blocks for the verification email
// extract_link() -> pulls the magic link, opens it
//
// No glue code. The agent owns the whole signup-and-confirm loop.
An agent asks for a channel, gets a real one provisioned on the spot, waits for the inbound message, and extracts what it needs — all through MCP tool calls. Flip between channels to see the flow.
create_inbox()Agent gets a real, live mailbox — no human picks an address.
wait_for_message()Long-polls until the verification mail lands, ~200 ms after MX.
extract_link()Pulls the magic link straight out of the HTML body.
Real email, SMS, and voice — running today on getinboxr.app — with an MCP server built so an AI agent can drive a whole signup-and-confirm flow on its own. REST, SMTP, and webhook surfaces are right there for the code you write by hand.
Drop @jassra25/inboxr-mcp into Claude Desktop, Cursor, or Claude Code. Tools for email, SMS, and voice — create_inbox, wait_for_message, extract_otp, extract_link, sms_*, voice_* — let an agent run signup-and-confirm flows end-to-end.
Wire up an agentBearer-authenticated /v1 endpoints for inboxes, messages, sending, and waiting. Try every call live in the in-portal playground.
Open the playgroundsmtp.getinboxr.app:587 with STARTTLS. Issue a per-inbox credential from /v1/inboxes/{id}/smtp-credentials and drop it into nodemailer / lettre / msmtp.
See SMTP docsPush every inbound message to your CI runner within ~200 ms of arrival. HMAC-SHA256 signed, 5-attempt retry with exponential backoff.
Configure webhooks# Claude Desktop / Cursor / Claude Code
{
"mcpServers": {
"inboxr": {
"command": "npx",
"args": ["-y", "@jassra25/inboxr-mcp"],
"env": {
"INBOXR_API_KEY": "inb_live_...",
"INBOXR_API_URL": "https://api.getinboxr.app"
}
}
}
}Restart your agent and it can create_inbox, wait_for_message, extract_otp, and extract_link without writing a line of glue.
An agent calls create_inbox / sms_create_inbox and gets a real, live mailbox or number it controls — provisioned mid-task, no human in the loop.
One MCP call blocks until the mail or SMS lands, then extract_otp / extract_link hands back exactly what the agent needs. No regex plumbing to write.
Every message exposes auth-results + the full RFC822 source. Confirm you're emulating production correctly.
Run the entire stack yourself — Postfix + Dovecot + OpenDKIM — with the same API surface. Pay us only when you want the cloud layer.
Hit a quota? Clear dashboard, predictable overage pricing. No surprise invoices.
Ship enterprise from day one. Google / Microsoft / Okta / custom SAML — plus SCIM for Scale + Enterprise.
Every plan ships with the full API, webhooks, and the web UI. Higher tiers add SSO, retention, and compliance. Need Enterprise? Get in touch.
Overage: $0.001 per message, $0.0001 per API call. Self-hosting free forever — run the engine yourself.