Skip to main content
Use this page when an IT or security reviewer is deciding whether to approve Migma as a custom MCP connector in ChatGPT, Claude, or another MCP client. This is not a setup guide. For connection steps, see ChatGPT, Claude, or MCP Server.

​
What Migma MCP does

Migma is an AI email marketer. The hosted MCP server lets a signed-in person use ChatGPT, Claude, or another MCP client to work in their Migma account. With an approved connection, the client can:
  • Prepare on-brand email drafts and show previews
  • Import contacts and manage lists or segments
  • Save lasting brand facts
  • Prepare campaign drafts and read campaign stats
  • Export reviewed emails to HTML or connected tools such as Klaviyo, Mailchimp, or HubSpot
  • Send test or live email only when send permission is granted
Migma is for permission-based email, not cold outreach. See Sending rules.

​
How sign-in works

Hosted MCP URL:
Add only that URL. The client opens Migma in the browser. A signed-in Migma user reviews the app name, return host, and requested permissions, then approves or denies access at migma.ai/connect/authorize. Hosted MCP does not ask you to paste an API key. After approval, Migma creates a connection key automatically. That key appears in Settings → Developers → API Keys. Hosted sign-in usually requests the full Migma API permission set so the client can use the matching tools. email:send is highlighted as destructive send access (test and live mail). Deny the connection if your policy does not allow this client to send. ChatGPT, Claude, and similar products may also require a workspace admin to allow custom MCP connectors. That is the client’s policy. Migma still requires a signed-in Migma user to consent before the connector can call Migma.

​
Permissions

MCP uses the same permission names as the Migma API. A granted permission allows the matching API actions, not extra access. Full list: Authentication.
email:send allows test and live sends through the connected account. campaign:write can also send or schedule campaigns. Only allow those permissions if you trust this client to send for you.

​
Data and access

  • The connection has the same reach as a Migma API key with those permissions. Treat MCP like direct API access, not a separate broader integration.
  • It can act on brands in the signed-in Migma account. API and data contracts use project / projectId for a brand.
  • Migma returns the account data or action result needed for each tool call. Authentication tokens are not included in normal tool results.
  • The MCP client (for example ChatGPT or Claude) processes conversation text and tool inputs or results under that vendor’s terms. See Privacy Policy.
  • Send, campaign, export, and audience-changing tools are marked as writes or as destructive. Clients that honor those hints typically ask the person before running them. Still treat a granted email:send as send capability.
  • Keep a human in the loop before live sends, exports, audience changes, and campaign sends.
  • Sending through Migma must follow acceptable use and sending rules.

​
Revoke access

  1. Open migma.ai and go to Settings → Developers → API Keys.
  2. Find the key created for the ChatGPT, Claude, or other MCP connection.
  3. Delete the key and confirm.
Revoking invalidates that key. Reconnect or restart the MCP client so it stops using the old connection.

ChatGPT setup

Add Migma as a custom ChatGPT MCP connector.

Claude setup

Connect Claude.ai, Claude Code, or Claude Desktop.

MCP Server

Hosted and local MCP connection details.

Security & compliance

SOC 2, GDPR, and email-law guidance.

Sending rules

Permission-based email. No cold outreach.

Authentication

API permissions and how to revoke keys.