Skip to main content
Glama

Related Servers

Alternatives to replyatlas-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables sending text, photo, and video Instagram Direct Messages and managing chats, messages, media downloads, users, stories, followers, following, posts, and likes through MCP tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Instagram actions (posts, media, comments, DMs, insights, Messenger profile) to Claude and ChatGPT via MCP.
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Connects 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.
      31
      229 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables publishing photos, reels, and stories to Instagram, reading and moderating comments, fetching performance insights, drafting captions via MCP sampling, and scheduling reels for later.
      13
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    A3.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues