mailbox.bot MCP Server
Connect any MCP-capable AI client to mailbox.bot using Model Context Protocol (MCP). Your agent gets 29 tools for inbound context, package management, scans, facility messages, outbound mail, standing instructions, and webhooks.
Inbound context loop
Use list_inbound_forwarding_addresses to discover the renter's private alias on forward.mailbox.bot. Forward or email scans, PDFs, photos, provider notices, and notes to that alias to initiate OCR/extraction. Then use list_inbound_mail or get_inbound_mail to retrieve draft_context for your LLM, and pass inbound_capture_id / postal_mail_thread_id into send_outbound_mail when the generated reply becomes physical mail.
Hosted MCP endpoint
https://mailbox.bot/api/mcpStreamable HTTPAuthorization: Bearer YOUR_API_KEY1. Get your API key
Copy an sk_agent_ key for agent use, or an sk_agent_test_ key for sandbox testing. You can also use an account sk_live_ key during setup. Get keys from the dashboard, then paste one below to fill the examples.
2. Choose your MCP client
Add this block to any MCP client that supports remote HTTP servers: Use https://mailbox.bot/api/mcp as the server URL and pass your API key in the Authorization header. If your client expects a local command instead of a remote URL, use the command bridge preset.
{
"mcpServers": {
"mailbox-bot": {
"url": "https://mailbox.bot/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Troubleshooting
Switch to the Bridge preset. It runs mcp-remote locally and connects to the same hosted endpoint.
Install Node.js LTS, restart the client, then refresh MCP servers. Command-bridge presets require npx.
Restart the client or use its MCP server refresh action. Some clients only load MCP servers at startup.
3. Reload your MCP client
Restart or reload your client so it discovers the mailbox.bot tools. Ask your agent to list packages, request a scan, send facility messages, or create outbound mail.