Skip to main content
Illustration showing Migma connected to Claude Code and Claude Desktop

Migma connects to Claude Code and Claude Desktop through Remote MCP

Connect Migma once, then use it from Claude Code or Claude Desktop to design branded emails, manage opted-in contacts, prepare campaigns, and read results. Browser OAuth handles access, so you do not paste an API key into Claude.
Both setup paths use Migma Remote MCP at https://migma.ai/mcp. Choose the section for the Claude app you use.

Start email marketing with Claude

Copy this prompt into Claude Code or Claude Desktop:

Before you start

You need:
  • A Migma account.
  • Claude Code installed and signed in, or access to custom connectors in Claude Desktop.
  • A browser on the same computer for Migma approval.
For Claude Code, check the installation:

Connect with Claude Code

1

Add Migma

Run this command in your terminal:
--scope user makes Migma available in every local Claude Code project for your user account. Use --scope local instead when you want it only in the current project.Confirm the saved configuration:
Illustration showing the Claude Code command that adds Migma as a user-scoped HTTP MCP server

Illustration of the Claude Code MCP setup command

2

Approve the connection

Start Claude Code, then enter:
Choose Migma, select the authentication action, and follow the browser link. Sign in to Migma if needed.Review every requested permission before approving. email:send allows test and live sends. Keep Claude Code’s confirmation controls enabled and approve only when you trust the session to act for you.
Illustration showing Migma permission groups and the Approve connection button for Claude Code

Illustration of the Migma connection review step

Migma creates the scoped connection key automatically. No key needs to be copied into a command or chat.
3

See your account

Run /mcp again and confirm Migma shows as connected. Then ask:
Claude shows your workspaces, brands, plan, and sending domains, then suggests the first useful step.
Illustration showing Migma connected in Claude Code and the account context with brands and suggestions

Illustration of a connected Migma server showing account context

Connect with Claude Desktop

1

Open the connector menu

In a Claude conversation, click +, then choose Connectors → Add connector → Add custom connector.You can also open Customize → Connectors, click +, then choose Add custom connector.
Illustration showing the Claude Desktop menus for Connectors, Add connector, and Add custom connector

Open Add custom connector in Claude Desktop

2

Add Migma

Enter:
  • Name: Migma
  • Remote MCP server URL: https://migma.ai/mcp
Leave OAuth Client ID and OAuth Client Secret empty. Keep individual sign-in enabled, then click Add.
Illustration showing Migma and its Remote MCP URL in Claude Desktop's Add custom connector dialog

Add Migma as a custom connector

3

Approve Migma access

Select Migma, click Connect, and follow the browser window. Sign in to Migma if needed.Review every requested permission before approving. email:send allows test and live sends. Approve only when you trust the Claude session to act for you.
Illustration showing Migma permissions and the Approve connection button for Claude Desktop

Review and approve the Migma connection

4

Enable Migma in the conversation

Click + → Connectors, then turn on Migma. The connector should show as enabled in the current conversation.
Illustration based on the Claude Desktop connector menu showing the Migma connector enabled

Migma enabled in Claude Desktop

5

Send a first request

Start with drafts — creating an email never sends anything:
Illustration of four coordinated emails ready for review on the Migma canvas

Claude can hand a complete email series back to the Migma canvas

On Claude Team or Enterprise, an organization owner may need to add the custom connector first. Each member then connects their own Migma account.

Why Claude alone is not enough

A Claude draft is not a campaign:
  • Brand fonts, colors, logos, and knowledge need to persist across sends.
  • Browser HTML is not email-safe HTML. Outlook, Gmail, and Apple Mail render differently.
  • Marketing sends need opted-in contacts, a verified sender, unsubscribes, and your approval.
  • Results live in campaign stats, not in a chat thread.
Migma owns those steps. Claude stays where you plan and ask.

Run the marketing workflow

1

Pick a brand

Ask Claude to list your brands and choose one. Every later Migma action needs that brand. If Claude asks for a project ID, that is the brand handle used by the API. For a new brand, ask Migma to import it from the website.
2

Save lasting brand facts

