> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# From Claude brief to sent email

> Research and brief in Claude, then create, check, and send the email with Migma

Claude writes the brief. Migma turns it into a real email: on-brand, editable, checked against Outlook, Gmail, and Apple Mail, ready to export or send. Connect Migma to Claude once, then ask for emails in plain language. You approve every send.

This is a Migma product guide, current as of August 15, 2026.

## Why the hand-off matters

Claude produces strong language and useful code, but a chat response is not a campaign:

* Brand assets and rules need to persist across campaigns.
* Browser HTML is not email-safe HTML, and mail clients render markup differently.
* Links, claims, and compatibility risks need review before anything ships.
* Sends need an opted-in audience, a sender identity, unsubscribes, and your approval.

Migma owns those steps. Claude stays the place where you think.

## Pick your route

Working with an existing Migma brand: connect MCP. Already designed something in Claude: import the .zip. Both end on the same editable canvas.

### Route 1: connect Claude to Migma

Add Migma as a custom connector in Claude with one URL:

```text theme={null}
https://migma.ai/mcp
```

Claude opens Migma's browser sign-in and consent screen. Review the requested permissions before approving; no API key gets pasted into Claude. Once connected, ask Claude to call `migma_get_capabilities` first so it plans with the tools your account actually has.

Setup details per client live in [MCP Server](/mcp-server) and [Claude setup](/agents/mcp-claude). [Watch the demo](https://x.com/Migma_AI/status/2087980715262505180).

### Route 2: import a Claude design

If Claude produced a React or JSX email design, export it as a .zip, then in Migma:

1. Open **Create**, select the **+** menu, and choose **Import Claude design**.
2. Pick **Create editable email** to preserve the direction, or **Create brand version** to apply your Migma brand.
3. Upload the .zip and review the converted email on the canvas.

Full walkthrough: [Claude Design to Email](/creating-emails/claude-design).

## Prompts worth saving

Create one email:

```text theme={null}
Use Migma to create one editable email for [brand].
Audience: [segment]
Decision: [what the reader should do]
Evidence: [approved facts and URLs]
Constraints: one CTA, no invented metrics.
Do not send. Return the email ID and a review checklist.
```

Create a series:

```text theme={null}
Use Migma to prepare a three-email onboarding series for [brand].
Email 1: first value
Email 2: overcome setup friction
Email 3: invite the next action
Keep the progression clear. Do not create a campaign or send.
```

Validate before hand-off:

```text theme={null}
Run available Migma validation for email [ID].
Separate confirmed errors, warnings, and checks not available.
Do not auto-fix. Recommend the smallest changes first.
```

## The workflow

<Steps>
  <Step title="Brief in Claude">
    Give Claude a decision, not a topic. "We are announcing collaborative dashboards to existing customers. Primary reader is a marketing lead managing three brands. Goal: get them to create their first shared dashboard. Separate verified facts from assumptions." Claude returns audience, offer, proof, CTA, and open questions.
  </Step>

  <Step title="Create in Migma">
    "Create a launch email from this approved brief. One primary CTA. Only verified facts. Do not send. Return the email ID." Saying "do not send" keeps creation separate from delivery.
  </Step>

  <Step title="Review on the canvas">
    Open the email in Migma. Check brand and logo, claim accuracy, CTA destination, mobile hierarchy, image alt text, footer links. Fix one section with chat or the visual editor instead of regenerating everything.
  </Step>

  <Step title="Run Preflight">
    Ask Claude to run validation and report errors, warnings, and unknowns separately. Then open [Email Preflight](/email-editor/email-preflight) and [client previews](/email-editor/client-compatibility), fix blockers, and send a test to yourself.
  </Step>

  <Step title="Export or send">
    Export HTML, PNG, or PDF, hand off to your email platform, or prepare a Migma campaign. Before any send, have Claude state the recipient scope, sender, subject, and timing. You approve last.
  </Step>
</Steps>

## When to use what

* **Claude + Migma**: research, reasoning, and email work in one conversation.
* **Migma web app**: a marketer wants visual control without connector setup.
* **[API](/api-reference/introduction), [SDK](/sdk), or [CLI](/cli)**: the workflow runs in code or CI.

## Keep a human in the loop

Claude can misread a source. A draft can need correction. Rendering checks do not guarantee inbox placement or legal compliance. Review claims, audience consent, sender identity, and a final test email before every send.

## Next

<CardGroup cols={2}>
  <Card title="Claude setup" icon="https://mintcdn.com/migmaai/kT6TJgF40rDP8_qB/images/logos/claude-code.png?fit=max&auto=format&n=kT6TJgF40rDP8_qB&q=85&s=21dc5dcc66f09660a16fbea3297333b4" href="/agents/mcp-claude" width="120" height="120" data-path="images/logos/claude-code.png">
    Connect Claude Desktop or Claude Code to Migma.
  </Card>

  <Card title="Claude Design to Email" icon="palette" href="/creating-emails/claude-design">
    Import a Claude-built design as an editable email.
  </Card>
</CardGroup>