Docs Pricing Blog Dashboard Open Dashboard

Programmable inboxes for your AI agents.

Send, receive, track, and replay. One API. Full visibility.

$ npx mailbot-mcp
Free sandbox included · No credit card required
getmail.bot · POST /v1/inboxes bash
MX records configured
Event notifications active
Ready to receive email
1

Create inbox

Provision a programmatic inbox via API. MX records auto-configured.

2

Send & receive

Send outbound. Receive inbound. Threads maintained automatically.

3

Track everything

Per-message open, click, bounce. Full event timeline for every email.

4

Debug & replay

Inspect event payloads. Replay any failed delivery. Fix without waiting.

0
Deliverability
Observed inbox placement trend
0%
Delivery Rate
52 emails sent, 0 bounced
0%
Open Rate
Live production data
0%
Click Rate
Live production data
10 yrs
Operational Maturity
Built for real production workflows

Real numbers from live production. Not projections.

Stop stitching email together.

Most email tools make sending easy. Much fewer make it easy to receive email, preserve thread context, inspect what happened, and recover when downstream systems fail. mailbot gives developers one programmable system for inboxes, messages, threads, events, and replay.

No visibility after send

You send email but get no feedback. Did it deliver? Was it opened? Did the link get clicked? Without observability, workflows fly blind.

Receive is harder than send

Most tools stop at sending. Real workflows need inbound email, thread context, and structured events — not manual mailbox setup and fragile infrastructure.

No recovery when things break

When an event consumer misses a notification or downstream systems fail, most email tools offer no replay or recovery. You're left guessing what happened.

mailbot gives you inboxes, two-way email, tracking, and replay — in one system.

See what happened, not just
that something sent.

mailbot is designed for developers who need to inspect, debug, and recover email workflows. Review thread history, inspect payloads, track lifecycle events, and replay deliveries.

← INBOUND
DELIVEREDOPENED (3×)CLICKED (1×)
customer@example.com · 3 min ago
Hi, I need help with my recent invoice...
→ OUTBOUND
DELIVEREDOPENED (1×)
agent-001@mailbot.id · 1 min ago
Thanks for reaching out! Your invoice #1234...

Per-message engagement, not just aggregate stats

Every email in your agent's inbox shows exactly what happened: delivered, opened (3×), clicked. Not just open rates across all emails — per-message, per-event. See which email triggered your agent's next action.

message.inbound
From: customer@example.com
notification.delivered
Delivered to your endpoint · 200ms
agent.started
Agent #1 processing
message.outbound
Accepted for delivery
message.delivered
Delivery confirmed
message.opened
Opened 3× from mobile

Chronological event timeline, like Chrome DevTools

Every event that touched a message — inbound, outbound, delivered, opened, clicked, bounced — in a single scrollable timeline. Color-coded. Filterable by type. Click any event to inspect its full payload.

Request
Response
MIME
Retries
POST your-app.example.com/webhooks/mailbot 200 OK
1 { 2 "event_id": "evt_ghi789", 3 "type": "message.inbound", 4 "from": "customer@example.com", 5 "subject": "Re: Support #1234" 6 }
Copy JSON
Copy as cURL
Replay Event

Debug events without leaving the console

Click any event to see the full request and response. JSON syntax-highlighted, collapsible nodes, line numbers. Copy the exact event payload as a cURL command, paste it into your terminal, and replay it from the console.

Recent
Re: Invoice #1234 — customer@example.com2m ago
Welcome email — new-user@company.com15m ago
Refund request — billing@example.com1h ago
Actions
Create Inbox⌘N
Go to Settings⌘,
Copy API Key⌘.

Navigate like it's VS Code

Cmd+K opens a command palette that indexes all your inboxes, conversations, and settings. j/k to navigate the list, Enter to open, e to toggle the event rail, / to search. No mouse required.

Five steps from API call to full visibility.

No SDK required. No vendor lock-in. Just a REST API and Bearer token authentication.

Create Inbox
Send Email
Receive via Hook
Track Engagement
Replay Event
POST /v1/inboxes bash

Built for workflows developers actually ship.

mailbot fits concrete workflow jobs — not abstract hype categories. Each use case below runs on real mailbot primitives: inboxes, threads, events, and replay.