When you share tone, products, offers, policies, or FAQs that should persist, ask Claude to save them to the Migma knowledge base. Those facts improve later emails.
3

Design emails and show drafts first

Ask for one email or a short series. Claude should generate the work, wait until it is ready, then show preview images and canvas links. Open a canvas link for visual edits in Migma. Run compatibility, deliverability, or spam checks after you have reviewed the design.
4

Import or build the audience

Upload or paste an opted-in contact CSV and name the list. Ask Claude to use one contact import with the full CSV text. You can also create a segment from contacts already in Migma.
5

Confirm the sender

Campaigns need a sending domain and From address. Ask Claude to list your domains. If none are ready, set up a domain you own, buy one, or start with a managed Migma address. See Sending domains.
6

Check and prepare the campaign

After you approve a draft, ask for a test send, inbox checks, or a small edit. Then create a draft campaign with subject, sender, and recipients. Ask Claude to wait for approval before any live send or schedule. You can also finish launch in the Campaigns UI.
7

Read results

After sending, ask for campaign stats and delivery logs. Clicks are a stronger signal than opens. Use what worked to improve the next brief. See Track results.
Campaigns send one approved email to an audience. Use an email series when you need a connected sequence drafted together. See Campaigns vs series.

Prompts worth saving

Design one email

Design a series

Save brand facts

Import a CSV list

Test, then prepare a campaign

Send after approval

Read performance

Run inbox checks only when you ask, or as a last step before send:

What Claude should and should not do

Export instead of sending in Migma when the campaign lives in another email platform. Available formats and destinations include HTML, PNG, PDF, Klaviyo, Mailchimp, and HubSpot. See Export options.

Sending rules that still apply

  • Send only to contacts with marketing consent. See What you can send.
  • Use a verified sending domain before live campaigns. See Sending domains.
  • Prefer Email Preflight and a test send to yourself before a large campaign.
  • Keep a human in the loop. Claims, audience, sender, and timing remain your decision.

Already designed in Claude?

If Claude produced a React or JSX email as a .zip, import it in Migma:
  1. Open Create, select +, then choose Import Claude design.
  2. Pick Create editable email to keep the direction, or Create brand version to apply your Migma brand.
  3. Upload the .zip and review it on the canvas.
See Claude Design to Email. After import, the same campaign workflow applies.

When to use what

  • Claude + Migma: plan, design, import lists, and launch from one conversation.
  • Migma web app: get visual control on the canvas without connector setup.
  • ChatGPT + Migma: run the same workflow in ChatGPT.
  • API, SDK, or CLI: build automation and CI workflows.

Tools Claude uses

Guided MCP recipes: launch_email_campaign, build_segment_and_send, import_brand_and_generate.

What you can ask Claude to do

Create one email or a series

Ask for drafts, wait for preview images, then open the canvas to review them together.

Use lasting brand context

Work with saved logos, colors, fonts, products, voice, references, and approved facts.

Prepare a campaign

Work with opted-in contacts, sender details, and a campaign draft. Keep live sending behind approval.

Read results

Ask for campaign stats and delivery logs after sending.

Optional: install Migma skills

Migma skills add guided workflows and setup instructions to Claude Code:
Run /reload-plugins inside Claude Code after installation. The plugin can also provide Migma MCP; Claude Code de-duplicates servers that point to the same endpoint.

Disconnect or revoke access

For Claude Code, remove the saved server:
For Claude Desktop, open Customize → Connectors, find Migma, and disconnect it. Removing the connector does not replace revocation. In Migma, open Settings → Developers → API Keys and revoke the Claude connection key. You can also clear authentication from Claude Code’s /mcp menu.

Troubleshooting

For product-specific behavior, see Anthropic’s Claude Code MCP guide and Claude custom connector guide.

Next

How Migma works

See how brand, canvas review, inbox checks, and sending fit together.

Claude setup reference

Compare Claude Code, Claude.ai, and Claude Desktop setup.

MCP permissions

Review access, approval, and revocation before connecting.

Migma MCP server

See available workflows, security guidance, and troubleshooting.
Last modified on September 6, 2026