ReplyAtlas

What ReplyAtlas MCP server does

ReplyAtlas MCP server exposes ReplyAtlas account operations to MCP-compatible assistants. It is designed for Instagram engagement workflows, including automations that respond to keyword comments with direct messages on posts, Reels, Lives, or story replies.

The available operations cover five main areas:

• Account details and connected Instagram accounts
• Automation creation, inspection, editing, and deletion
• Lead lookup, tagging, and export
• Dashboard, analytics, and direct-message logs
• Conversations and broadcast management

The ReplyAtlas MCP server works against the ReplyAtlas REST API rather than connecting directly to Instagram. ReplyAtlas uses Instagram’s official API for the underlying comment-to-DM behavior.

How it works

An MCP client starts the package with npx, and the server authenticates to ReplyAtlas using an API key. At startup, it checks the key through the account endpoint. Invalid credentials, or an account plan without API access, cause the process to exit with an explanatory error.

Operations that can contact real people are deliberately split into two calls. A conversation reply or broadcast first produces a preview and a confirmation token. The assistant must submit that token in a follow-up call before ReplyAtlas sends the message. Read-only requests and account management actions do not use this confirmation flow.

The server communicates with ReplyAtlas over HTTPS. It does not receive or store an Instagram password or Instagram access tokens.

Setup and configuration

A ReplyAtlas plan with API access is required. Create an API key from ReplyAtlas settings, then provide it to the MCP client as REPLYATLAS_API_KEY. The key is required and uses the mf_live_... format.

Node.js 18 or newer is needed to run the package. No separate installation is required when the client launches it with npx -y replyatlas-mcp.

The optional REPLYATLAS_BASE_URL variable changes the API host from its default of https://replyatlas.com. This can be useful when the API endpoint needs to be overridden, but the material does not specify additional hosts or deployment modes.

Claude Desktop and Cursor can load the server through their MCP configuration files. Claude Code can add it with claude mcp add, passing the API key as an environment setting.

Tools and capabilities

ReplyAtlas MCP server provides the following tool groups:

• 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: list_conversations, reply_to_conversation
• Broadcasts: list_broadcasts, create_broadcast, send_broadcast

These tools support tasks such as creating a keyword-triggered guide delivery flow, finding recent leads, adding tags, exporting a lead set, reviewing performance data, replying to a conversation, or preparing and sending a broadcast.

Limitations and notes

API access depends on the ReplyAtlas plan; having an account alone is not sufficient. The server manages ReplyAtlas resources and does not provide direct Instagram credential management. Sending replies and broadcasts is not immediate: each requires a preview followed by confirmation with the returned token.

The documented package workflow uses Node.js 18+, npx, and an MCP client. The repository also includes development commands for installing dependencies, running Vitest tests, and building the TypeScript package, but those commands are not needed for normal client configuration.