Skip to main content
Use /setup when you want an AI coding agent to add Migma to an existing app. It is agent-guided. The agent still reviews and edits your codebase, then uses Migma to create or reuse emails and wire safe server-side sends.

​
Documentation Index

Fetch the complete documentation index at: https://docs.migma.ai/llms.txt Use this file to discover all available pages before exploring further.

​
Install

​
CLI and skills

curl -fsSL https://raw.githubusercontent.com/MigmaAI/migma-cli/main/setup.sh | sh
Or install each part: 
curl -fsSL https://raw.githubusercontent.com/MigmaAI/migma-cli/main/install.sh | sh
curl -fsSL https://raw.githubusercontent.com/MigmaAI/migma-skills/main/install.sh | sh

​
Plugin

Add the marketplace once, then install the Migma plugin in your agent.
https://mintcdn.com/migmaai/QHH_kDlhE97DvfUZ/images/logos/claude-color.svg?fit=max&auto=format&n=QHH_kDlhE97DvfUZ&q=85&s=87dfd67137723cac140274a92b596a9c

Claude Code

claude plugin marketplace add MigmaAI/migma-skills
claude plugin install migma@migma-plugins
https://mintcdn.com/migmaai/QHH_kDlhE97DvfUZ/images/logos/openai.svg?fit=max&auto=format&n=QHH_kDlhE97DvfUZ&q=85&s=acbaf5092a31aafd865b5c726ce593ff

Codex

codex plugin marketplace add MigmaAI/migma-skills
codex plugin add migma@migma-plugins
https://mintcdn.com/migmaai/QHH_kDlhE97DvfUZ/images/logos/cursor.svg?fit=max&auto=format&n=QHH_kDlhE97DvfUZ&q=85&s=b3faa266343083f847bbdf001ce1c506

Cursor

Open Settings, go to Plugins, paste https://github.com/MigmaAI/migma-skills, then install Migma.

​
Skill fallback

npx skills add MigmaAI/migma-skills --skill setup

​
What setup does

  1. Audits existing email providers, templates, receipts, invites, campaigns, lifecycle jobs, queues, and webhooks.
  2. Resolves the correct Migma brand/project.
  3. Lists existing Migma emails and reuses matches.
  4. Creates missing emails with prompts grounded in trigger files, recipients, variables, subject copy, and CTAs.
  5. Stores each returned emailId, subject, sender, and matching app trigger in server-side config or constants.
  6. Wires sends only in trusted backend paths.
  7. Adds a dry-run or smoke test that verifies each trigger selects the right emailId without sending duplicates.

​
API access

Use a Migma API key server-side: 
MIGMA_API_KEY=<set outside chat>
MIGMA_FROM=hello@brand.migma.email
MIGMA_FROM_NAME=Brand
Get a key from Settings → API Integration → API Keys, or let the agent use agent registration at https://api.migma.ai/auth.md.

​
REST fallback

If plugin or skill install is unavailable, use REST.
TaskEndpoint
List brands/projectsGET /v1/projects
List existing emailsGET /v1/projects/emails?projectId=<projectId>
Create emailsPOST /v1/projects/emails/generate
Poll generationGET /v1/projects/emails/{conversationId}/status
Fetch one emailGET /v1/emails/{emailId}
SendPOST /v1/sending
Base URL: https://api.migma.ai Auth header: Authorization: Bearer $MIGMA_API_KEY

​
Guardrails

  • Keep API keys and send calls server-side.
  • Do not put Migma secrets in browser code.
  • Ask before installing packages, calling Migma APIs, creating emails, or sending tests.
  • Test before live sends.
  • Add idempotency before transactional sends.
  • Do not send cold email or email unsubscribed contacts.
  • If the app is frontend-only, stop after audit/email creation and add a backend prerequisite before wiring sends.

​
Which tool to use

SurfaceUse it for
setup skillApp audit, email mapping, backend send wiring
Migma pluginPackaging setup, migma, and public API guidance for agents
CLITerminal workflows: generate, fetch, edit, send-test, send, campaign, export
MCPMigma-side actions from MCP clients: list, generate, fetch, edit, send, campaign
REST or SDKProduction app integration
Related docs: Skills, CLI, MCP, Authentication, Agent registration.