Mailbase Developer Docs

Production integration notes for teams that want Mailbase to sit cleanly inside their app, backend jobs, AI tools, and self-hosted email stack.

Start Here

Mailbase has two integration surfaces: the REST API for product teams that need deterministic backend calls, and the MCP server for AI-assisted workflow clients. Both are workspace-scoped and designed around your sender domains, audiences, campaigns, replies, and useSend setup.

REST API
Send transactional email, list campaigns, and create audiences from your backend.
Open docs
useSend integration
Connect your own useSend instance, API key, webhooks, sender domains, and reply inbox.
Open docs
MCP server
Connect Claude Code, Cursor, Codex, or any MCP client to your workspace.
Open docs
Pricing model
Understand transactional volume, marketing contacts, and bring-your-own useSend.
Open docs

Professional Integration Checklist

  • Create a workspace and verify at least one sender domain.
  • Open Settings, then Developer API, and create a scoped API token.
  • Store the token in your backend secret manager, never in frontend code.
  • Call /api/v1/me from CI or staging to verify the token scope.
  • Use /api/v1/send for transactional email from your app.
  • Use useSend webhooks so delivery, bounce, complaint, and reply events flow back.