ReplyAtlas MCP server: connect Instagram automation to Claude Desktop & Cursor

The replyatlas-mcp server lets an AI assistant operate your ReplyAtlas account through the Model Context Protocol. This guide covers the full install for Claude Desktop and Cursor, the complete tool list, and how to troubleshoot a connection that won't come up.

If you just want the short version, it's one JSON block and an API key. Here's the whole thing, then the details.

Prerequisites

• Node.js installed (the server runs via npx, which ships with Node). Any recent LTS is fine.
• A ReplyAtlas Pro or Pro+ plan. API access — and therefore MCP access — is a Pro feature. On Free, Starter, or Growth you can't create an API key, and the server will exit at startup with a message telling you so.
• An MCP client: Claude Desktop or Cursor (both covered below).

Step 1 — Create your API key

1. Log in to ReplyAtlas and open Settings → API Keys.
2. Click Create key, give it a label like Claude Desktop, and copy the mf_live_… value. It's shown once — if you lose it, revoke it and make a new one.

This key is your REPLYATLAS_API_KEY. It authenticates every request the MCP server makes on your behalf, and you can revoke it any time.

Step 2 — Add the server to your client

Claude Desktop

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "replyatlas": {
      "command": "npx",
      "args": ["-y", "replyatlas-mcp"],
      "env": { "REPLYATLAS_API_KEY": "mf_live_your_key_here" }
    }
  }
}

Save, then fully quit and reopen Claude Desktop.

Cursor

Edit ~/.cursor/mcp.json (or the project-level .cursor/mcp.json):

{
  "mcpServers": {
    "replyatlas": {
      "command": "npx",
      "args": ["-y", "replyatlas-mcp"],
      "env": { "REPLYATLAS_API_KEY": "mf_live_your_key_here" }
    }
  }
}

Reload Cursor. The replyatlas server should appear in your MCP settings with its tools listed.

There is nothing to install manually — npx -y replyatlas-mcp fetches the published package on first run and caches it.

Step 3 — Verify

Ask your assistant: "List my ReplyAtlas Instagram accounts." A correct connection returns your connected handle(s). If you get an auth error, jump to troubleshooting below.

The full tool list

The server exposes 18 tools in six groups:

Group	Tools
Account	get_account, list_ig_accounts
Automations	list_automations, get_automation, create_automation, update_automation, delete_automation
Leads	list_leads, get_lead, list_tags, tag_lead, export_leads
Analytics	get_dashboard, get_analytics, list_dm_logs
Conversations & Broadcasts	list_conversations, reply_to_conversation, list_broadcasts, create_broadcast, send_broadcast

Send safety: reply_to_conversation and send_broadcast are two-step. The first call returns a preview and a confirmToken; the message only sends when a second call includes that token. This stops an assistant from sending DMs without your explicit go-ahead.

Configuration reference

Env var	Required	Default	Notes
REPLYATLAS_API_KEY	Yes	—	Your mf_live_… key from Settings → API Keys.
REPLYATLAS_BASE_URL	No	https://replyatlas.com	Override only if you're pointing at a staging environment.

Troubleshooting

"The server won't start / exits immediately." Most often this is a plan issue — MCP access requires Pro or Pro+. Confirm your plan in Settings → Billing. The startup handshake calls /me; if your plan lacks API access, it stops there with a clear message.

"401 / unauthorized." The API key is wrong, revoked, or has a stray space. Re-copy it from Settings → API Keys, or mint a fresh one.

"npx not found." Node isn't installed or isn't on your PATH. Install a current LTS build of Node.js and restart your client.

"Tools don't appear after editing the config." You need a full restart of the client (quit and reopen), not just a new chat window. Also double-check the JSON is valid — a trailing comma will silently break it.

"It connected but can't see my automations." Make sure the Instagram account you expect is actually connected in ReplyAtlas (Settings → Instagram). list_ig_accounts shows exactly what the key has access to.

Where to go next

• MCP integration overview — what it is and why it's useful, in plain terms.
• API reference (/docs) — every endpoint the tools wrap, with a live "try it" console.
• Manage Instagram DM automation from Claude — real examples of what to ask once you're set up.

Two minutes of setup, and your Instagram automation lives inside the assistant you already use all day. Get started on Pro →