replyatlas-mcp
Related Servers
Alternatives to replyatlas-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables sending text, photo, and video Instagram Direct Messages and managing chats, messages, media downloads, users, stories, followers, following, posts, and likes through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceExposes Instagram actions (posts, media, comments, DMs, insights, Messenger profile) to Claude and ChatGPT via MCP.MIT
- AlicenseBqualityAmaintenanceConnects an MCP-compatible agent to a real Instagram, WhatsApp, or Messenger inbox, exposing 29 tools, 11 playbook prompts, and 2 resources for reading and writing conversations, messages, contacts, templates, journeys, campaigns, comments, and tickets. Includes guided zero-key setup, plan recommendation, and destructive-action hints so cautious agents can confirm state-changing operations.31229 npmMIT
- AlicenseAqualityCmaintenanceEnables publishing photos, reels, and stories to Instagram, reading and moderating comments, fetching performance insights, drafting captions via MCP sampling, and scheduling reels for later.1314 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage a Meta-linked Instagram professional account, including comments, replies, and messages, using Meta's official APIs with deterministic permissions and audit state.MIT
TDQS
Scored across 20 tools
Each tool maps to a distinct resource+action (automations, leads, tags, broadcasts, conversations, logs), and descriptions carefully clarify boundaries. The main risk is get_dashboard vs get_analytics, which both cover reporting and could be confused, and list_dm_logs vs list_conversations overlap slightly around messaging history.
All 20 tools follow a strict snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, send_*, export_*, reply_to_*, tag_lead). Resource naming is predictable and the verb set is used consistently across resources.
20 tools is on the heavier side but justified by a broad SaaS domain spanning automations, leads, analytics, DM logs, inbox conversations, and broadcasts. Each tool maps to a real operation rather than padding, though it sits near the upper bound of reasonable.
Automations get full CRUD and leads/broadcasts/conversations cover core lifecycle flows. Minor gaps remain: no create_tag (tag_lead explicitly cannot create tags), no get_broadcast/update_broadcast/delete_broadcast, and leads are read-only, but these are workable for the primary workflows.