Skip to main content
Glama
Sign In
replyatlas-mcp

replyatlas-mcp

by ashishdesai0592
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to replyatlas-mcp

No user-submitted related servers found.

    Related Servers

    • Instagram DM MCP server

      camila00740
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables sending Instagram Direct Messages from your account and managing chats, messages, media, users, stories, followers, and related interactions through MCP tools.
      -

    • Instagram DM MCP server

      Somjai873
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables sending Instagram Direct Messages, including text, photos, and videos, while managing DM threads, media, users, stories, followers, and likes through an MCP integration.
      -

    • Instagram DM MCP server

      brooks3255
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables sending direct messages and managing conversations, media, user profiles, stories, followers, and engagement from an Instagram account through MCP tools.
      -

    • Instagram DM MCP server

      viktorcosta291
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to send, retrieve, search, and manage Instagram Direct Messages and related media, threads, users, stories, likes, followers, following, and posts from their Instagram account through MCP tools.
      -

    • Instagram DM MCP server

      IgorReed31
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables sending direct messages, managing chats and media, retrieving user, story, and follower information, and performing engagement actions on Instagram through MCP tools.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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
    ResponsivenessSyncing

    Resources