Building Interactive Emails with an AI Copilot & MCP Server

A studio full of layout, chart, form and event blocks is only as useful as how fast you can get an idea onto the canvas. The AI copilot is a real multi-turn conversation, not a one-shot draft: it edits your project's block tree one change at a time — the same way you'd use the studio yourself — so a follow-up request only touches what you asked for. The same tool access is exposed as an MCP server, so an agency running client builds through Claude Code, or a developer scripting emails from their own AI tooling, gets the identical capability without ever opening the dashboard.

Chat with the AI copilot in the studio to build or edit an email one block at a time, or point Claude Desktop or Claude Code at MailInApp's MCP server and get the identical capability from outside the dashboard.

A studio full of layout, chart, form and event blocks is only as useful as how fast you can get an idea onto the canvas — and a good idea rarely arrives fully formed in one request.

Grounded in your Brand Voice Profile

The AI Copilot automatically loads your account's Brand Voice Profile on every turn:

  • Tone Guidelines: Learns your brand's unique tone (direct, technical, witty, authoritative).
  • Banned Words & Buzzwords: Automatically avoids AI tells ("seamlessly", "unlock", "game-changer") and custom banned terms.
  • Value Proposition: Weaves your brand's core positioning naturally into copy.

A real conversation, not a one-shot draft

The old "Generate with AI" button made a single structured-output call and handed back a whole email you could only regenerate, never adjust. The copilot instead edits your project's block tree one change at a time — add, update, move, or remove a single block — the same way you'd use the studio yourself. A follow-up like "swap the countdown for a poll" only touches that one block instead of rebuilding the email from scratch.

Pre-Flight Quality Verification

Before sending, run the 🔍 Pre-Flight Check in the studio toolbar to verify AI-generated copy against your brand guidelines. The Pre-Flight Inspector computes a 0–100% Quality Score and flags any remaining AI buzzwords, dark mode image risks, or missing mobile CTAs.

Every block type, not a fixed subset

Because the copilot works by calling the same tools a human editor calls, it automatically covers every block the studio registry defines — layout (section, columns, repeat), all 13 chart types, event blocks like RSVP and meeting link, forms, quizzes, and your project's theme tokens.

The same tools, two front doors

src/lib/studio/aiTools.ts's tool core — add_block, update_block, remove_block, move_block, set_theme, get_tree — is shared by both front doors:

  • In the studio, the ✨ AI Copilot toolbar button opens a chat panel that applies changes straight to your open canvas, through the same undo/redo stack as any manual edit.
  • Over MCP, an external client authenticates with the same Bearer API key as the Send API and writes directly to the project — no open browser tab required.

Plan availability

The AI copilot and MCP server draw from one shared monthly turn allowance, available from the Lite plan up — Free and Starter don't include it. See pricing for exact allowances per plan.

A typical build-and-send sequence

  1. 1

    Open the copilot or connect the MCP server

    In the studio, click ✨ AI Copilot in the toolbar; from an external tool, add MailInApp as an MCP server in Claude Desktop or Claude Code using an API key minted under Developers.

  2. 2

    Describe the email, or one change to it

    "Build a product-drop email with a countdown and a product block" for a first draft, or "swap the countdown for a poll" for a targeted edit to something already built — both are the same kind of request.

  3. 3

    Watch it edit the real tree

    Each reply is an actual add_block/update_block/move_block/set_theme call against the project, not a wholesale regeneration — the studio canvas (or, over MCP, the project itself) updates block by block.

  4. 4

    Review, then send

    Every change flows through the studio's normal undo/redo and autosave; nothing about sending, the fallback engine, or plan limits changes because AI built or edited a block instead of a person dragging one.

Frequently asked questions

How is this different from the old "Generate with AI" button?

The old button made one structured-output call that could reach only 16 of the studio's block types and could never produce a container like a section or columns layout, because that mode has no way to describe nested structure. The copilot instead edits the tree one node at a time via tool calls, so it automatically covers every block type the registry defines — charts, events, layout, all of it — with no hand-maintained list to fall behind.

Can it accidentally wreck an email I've already built?

Every copilot change lands through the same undo/redo stack as a manual edit, so Ctrl/Cmd+Z reverses it exactly like it would a drag-and-drop mistake. It also never invents real prices, dates or URLs, and never touches the unsubscribe footer or social links — those stay automatic.

What can I do through the MCP server that I can't do in the studio chat?

The tool set is identical either way — list, create, read and edit projects. The difference is where the request comes from: the in-studio panel needs an open browser tab and applies changes to your current canvas session, while the MCP server writes directly to the project so an agent running outside the dashboard (a script, Claude Code, an agency's own tooling) can build or edit an email with no browser involved at all.

Does an MCP-driven edit show up if I have the project open at the same time?

Yes — an external edit bumps the project's revision exactly like any other save, so your next autosave in an already-open studio tab shows the same "Changed elsewhere" conflict banner you'd get from a teammate editing concurrently.

Is there a separate credential for the MCP server?

No — it authenticates with the same API key used for the Send API (Authorization: Bearer, minted under Developers), so there's nothing new to provision if you're already calling the API.

Which plans include it?

The AI copilot and MCP server share one monthly turn allowance, available from the Lite plan up; Free and Starter don't include it. Both draw from the same counter, since an in-studio chat message and an MCP tool call run the identical underlying loop.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.