Skip to main content
Glama
3APA3A-3AHO3A

remnawave-mcp

by 3APA3A-3AHO3A
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to remnawave-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-remnawave

      Maaagiic
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients like Claude Code, Claude Desktop, or Cursor to read and manage Remnawave 3.x VPN panel resources — users, nodes, hosts, config profiles, squads, subscription templates, billing, and HWID devices — through the panel's REST API, with contract-driven tool schemas, numeric user IDs, multi-panel config lookup, and an optional readonly mode.
      13 npm
      MIT

    • remnawave-mcp

      Alex0neS
      A
      license
      C
      quality
      C
      maintenance
      Enables AI clients to drive the full Remnawave panel API, exposing one tool per method+path operation (users, nodes, hosts, subscriptions, inbound, bulk actions) plus search, describe, status, audit and metrics helpers. Read-only/read-write gating, deny rules, confirm-preview and dry-run, response secret redaction and an audit journal keep mutations controlled.
      222
      13 npm
      MIT
    • Kaidn-mcp by Kaidn-io

      Kaidn-mcpofficial

      Kaidn-io
      A
      license
      A
      quality
      B
      maintenance
      Investigate fraud directly from Claude, Cursor, or any MCP-compatible client. Analyze suspicious activity with clear, evidence-backed verdicts. Pivot from a single signup to every account sharing the same device, IP address, or email inbox. Check entities against a cross-operator abuse network, review linked accounts, and efficiently process your fraud review queue. Read-only by default, with no r
      10
      99 npm
      MIT
    • IcePanel MCP Server by IcePanel

      IcePanel MCP Serverofficial

      IcePanel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with IcePanel for architectural diagram management via MCP clients, such as Claude Desktop, Cursor, and Windsurf. Deprecated in favor of a remote MCP server.
      59 npm
      15
      MIT
    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

    C2.6/5.0

    Scored across 86 tools

    Disambiguation3/5

    The tool set contains many closely related read endpoints, such as multiple subscription lookups by different identifiers and numerous stats/usage tools (e.g., get_stats, get_bandwidth_stats, get_stats_digest, get_node_usage). Descriptions are detailed and help distinguish some tools, but an agent still faces ambiguity in selecting the right one for a given query.

    Naming Consistency4/5

    Most tools follow a consistent snake_case pattern with a get_ prefix for read operations. A few custom tools (user_report, panel_overview, find_user, geocheck_node) deviate slightly, but the overall naming is predictable and readable.

    Tool Count1/5

    With 86 tools, the server is far beyond a well-scoped size (typically 3–15). Many are thin wrappers around individual API endpoints, which creates an overwhelming and hard-to-navigate surface.

    Completeness2/5

    The tool set is almost entirely read-only (GET endpoints), with no create, update, or delete operations for users, nodes, subscriptions, or other core resources. For a panel management server, this is a significant gap that will prevent agents from performing lifecycle tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources