mcp-remnawave
Related Servers
Alternatives to mcp-remnawave
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables Claude Desktop, Cursor, and other MCP clients to inspect a Remnawave 3.x panel through natural-language chat, covering users, nodes, traffic, devices, connections, and GeoCheck, with tools generated from the official backend contract to match the panel version. Read-only by default and privacy-filtered, so secrets, keys, and client identifiers are hidden or replaced with aliases before reaching the chat.856 npm4MIT
- 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
- AlicenseAqualityBmaintenanceMCP server for Remnawave panel API. Manage VPN users, nodes, hosts, and system stats from Claude Code or any MCP-compatible client.341MIT
- AlicenseCqualityCmaintenanceEnables 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.2226 npmMIT
- AlicenseCqualityBmaintenanceEnables managing a Remnawave VPN panel from MCP clients, providing tools for users, nodes, subscriptions, statistics, billing, and system operations, plus resources and prompts for common admin tasks.1906 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.15 npmMIT
TDQS
Scored across 204 tools
Tools are generally named by resource and action, but several overlapping getters/resolvers exist (e.g., users_get, users_get_by_username, users_get_by_short_uuid, users_resolve; multiple subscription getters; generic nodes_bulk_actions vs specific bulk tools). The sheer number of closely related bulk and stats tools creates selection friction, though descriptions usually clarify intent.
Names predominantly follow a snake_case resource_action pattern (users_list, nodes_create, hosts_update). Minor inconsistencies appear in singular/plural prefixes and special cases like api_request, auth_status, keygen_get, subscription_info, and metadata_node_get vs nodes_get.
204 tools is an extreme mismatch for an MCP server; even a comprehensive panel API can be exposed more compactly. This volume makes tool selection impractical and exceeds any reasonable agent context.
The surface covers the full Remnawave domain: users, nodes, hosts, config profiles, squads, subscriptions, templates, plugins, shared lists, billing, stats, and more, with CRUD and bulk operations. A raw api_request fallback further covers any unlisted endpoints, so no obvious gaps remain.