Skip to main content
ChatGPT briefs and decides. Migma designs, stores brand rules, holds your audience, and sends only after you approve. Connect once with browser OAuth, then run the full marketing loop in plain language. This is a Migma product guide, current as of August 19, 2026.

​
Why ChatGPT alone is not enough

A ChatGPT 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. ChatGPT stays the place where you plan and ask.

​
Connect ChatGPT to Migma

  1. In ChatGPT, add a custom MCP connection (developer mode or workspace admin settings, depending on your plan).
  2. Use this URL only:
  1. ChatGPT opens Migma in the browser. Sign in, review permissions, then approve. email:send is destructive send access (test and live mail). Allow it only if you trust ChatGPT to send for you.
  2. Do not paste an API key into ChatGPT. Migma creates a scoped connection key automatically. Revoke it anytime from Settings → Developers → API Keys.
Setup details: ChatGPT · MCP Server.

​
First ask

Ask:
If tools are missing or look stale, reconnect the MCP connector and confirm custom MCP is enabled for your workspace.

​
The marketing loop

1

Pick a brand

Ask ChatGPT to list brands and choose one. Every later tool call needs that brand. If ChatGPT asks for a project id, that is the brand handle for the API.
2

Save lasting brand facts

When you share tone, products, offers, policies, or FAQ that should stick, say so once. ChatGPT should call migma_add_knowledge_base without listing first. Those facts improve later emails.
3

Design emails (show drafts first)

Ask for one email or a short series. ChatGPT should generate, wait until ready, then show preview images and each canvas link immediately. Do not let it run compatibility, deliverability, or spam checks before you have seen the drafts.
4

Import or build the audience

Upload or paste a contact CSV and name the list. ChatGPT should call migma_create_contact_import once with the full CSV text and an optional list tag. Prefer that over converting rows to JSON. Or ask it to create a segment from existing contacts.
5

Optional checks, then campaign

After you like a draft, ask for inbox checks or a small edit. Then create a campaign draft with subject, sender, and recipients (list or segment). Ask before any live send or schedule.
6

Read results

After send, ask for campaign stats and delivery logs. Fix the next brief from what worked.

​
Prompts worth saving

​
Design one email

​
Design a series

​
Import a CSV list

​
Launch a campaign (approval gate)

​
After you approve

​
Read performance

​
What ChatGPT should and should not do

​
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 blast.
  • Keep a human in the loop: claims, audience, sender, and timing are your call.

​
When to use what

  • ChatGPT + Migma: plan, design, import lists, and launch from one conversation.
  • Migma web app: visual control on the canvas without connector setup.
  • Claude + Migma: same loop in Claude, plus optional Claude design .zip import.
  • API, SDK, or CLI: automation and CI.

​
Next

ChatGPT setup

Connect ChatGPT with browser OAuth.

MCP Server

Tool workflows: design, CSV, knowledge base.

Send a campaign

Recipients, sender, schedule in the app.

Manage contacts

CSV import and audience lists.