Integrations

Connect MailerBot to your existing tools and workflows. Send physical mail from AI assistants, automation platforms, and more.

Connect MailerBot

Automation platforms and SDKs you can use today, and what comes next.

Start Sending

4 available3 coming soon

Automation

Workflow automation platforms.

Available
Add MailerBot to your Zapier workflows.
Available
Add MailerBot to your Make scenarios.

Developer SDKs

Client libraries for the MailerBot API.

Python SDK
Available
Work with the MailerBot API from Python.
JavaScript SDK
Available
Work with the MailerBot API from JavaScript.

For endpoints and authentication, see the API reference.

Coming soon

Not available yet.

website (opens in a new tab)
Coming soon
website (opens in a new tab)
Coming soon
website (opens in a new tab)
Coming soon

What you can do

Create and send letters & postcards
Design postcards with AI
Use templates & merge fields

Manage contacts & address books
Track orders & delivery status
Check pricing & account balance

Server URL

https://mcp.mailerbot.com/mcp

Quick Setup: Claude Code

Run this command in your terminal:

claude mcp add --transport http mailerbot https://mcp.mailerbot.com/mcp

In Claude Code, use /mcp and follow the MailerBot sign-in flow. For Claude Desktop, open Customize > Connectors, add a custom connector named MailerBot with https://mcp.mailerbot.com/mcp, then complete authentication. Team and Enterprise users may need an organization owner to add the connector first.

Quick Setup: Cursor

Add this remote server to .cursor/mcp.json for your project:

{
  "mcpServers": {
    "mailerbot": {
      "url": "https://mcp.mailerbot.com/mcp"
    }
  }
}

For a global configuration, use ~/.cursor/mcp.json. Follow Cursor’s authentication prompt to sign in to MailerBot. For Windsurf or another MCP client, follow its own remote HTTP server instructions using the same endpoint.

Authentication

The MCP server uses OAuth 2.1. When you first connect, you'll be redirected to sign in with your MailerBot account. Your session persists across requests — no API keys needed.