💬 P0 · Most requested

Support automation

Receive inbound customer email, classify and respond via your agent, preserve thread context across the entire conversation, escalate when needed. Inspect every step in the event timeline.

// Agent receives customer email notification app.post('/webhooks/mailbot', async (req) => { const { from, subject, text, thread_id } = req.body.data; const reply = await agent.generateReply(text); await mailbot.messages.send({ inboxId, threadId: thread_id, to: [from], subject: `Re: ${subject}`, text: reply }); });
🧪 P0 · QA teams

Email testing & QA

Create isolated inboxes per test run, send transactional emails through your system, retrieve and assert on content/subject/links via API, tear down cleanly. No shared state between tests.

// Jest: verify welcome email const inbox = await mailbot.inboxes.create({ username: `test-${Date.now()}` }); await triggerSignup(inbox.email); const messages = await mailbot.messages.list(inbox.id); expect(messages[0].subject).toContain('Welcome'); await mailbot.inboxes.delete(inbox.id);
📊 P1 · Growth teams

Outbound with engagement awareness

Send outbound email and know exactly what happened: delivered? opened? clicked? replied? bounced? Your agent can react to each event in real-time via notifications.

// React when prospect opens your email app.post('/webhooks/mailbot', async (req) => { if (req.body.type === 'message.opened') { const { message_id, open_count } = req.body.data; if (open_count >= 3) { await crm.markAsHotLead(message_id); } } });
📄 P1 · Ops teams

Document & operational intake

Receive invoices, confirmations, and operational notifications by email. Extract attachments, parse structured data, route to downstream systems. All with full audit trail.

// Process incoming invoice app.post('/webhooks/mailbot', async (req) => { const { attachments, from } = req.body.data; for (const file of attachments) { const invoice = await parseInvoice(file.url); await accounting.createEntry(invoice); } });

MCP Server. Two SDKs. Five minutes.

Add mailbot to Claude Desktop in one config. Or install the SDK and send your first email.

MCP Server POPULAR
Claude Desktop, Claude Code, Cursor, and any MCP client.
$ npx mailbot-mcp
Terminal
# add to Claude Code: $ claude mcp add mailbot -- npx mailbot-mcp # set your API key: $ export MAILBOT_API_KEY=mb_your_api_key_here
Node.js
$ npm install @mailbot/sdk
import { MailBot } from '@mailbot/sdk'; const client = new MailBot({ apiKey: 'mb_live_xxx' }); // Create inbox + send email in 4 lines const inbox = await client.inboxes.create({ username: 'support-bot', domain: 'yourdomain.com' }); await client.messages.send({ inboxId: inbox.id, to: ['user@example.com'], subject: 'Hello from mailbot', text: 'Your agent is live.' });
🐍 Python
$ pip install mailbot-sdk
from mailbot import MailBot client = MailBot(api_key="mb_live_xxx") # Create inbox + send email in 4 lines inbox = client.inboxes.create( username="support-bot", domain="yourdomain.com" ) client.messages.send( inbox_id=inbox.id, to=["user@example.com"], subject="Hello from mailbot", text="Your agent is live." )

Fits into your existing stack.

Start with plain HTTP and event notifications, then plug mailbot into whatever runtime or agent workflow you already use.

MCP Server

npx mailbot-mcp

REST API

POST /v1/inboxes

Event Notifications

POST /your-endpoint

Node.js

npm install @mailbot/sdk

Python

pip install mailbot-sdk

Launch faster with fewer moving parts.

mailbot gives teams one surface for inboxes, sending, replies, tracking, and operational visibility, so you can ship email workflows without stitching together multiple tools first.

mailbot
YOUR AGENTAPI call
REST API
mailbot APIYou control this
Direct path
mailbot deliveryManaged for you
Delivered
INBOX DELIVEREDRecipient mail server
Other email APIs
YOUR AGENTAPI call
Email APINo control
Extra moving partsMore setup to manage
maybe?
INBOXNo guarantee

Fast Setup

Create an inbox, send a message, and receive replies without a long onboarding path.

Operational Visibility

See message status, delivery attempts, and conversation history in one place.

📅

Built for Real Workflows

