Cursor

Use Migma MCP in Cursor when you want an agent to prepare emails, review campaigns, manage contacts, or export approved work without leaving your editor.

Option 1: Remote MCP

Use Remote MCP when Cursor supports Streamable HTTP servers with headers.

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

Add this to project-level .cursor/mcp.json or global Cursor MCP settings.

Option 2: Local MCP

Use Local MCP when your Cursor setup cannot send remote headers.

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

Verify

Restart Cursor, then ask:

Use Migma to list my brands, then tell me which brand IDs are available.

If Cursor returns projectId is required, ask it to call migma_list_projects first and pass projectId to the next tool call.

MCP Server

Remote and local MCP details.

Agent Registration

Let Cursor request a scoped key without copy-paste.

MCP Server Claude

⌘I

Getting Started

Tools

MCP Clients

AI App Builders

Agent Access

Option 1: Remote MCP

Option 2: Local MCP

Verify

Next

MCP Server

Agent Registration

​Option 1: Remote MCP

​Option 2: Local MCP

​Verify

​Next

MCP Server

Agent Registration

Option 1: Remote MCP

Option 2: Local MCP

Verify

Next