
Mailbox.bot
@arbengine
About Mailbox.bot
Postal mail API for AI agents. mailbox.bot lets agents send outbound physical mail, including letters, certified mail, postcards, and batch mailings, with cost previews, approval controls, tracking, proof artifacts, and signed webhooks. It also supports inbound mail context from
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mailbox-bot": {
"url": "https://mailbox.bot/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_MAILBOX_BOT_API_KEY"
}
}
}
}Tools
19Get your agent's real mailing address beta endpoint when the account has explicit beta access: street address + mailbox number for approved accounts. For generally available inbound context, use list_inbound_forwarding_addresses instead; that returns a private intake alias for scans, PDFs, photos, provider notices, and notes from addresses the operator already uses.
Get usage summary, billing events, and prepaid credit balance for a time period. Returns itemized events (scans, forwards, mail sends) with costs, period totals, and credits. Defaults to the current billing period if no dates are specified. Use this in Cursor/MCP chat when the human asks how many mailbox.bot credits are left; answer with the prepaid balance and explain that only the signed-in human can add funds.
List the renter’s private inbound forwarding aliases on forward.mailbox.bot. These are the unique intake email addresses an operator, assistant, provider, or external agent can forward scans, PDFs, photos, provider notices, notes, and other context-aware documents to so mailbox.bot can build OCR-backed inbound context. Forwarding/emailing attachments here initiates OCR/extraction; this tool discovers the address and does not upload files directly into OCR. The alias is member-scoped, so live and sandbox agent keys for the same member resolve to the same intake address.
List forwarded inbound mail items captured from private forwarding aliases. Default output includes compact draft_context so an LLM or external agent can reason about OCR context, reply contact candidates, deadlines, and thread linkage before generating outbound mail.
Get one forwarded inbound mail item with compact draft_context by default. Use this before drafting an outbound reply when you need sender context, reply contact candidates, deadline clues, source files, and thread linkage in one stable payload.
List physical-mail threads that group inbound mail context, human review, and outbound sends. Use this to understand which inbound items and outbound documents belong to the same business workflow.
Get one physical-mail thread with optional timeline events. Use this to explain how a generated outbound mail piece relates back to prior inbound scans and review decisions.
Get the renter's MAILBOX.md standing instructions for this agent. Returns the full instruction text, version number, content hash, and last update timestamp. Call this on startup and cache the version — you must pass it to send_outbound_mail for sync verification.
Propose changes to the renter's MAILBOX.md instructions with reasoning. The renter will see your suggestion in their dashboard and can accept, reject, or modify it. Use this when you observe patterns that could be codified into standing instructions.
Send a message to the Austin HQ operator managing your mailbox. Facility routing is automatic. Messages appear in the shared conversation visible to you, the renter, and the facility. Optionally link the message to a specific package or action request for context.
List your Austin HQ conversation with its unread message count and last message preview. Facility routing is automatic.
Read the message thread with Austin HQ. Facility routing is automatic. Returns messages in reverse chronological order with sender role (member, facility, agent). Supports cursor-based pagination. Automatically marks facility messages as read.
Configure webhook endpoint URL and event subscriptions for real-time notifications. Outbound events are mail.pending_approval, mail.submitted, mail.ready, mail.mailed, mail.delivered, mail.failed, and mail.cancelled. Canonical physical-custody events are inbound.received and inbound.scan_available. The endpoint must use HTTPS and respond with 2xx within 10 seconds.
Submit a document for printing and postal mailing by the facility. Supported formats: PDF, DOCX, JPG, PNG, TXT, CSV. The document is stored securely and printed by the facility operator. Published default pricing is $2.50 handling + $0.40/page B&W printing + carrier postage/rate; FedEx Overnight adds a fixed $18.00 after the otherwise-calculated carrier baseline (service_adjustment_cents: 1800). Color pages cost $0.70/page total by default before handling and postage: $0.40/page base B&W printing plus a $0.30/page additive color upgrade. In cost_breakdown, color_printing_per_page_cents is the total color-page printing price (70 cents by default), while color_surcharge_per_page_cents is the additive upgrade only (30 cents by default). Account-specific pricing can override these defaults; cost_breakdown is authoritative. IMPORTANT: With a production key (sk_agent_), this spends the human member's prepaid mailbox.bot credits. Agents never access Stripe, card data, or Auto-Fill settings. If the signed-in human separately enabled Agent Auto-Fill, an eligible live order may trigger a bounded server-managed reload. Use dry_run=true to preview required credits before committing, or requires_approval=true to defer the credit debit until human approval. Sandbox keys (sk_agent_test_) skip credit debits and facility fulfillment. Responses include human_review with send-to address, return address, mail class, document details, preview URL when available, cost, safeguards, and next step; show that to the human before live funded sends. tracking_number is required for priority, certified, certified_return_receipt, FedEx, and UPS mail classes. USPS first_class does not include carrier tracking by default; tracking_number may be null. Optionally attach the outbound mail to inbound context with inbound_capture_id and postal_mail_thread_id so lineage stays explicit. Explicit Business mail runs are REST-only.
List outbound mail jobs with status tracking. Returns mail ID, recipient, mail class, status, cost, timestamps, and failure metadata. Filter by status, created_at date range, or search recipient/address/tracking/agent notes.
Get full details of an outbound mail job including recipient address, mail class, page count, cost breakdown, current status, failure metadata, document metadata, and fulfillment photos. Legacy plaintext records may include direct document URLs; encrypted source documents are retrieved through the REST document endpoint with document.read scope.
Cancel a queued outbound mail job before facility printing starts. If the mail was funded with prepaid credits, eligible credits are returned to the member ledger. Safe to retry: already-cancelled mail returns cancelled status without creating a duplicate refund. In chat, report cancellation status, returned credits, updated balance, and whether it had already been cancelled. If a transient error occurs, poll the mail status and credits before retrying.
Create a sandbox outbound mail record without uploading a real document. The record is always test_mode=true, cost_cents=0, includes estimated_live_cost_cents and cost_breakdown, and queues a mail.submitted webhook. Color pages cost $0.70/page total by default before handling and postage: $0.40/page base B&W printing plus a $0.30/page additive color upgrade. In cost_breakdown, color_printing_per_page_cents is the total color-page printing price (70 cents by default), while color_surcharge_per_page_cents is the additive upgrade only (30 cents by default). Account-specific pricing can override these defaults; cost_breakdown is authoritative. FedEx and UPS estimates use the same configured origin and destination zone/region logic as production; FedEx Overnight adds a fixed $18.00 after the otherwise-calculated carrier baseline and reports service_adjustment_cents: 1800. Use with a sandbox key to rehearse outbound workflows before sending real physical mail.
Advance a test_mode outbound mail record one lifecycle step and queue the matching webhook. submitted becomes ready with simulated pages/envelope photos; ready becomes mailed with carrier, dispatch method, receipt photo, and tracking when the selected service includes tracking; mailed becomes delivered.
Overview
What is Mailbox.bot?
Mailbox.bot is a remote MCP server and postal mail API for AI agents. It enables agents to send outbound physical mail (letters, certified mail, postcards, batch mailings) with cost previews, approval controls, tracking, proof artifacts, and signed webhooks. It also supports inbound mail context from forwarded scans, photos, PDFs, and documents, allowing agents to understand and generate replies to physical mail.
How to use Mailbox.bot?
Configure the server by adding the mailbox-bot entry to your mcpServers JSON with the endpoint https://mailbox.bot/api/mcp and an Authorization header using a Bearer token from your mailbox.bot API key. The server uses Streamable HTTP transport.
Key features of Mailbox.bot
- Send outbound postal mail, certified mail, and postcards
- Preview mailing costs before sending
- Track outbound mail status in real time
- Receive proof artifacts and signed webhooks
- Process inbound mail context from scans, PDFs, and photos
- Generate replies using physical-mail context
Use cases of Mailbox.bot
- An AI assistant sends a certified letter on behalf of a user and tracks its delivery.
- A business processes incoming postal mail photos, extracts context, and drafts a response.
- An agent previews costs for a batch mailing before approving the send.
- A user receives proof of delivery artifacts via webhook after a postcard is mailed.
FAQ from Mailbox.bot
What transport does Mailbox.bot use?
Mailbox.bot uses Streamable HTTP transport.
How do I authenticate with Mailbox.bot?
Authentication is via a Bearer token in the Authorization header using your mailbox.bot API key.
Can Mailbox.bot handle inbound mail?
Yes, it processes inbound mail context from forwarded scans, phone-captured postal mail, PDFs, photos, and documents so agents can understand physical-mail context and generate replies.
Does Mailbox.bot support real street-address mailboxes?
Real street-address receiving mailboxes for AI agents are opening soon through the mailbox.bot waitlist.
Frequently asked questions
What transport does Mailbox.bot use?
Mailbox.bot uses Streamable HTTP transport.
How do I authenticate with Mailbox.bot?
Authentication is via a Bearer token in the `Authorization` header using your mailbox.bot API key.
Can Mailbox.bot handle inbound mail?
Yes, it processes inbound mail context from forwarded scans, phone-captured postal mail, PDFs, photos, and documents so agents can understand physical-mail context and generate replies.
Does Mailbox.bot support real street-address mailboxes?
Real street-address receiving mailboxes for AI agents are opening soon through the mailbox.bot waitlist.
Basic information
More Other MCP servers
Inbox Zero AI MCP
elie222The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
FastMCP v2 🚀
jlowin🚀 The fast, Pythonic way to build MCP servers and clients.
IDA Pro MCP
mrexodiaAI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Mcp
browsermcpBrowser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
🚀 Model Context Protocol (MCP) Curriculum for Beginners
microsoftThis open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
Comments