Manage Instagram comment-to-DM automations, leads, analytics, conversations and broadcasts.
Manage your ReplyAtlas account from Claude, Cursor or any Model Context Protocol client: Instagram comment-to-DM automations, leads, analytics, conversations and broadcasts.
ReplyAtlas auto-sends an Instagram DM to anyone who comments a keyword on your posts, Reels, Lives or story replies, using Instagram's official API. This server lets an AI assistant run that account for you: "create an automation that DMs my free guide to everyone who comments GUIDE", "who were my hottest leads this week?", "export leads tagged webinar".
Requires a ReplyAtlas plan with API access. Create an API key in ReplyAtlas → Settings → API Keys.
No install needed. Your MCP client runs it with npx (Node.js 18+).
claude_desktop_config.json){
"mcpServers": {
"replyatlas": {
"command": "npx",
"args": ["-y", "replyatlas-mcp"],
"env": { "REPLYATLAS_API_KEY": "mf_live_your_key_here" }
}
}
}
~/.cursor/mcp.json){
"mcpServers": {
"replyatlas": {
"command": "npx",
"args": ["-y", "replyatlas-mcp"],
"env": { "REPLYATLAS_API_KEY": "mf_live_your_key_here" }
}
}
}
claude mcp add replyatlas -e REPLYATLAS_API_KEY=mf_live_your_key_here -- npx -y replyatlas-mcp
| Env var | Required | Default | Notes |
|---|---|---|---|
REPLYATLAS_API_KEY | yes | — | Your mf_live_… API key. |
REPLYATLAS_BASE_URL | no | https://replyatlas.com | Override the API host. |
On start the server calls /api/v1/me to check the key and exits with a clear
message if the key is invalid or the plan has no API access.
| Area | 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 | list_conversations, reply_to_conversation |
| Broadcasts | list_broadcasts, create_broadcast, send_broadcast |
Anything that messages real people is two-step. reply_to_conversation and
send_broadcast first return a preview and a confirmToken; nothing is sent
until the tool is called again with that token. The server only talks to the
ReplyAtlas REST API over HTTPS with your API key. It never sees your Instagram
password or tokens.
pnpm install
pnpm test # vitest
pnpm build # tsup → dist/index.js
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y replyatlas-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ashishdesai0592-replyatlas": {
"command": "npx",
"args": [
"-y",
"replyatlas-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencereplyatlas-mcpnpmReplyAtlas works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.