Inboxr is a multi-channel messaging platform. Connect email, SMS, Telegram, and WhatsApp per workspace and send, receive, branch, and filter through a single unified message log. Broadcast to many recipients, attach files, and read cross-channel analytics — over REST, SMTP, webhooks, or the MCP server your AI agents already speak.
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.
Email, SMS, Telegram, and WhatsApp — running today on getinboxr.app — behind one unified message log. Drive them from an AI agent over MCP, the bearer /v1 API, SMTP submission, or HMAC-signed webhooks. Same surface across every connector; pick whichever is closest to your code.
Drop @jassra25/inboxr-mcp into Claude Desktop, Cursor, or Claude Code. Tools across every channel — create_inbox, wait_for_message, extract_otp, extract_link, plus connector send + broadcast — let an agent run signup-and-confirm flows end-to-end.
Wire up an agentBearer-authenticated /v1 endpoints for inboxes, messages, connectors, sending, and broadcasting across email, SMS, Telegram, and WhatsApp. 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.
Email, SMS, Telegram, and WhatsApp land in a single tenant-scoped log with a shared shape — peer, direction, body, timestamp. Read every channel through one API.
Connect your bot in one paste of its token. We register the webhook, route two-way chat and files, and let you broadcast to every subscriber — $19/mo.
Bring your Meta Cloud API number and send template + session messages on your WABA. Signed inbound, per-connector billing — $49/mo plus Meta pass-through.
Route inbound by channel, sender, or content and forward matches to your own endpoint. The same rule engine that powers email flows now spans every connector.
Fan one message out to hundreds of recipients. Small sends go inline; large audiences queue to a worker that paces delivery at a provider-safe rate.
Send and receive media across channels that support it — images, documents, and voice notes flow through with the message, not around it.
Inbound vs outbound volume per connector, plus a daily time series over the unified log. See the whole platform in one dashboard, not four.
Drive every channel from an AI agent over MCP, or hit the bearer /v1 API, SMTP submission, and HMAC-signed webhooks by hand. Same surface, your choice.
Every plan ships with the full API, webhooks, and the MCP server. SMS and channel connectors bill on their own axes — see the full pricing page for the complete picture.
Need Enterprise, SMS, or the Telegram / WhatsApp connectors? See full pricing → Self-hosting free forever — run the engine yourself.