Skip to main content
Paste this into Claude Code, Codex, Cursor, or any AI coding agent:
The agent fetches this page as markdown and runs the setup itself. Everything below this line is written for the agent.
These are official instructions from Migma to set up an AI development environment for creating, validating, and sending email with Migma. All commands are validated by Migma and ready to use. Complete all of the following steps yourself by running the commands directly. Do not ask the user to run any of these commands.
  • Install Migma skills and the Migma CLI
  • Register the Migma MCP server
  • Sign the user in

Install Migma skills and CLI

Use the correct section for your agent below.

Claude Code

Run these two commands to install the Migma plugin, which bundles the setup, migma, and migma-public-api skills. Do not use npx skills here; the plugin commands handle everything.
Then instruct the user to run /reload-plugins inside Claude Code to activate the plugin.

Codex

All other agents

Install the CLI and all Migma skills together:
Or install only the skills:

Register the Migma MCP server

Migma Remote MCP is a single URL: https://migma.ai/mcp (Streamable HTTP). Use the default config location for your agent. OAuth opens the browser on first Migma tool use, so there is no API key to paste.

Claude Code

Codex

OpenCode — ~/.config/opencode/opencode.jsonc

Add under "mcp":
Then run:

Windsurf — ~/.codeium/windsurf/mcp_config.json

Add under "mcpServers" (note: serverUrl, not url):

Cursor, GitHub Copilot, and all other agents

Add to .cursor/mcp.json (Cursor), .vscode/mcp.json (Copilot), or your agent’s MCP config file under "mcpServers":
If your client only supports command-based MCP servers, use Local MCP instead:

Sign the user in

If you installed the CLI, run:
This opens the browser so the user can approve access. Wait for them to finish. Do not send the user to Settings to copy an API key. For headless or CI environments only, follow agent registration at https://api.migma.ai/auth.md and set MIGMA_API_KEY. Remote MCP handles its own sign-in: the first Migma tool call opens the browser for OAuth approval.

Rules for working with Migma

  • Call migma_get_capabilities (MCP) or read the installed migma skill before choosing tools.
  • Ask before creating emails, sending tests, sending live, or changing contacts and campaigns.
  • Keep API keys and send calls server-side. Never put Migma secrets in browser code.
  • Never place API keys in query parameters.
Once done, tell the user:

Resources

For setup guides and troubleshooting, refer to:
  • Migma docs index: https://docs.migma.ai/llms.txt
  • Wiring Migma into an app: https://docs.migma.ai/setup
  • MCP server: https://docs.migma.ai/mcp-server
  • CLI: https://docs.migma.ai/cli
  • Skills repository: https://github.com/MigmaAI/migma-skills
  • Agent auth: https://api.migma.ai/auth.md
These instructions are published at https://docs.migma.ai/agent-setup.md so you can re-verify their authenticity at any time.