Designed for support, ops, outbound, and agent-driven inbox automation.

🔒

Secure by Default

API keys, event verification, and account-level controls are built into the platform.

📍

Flexible Rollout

Start on a shared setup, then bring your own domain and production workflow when ready.

What you get on day 1:

✓ SPF, DKIM, DMARC auto-configured on domain verification
✓ Managed sending path with no manual warm-up checklist
✓ Inbound email routing built-in
✓ Event delivery with automatic retry + replay
✓ Full event timeline per message
✓ Dashboard with Cmd+K, keyboard navigation

"mailbot should feel easy to adopt on day one and easy to operate on day one hundred."

The Console. Outlook meets Chrome DevTools.

Every inbox, conversation, event, and notification payload is one keyboard shortcut away. Dark mode default. Zero magic, full control.

mailbot Console — getmail.bot/dashboard/console
Inboxes
support@mailbot.id
12 conversations
billing@mailbot.id
5 conversations
agent-001@mailbot.id
8 conversations
Conversations
Re: Invoice #1234
DELIVEREDOPENED (3×)
customer@example.com · 3m
Welcome to mailbot
DELIVEREDOPENED (1×)CLICKED
new-user@company.com · 15m
Refund request
DELIVERED
billing@example.com · 1h
Event Timeline
message.inbound
3m ago
notification.delivered
200 OK · 145ms
agent.started
Processing
message.outbound
Accepted for delivery
message.delivered
Confirmed
message.opened
3× mobile

Keyboard-first

j/k navigation, Cmd+K, full shortcut coverage

Event Replay

Re-fire any event to any endpoint. Same payload, new delivery.

{}

JSON Payload Viewer

Collapsible, syntax-highlighted. Copy as cURL in one click.

Dark / Light

Ships dark. Toggle with one click. Your preference saved.

Not your typical email API.

You have options. Here's why mailbot is different from each.

vs. Build Your Own

Don't spend weeks before your first email

Building your own email workflow means stitching together inboxes, sending, parsing, event routing, retries, and observability before you even validate the product. mailbot gets you to a usable workflow faster.

vs. Generic Email API

See more than just "sent"

Generic email APIs can stop at send primitives. mailbot keeps inboxes, replies, event flow, and message status connected so your team can actually operate the workflow.

vs. Agent Email SaaS

Debug what your agent actually did

Other agent email services give you an inbox API. mailbot gives you an inbox API plus a DevTools-grade console: per-message engagement, event timelines, event payload viewer, and replay — so you can understand and fix failures.

Built by developers who hate bad tooling.

The mailbot Console is designed to the same standard as your IDE. Every UI filter exports to an API call. Every event is inspectable. Every action has a keyboard shortcut. No sales calls. No onboarding emails. Self-serve by design.

⌘KOpen command palette
j / kNavigate conversations
eToggle event timeline
/Focus search
cCopy conversation ID
?Show all shortcuts
</>

Every filter = API parameter

Set filters in the UI. Copy the equivalent API call below the filter bar. Paste into your code.

Command Palette

Cmd+K. Search inboxes, conversations, settings, shortcuts.

Keyboard Navigation

j/k navigate. Enter opens. Escape closes. No mouse required.

>_

Copy as cURL

One click generates a cURL command for any API call or event payload.

Event Replay

Re-fire any past event to any endpoint. Override target URL on the fly.

🔑

Self-Serve API Key

Create account, get API key, start building — no sales, no demo, no trial approval.

Trust and operational control.

Practical security controls

Security controls from API authentication to verified event delivery, with an audit trail for operational visibility.

🌐

GDPR Aware

Built with European data protection principles in mind.

🏳

Data Protection Compliant

Built to meet regional data protection requirements.

📍

Regional Data Residency

Data stored and processed in your preferred region.

🔒

API Keys Hashed with Argon2

Your API credentials are never stored in plaintext. Industry-standard key hashing.

mailbot is designed to give teams a cleaner operational surface, with practical controls for authentication, event verification, and day-to-day visibility.

Build email workflows with less guessing.

Start with a shared domain, or bring your own when you're ready.

Free to start · No credit card required · Setup in minutes

Setup in minutes · Event visibility built in · Global developer product