postengage-mcp

Manage your PostEngage Instagram comment & DM automations from Claude, Cursor, or any MCP client.

List, pause, resume and draft automations, and read your runs and leads — without leaving the tool you already work in.

Setup

1. Create an API key at app.postengage.ai/settings/developer. It is shown once — copy it.
2. Connect your client.

Claude Code

claude mcp add postengage -- npx -y postengage-mcp

Set POSTENGAGE_API_KEY in its environment.

Claude Desktop / Cursor — add to the MCP config:

{
  "mcpServers": {
    "postengage": {
      "command": "npx",
      "args": ["-y", "postengage-mcp"],
      "env": { "POSTENGAGE_API_KEY": "pe_live_…" }
    }
  }
}

Tools

| Tool | What it does | | ------------------- | --------------------------------------------------------------------- | | list_automations | Every rule, with status and counts | | get_automation | One rule in full, including its definition | | list_runs | An automation's recent runs, with the reason each did or did not send | | list_leads | Leads captured from conversations | | account_status | Connected accounts, plan and credit balance | | pause_automation | Stop a rule replying (reversible) | | resume_automation | Turn a rule live | | create_automation | Create a draft rule (never live) |

Security

A key reads and runs automations. It cannot delete anything, change billing, touch your login, or make another key — those stay behind a browser sign-in, so a leaked key's worst case is a paused rule, revocable in one click. Only the SHA-256 hash of a key is stored server-side; the raw pe_live_… value exists once, in your config.

Configuration

| Env var | Default | | | -------------------- | --------------------------- | ------------------------------------------------ | | POSTENGAGE_API_KEY | — | Required. Your key from Settings → Developer | | POSTENGAGE_API_URL | https://api.postengage.ai | Override for self-host/testing |

License

MIT