Integration · Claude & Cursor · Pro

Run your Instagram automation from Claude.

The ReplyAtlas MCP server connects your account to Claude Desktop, Cursor, and any Model Context Protocol client. Ask your assistant to spin up a comment-to-DM automation, pull this week's lead list, or check DM analytics — it calls the ReplyAtlas API directly. No code — npx and go.

Setup · ~2 minutesModel Context ProtocolNo Zapier required
What syncs where

Your MCP client runs `npx -y replyatlas-mcp` locally and authenticates with a ReplyAtlas API key you mint in Settings. It exposes 18 tools across six groups — account, automations, leads, analytics, conversations, and broadcasts — each mapping to the same /api/v1/* REST endpoints the public API uses. Send actions (replying to a DM, firing a broadcast) are two-step: the assistant previews first, then confirms with a token, so nothing goes out by accident.

How it works

Four steps. ~2 minutes.

  1. 1. Be on Pro (or Pro+)

    MCP access rides on the same API_ACCESS feature as the public REST API — available on Pro and Pro+. Free, Starter, and Growth plans can't mint an API key, so the server will refuse to start with a clear message.

  2. 2. Mint an API key

    In ReplyAtlas → Settings → API Keys, create a key. You'll see the mf_live_… value once — copy it. That's your REPLYATLAS_API_KEY.

  3. 3. Add the server to your client

    Drop a small JSON block into claude_desktop_config.json (Claude Desktop) or ~/.cursor/mcp.json (Cursor): command npx, args ['-y','replyatlas-mcp'], and your key in env. The full copy-paste config lives on the /docs page.

  4. 4. Restart and ask

    Restart the client, then ask 'list my ReplyAtlas automations' or 'create a comment-to-DM automation on my latest Reel for the keyword LINK'. The assistant calls the tools and reports back.

What teams use this for

Four common patterns.

Authoring

Build automations by describing them

Instead of clicking through the wizard, tell Claude 'DM everyone who comments INFO on my latest post with my link'. It calls create_automation with the right trigger, keywords, and template.

Reporting

Ask for the numbers in plain English

'How many DMs went out this week and what's my reply rate?' pulls get_dashboard and get_analytics and summarises. No exporting CSVs, no dashboard hunting.

Lead ops

Query and tag leads conversationally

'Show me leads from the summer-launch automation and tag the ones who clicked as hot.' That's list_leads plus tag_lead, driven straight from chat.

Inbox

Draft and send replies with a safety net

reply_to_conversation and send_broadcast are two-step — the assistant shows exactly what it'll send and waits for a confirm token before anything leaves your account.

FAQ

Questions about the Claude & Cursor integration

The Model Context Protocol is an open standard for connecting AI assistants to external tools and data. ReplyAtlas ships an MCP server so clients like Claude Desktop and Cursor can operate your account directly — with your permission and your own API key.

Connect Claude & Cursor in ~2 minutes.

Free Starter plan, 1,000 DMs/month. Upgrade to Pro when you want this integration on.