Connect AI Agents with the Migma MCP Server

​

Where this lives in Migma

​

Choose connection type

​

Remote MCP

​

Recommended: OAuth connector setup

1. Add Migma as a custom connector with https://migma.ai/mcp.
2. Follow the client sign-in flow. It opens Migma so you can review and approve access.
3. On migma.ai/connect/authorize, check the app name, return host, and requested scopes. email:send permits test/direct sends. campaign:write permits campaign creation, send, and schedule. Migma marks both as delivery access.
4. Approve the connection. Migma gives the client a scoped API key automatically, so there is no key to copy or paste.

​

Claim-code fallback

​

CI and server automation

{
  "mcpServers": {
    "migma": {
      "url": "https://migma.ai/mcp",
      "headers": {
        "Authorization": "Bearer your_migma_api_key"
      }
    }
  }
}

​

Local MCP

{
  "mcpServers": {
    "migma": {
      "command": "npx",
      "args": ["-y", "@migma/mcp"],
      "env": {
        "MIGMA_API_KEY": "your_migma_api_key"
      }
    }
  }
}

export MIGMA_PROJECT_ID=proj_abc123

claude mcp add --scope user migma -- npx -y @migma/mcp
claude mcp list
claude mcp get migma
claude mcp remove migma

​

Client setup

Cursor

Add Migma MCP to Cursor.

Claude

Connect Claude.ai, Claude Code, or Claude Desktop. Visual setup: Claude tutorial.

ChatGPT

Use the public Migma plugin. Visual setup: ChatGPT tutorial.

Grok

Ask Grok Bot to add Migma Remote MCP, or connect Grok web and Grok Build directly.

Copilot

Connect GitHub Copilot to Migma MCP.

Codex CLI

Add Migma MCP to Codex CLI.

Windsurf

Connect Migma MCP to Windsurf.

Antigravity

Add Migma MCP to Google Antigravity.

Raycast

Use Migma MCP from Raycast AI.

VS Code

Connect Migma MCP to VS Code.

​

Verify the connection

​

Common workflows

​

Design emails (show drafts first)

1. List brands and choose projectId.
2. For researched work, build an exact source-backed fact checklist. Pass required facts in the prompt and up to five public HTTPS source-image URLs through structured images; prompt-only URLs are not image inputs.
3. Create or design with one migma_generate_email call (load that tool by exact name). For several emails pass count (max 12) and name each email’s job in the prompt. Do not call generate once per email. Then poll migma_get_generation_status. Existing HTML or .eml uses migma_import_html instead of generate.
4. Show returned preview images and each canvas link immediately.
5. After first show, verify every required fact and source image before claiming success. If a preview cannot be attached, show its canvas link and say visual verification is incomplete.
6. Only then offer edits, inbox checks, or a campaign. Do not run validate or edit tools before that first show. Text-only edit cannot add structured source images; that requires replacement generation.
7. Run migma_validate_* when the user asks for checks, or as a last step before send.

​

Convert existing HTML

1. List brands and choose projectId.
2. Call migma_import_html once with the HTML or .eml source (or htmls for several files). Optional instruction: keep it as-is, or apply the brand.
3. Poll migma_get_generation_status, then show preview images and each canvas link.
4. Each result is one canvas slot with its own emailId. Edit, send, and export use that id.

​

Save brand facts

• Call migma_add_knowledge_base when the user shares lasting facts (tone, products, offers, policies). Do not list first.

​

Import a CSV audience

• Call migma_create_contact_import once with the full CSV text and an optional list tag.
• Leave column mapping empty when headers look like email, first name, or last name.
• Prefer this over converting CSV rows into a JSON bulk import.
• The import can wait and return final counts in the same turn.

​

Out of credits

• On an out-of-credits error, call migma_get_credits to show the plan and remaining credits.
• Call migma_get_upgrade_link and show the returned URL. The user opens it and pays in the browser. The tool call itself charges nothing.

​

Buy a domain

1. Search availability and yearly prices with migma_search_buyable_domains.
2. Call migma_buy_domain and show the returned checkout URL. The user pays in the browser. Buying needs a paid Migma plan, so offer an upgrade link if the account does not have one.
3. Poll migma_get_domain_purchases until the domain is active.
4. Set it up for sending with migma_setup_domain.

​

Other

• Open the email in Migma from the returned canvas link
• Fetch exact emailId values
• Send a test email (ask before any live send)
• Create a campaign draft
• Export approved email to HTML, PNG, PDF, Klaviyo, Mailchimp, or HubSpot
• Read campaign metrics and logs
• Manage contacts, lists, segments, and sending domains
• Check the plan and remaining credits, and get an upgrade link (migma_get_credits, migma_get_upgrade_link)
• Search, buy, and track domains (migma_search_buyable_domains, migma_buy_domain, migma_get_domain_purchases); payment happens in the user’s browser
• Manage DNS records on domains bought in Migma (migma_list_dns_records, migma_add_dns_record, migma_remove_dns_record): add A, AAAA, CNAME, MX, TXT, or NS records like Google Workspace MX or a site-verification TXT, and remove user-added records. Migma’s email sending records are protected, and the root and www names are reserved for domain forwarding

​

Security

• Prefer OAuth connection for clients that support it.
• Use scoped API keys.
• Review scopes before approval. email:send allows test/direct sends. campaign:write allows campaign creation, send, and schedule. Only allow either when you trust the connector to deliver mail.
• Revoke OAuth-created and manually created keys from Settings → Developers → API Keys.
• Keep human approval enabled before sends, exports, audience changes, and campaign changes.
• Send API keys through the documented authorization header.
• Treat MCP like direct API access. Tool calls use the same Migma permissions as SDK, CLI, and REST API requests.

​

Troubleshooting

​

Resources