remnawave-mcp
Related Servers
Alternatives to remnawave-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceWraps the Remnawave panel API into 22 callable tools so AI assistants can manage VPN nodes, users, squads, config profiles, and hosts through natural language instead of manual curl requests. It supports listing, creating, enabling, disabling, restarting, and extending entities, along with traffic resets and node key generation, using credentials supplied via environment variables.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage a Remnawave panel through its full API, covering users, nodes, hosts, subscriptions, and more with configurable tool profiles and read/write token access.19 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables managing 3x-ui panels through their current API, including creating and updating clients across inbounds, monitoring online clients, and accessing panel features like nodes, routing, and backups via runtime-discovered API tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to administrate WHMCS installations through the External API, providing ~50 tools for clients, billing, orders, services, domains, support, and aggregators with safety features and governance.40 npm3ISC
- AlicenseCqualityBmaintenanceWraps the Remnawave API to provide per-operation MCP tools with mutation safety and data redaction, enabling secure interaction with Remnawave panel.100MIT
TDQS
Scored across 222 tools
With 222 tools, many endpoints overlap in purpose (e.g., two internal squad usage tools, offset vs cursor user listing, multiple subscription getters), forcing the agent to read fine-grained descriptions to choose correctly. The controller prefixes help somewhat, but the volume and near-duplicate names make misselection likely.
Names generally follow a resource_action snake_case pattern (users_create_user, nodes_restart_node), but inconsistencies appear: random suffixes like _1r7914, a typo (infra_billing_delte_infra_provider), and mixed get vs get_all conventions. Still, the dominant pattern is readable.
222 tools vastly exceeds a reasonable MCP surface (calibration marks 50+ as extreme mismatch), overwhelming the agent and making navigation costly despite helper tools like api_search.
The surface covers nearly all Remnawave panel domains (users, nodes, hosts, squads, configs, billing, subscriptions, auth, passkeys, metrics, etc.) with full CRUD and bulk operations, leaving few obvious gaps.