AI/MCP Email Workflow in Mailbase

Overview

Mailbase exposes a workspace-safe MCP server for email operations. OAuth-scoped MCP clients can work with audiences, templates, contacts, suppressions, analytics, send jobs, replies, campaigns, scheduling, and AI task completion without guessing a workspace.

Tool Surface

The MCP tools cover read and write operations that match the product workflow: list campaigns, draft variants, inspect analytics, review send jobs, work with contacts and suppressions, and complete queued AI tasks.

Workspace selection is explicit. OAuth-scoped clients stay pinned to the authorized workspace, and legacy sessions fail safely when a workspace cannot be resolved.

Workspace selection tools
Campaign and scheduling tools
Analytics and send-job tools
Audience, template, contact, and suppression tools
AI task completion tools

Review-First AI

AI output enters Mailbase through task completion schemas. The app stores the result, shows review history, and lets teammates apply supported outputs to replies, templates, tags, or contact notes.

Workspace AI policy settings expose tone, signature, forbidden claims, and pricing guidance to MCP clients before they write.

Structured result schemas
Completed-task review history
Apply actions
Workspace AI policy
No automatic sending

Common Mistakes

Choosing a tool before deciding who owns deliverability.
Treating DNS authentication as a one-time checkbox instead of an operating baseline.
Mixing product-critical transactional email with experimental marketing sends, with no clear boundary.
Trusting headline metrics (like open rate) that privacy proxies now inflate.