remnawave-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMNAWAVE_API_KEY | No | API key for Caddy reverse proxy authentication | |
| REMNAWAVE_BASE_URL | Yes | Panel URL (e.g. https://vpn.example.com) | |
| REMNAWAVE_READONLY | No | Set to 'true' to enable readonly mode | |
| REMNAWAVE_API_TOKEN | Yes | API token from panel settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| users_listB | List all Remnawave VPN users with pagination |
| users_getC | Get a specific Remnawave user by their UUID |
| users_get_by_usernameC | Get a Remnawave user by their username |
| users_get_by_short_uuidB | Get a Remnawave user by their short UUID |
| users_createC | Create a new VPN user in Remnawave |
| users_updateC | Update an existing Remnawave user |
| users_deleteB | Permanently delete a Remnawave user |
| users_enableB | Enable a disabled Remnawave user (restore VPN access) |
| users_disableA | Disable a Remnawave user (block VPN access) |
| users_revoke_subscriptionC | Revoke subscription for a Remnawave user (generates new subscription link) |
| users_reset_trafficC | Reset traffic counter for a Remnawave user |
| nodes_listB | List all Remnawave nodes |
| nodes_getC | Get a specific node by UUID |
| nodes_createC | Create a new node in Remnawave |
| nodes_updateC | Update an existing node |
| nodes_deleteB | Delete a node from Remnawave |
| nodes_enableC | Enable a disabled node |
| nodes_disableC | Disable a node |
| nodes_restartC | Restart a specific node |
| nodes_restart_allB | Restart all nodes |
| nodes_reset_trafficC | Reset traffic counter for a node |
| nodes_reorderC | Reorder nodes by providing an ordered array of UUIDs |
| hosts_listB | List all Remnawave hosts |
| hosts_getC | Get a specific host by UUID |
| hosts_createC | Create a new host in Remnawave |
| hosts_updateC | Update an existing host |
| hosts_deleteC | Delete a host from Remnawave |
| system_statsB | Get overall Remnawave panel statistics (users, nodes, traffic, memory, CPU) |
| system_bandwidth_statsC | Get bandwidth statistics |
| system_nodes_metricsC | Get detailed node metrics |
| system_nodes_statisticsC | Get node statistics |
| system_healthB | Check Remnawave panel health status |
| system_metadataB | Get Remnawave panel metadata and version information |
| system_generate_x25519B | Generate X25519 key pair for VLESS Reality |
| auth_statusB | Check current authentication status with Remnawave panel |
| subscriptions_listC | List all subscriptions with pagination |
| subscriptions_get_by_uuidC | Get subscription details by UUID |
| subscriptions_get_by_usernameC | Get subscription details by username |
| subscriptions_get_by_short_uuidC | Get subscription details by short UUID |
| subscription_infoC | Get subscription info by short UUID (public endpoint) |
| config_profiles_listB | List all config profiles |
| inbounds_listB | List all inbounds from all config profiles |
| squads_listB | List all internal squads |
| squads_createC | Create a new internal squad |
| squads_updateC | Update an internal squad |
| squads_deleteB | Delete an internal squad |
| squads_add_usersC | Add users to an internal squad |
| squads_remove_usersC | Remove users from an internal squad |
| hwid_devices_listC | List HWID devices for a specific user |
| hwid_device_deleteC | Delete a specific HWID device |
| hwid_devices_delete_allC | Delete all HWID devices for a user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_user_wizard | Step-by-step guide to create a new VPN user |
| node_diagnostics | Diagnose issues with a specific node |
| traffic_report | Generate a traffic usage report |
| user_audit | Complete audit of a specific user |
| bulk_user_cleanup | Find and manage expired or inactive users |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| panel-stats | Current Remnawave panel statistics (users, nodes, traffic, system) |
| panel-nodes | Status of all Remnawave nodes (online/offline, traffic) |
| panel-health | Remnawave panel health check |
TDQS
Scored across 51 tools
Most tools have distinct purposes targeting specific resources like hosts, nodes, users, subscriptions, and system operations, with clear action distinctions (e.g., create, delete, list). However, some overlap exists, such as 'subscription_info' and 'subscriptions_get_by_short_uuid' which both retrieve subscription details by short UUID, potentially causing confusion. Overall, descriptions help clarify boundaries, but a few tools could be misselected due to similar functions.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'hosts_list', 'nodes_create', and 'users_update'. All tools use snake_case uniformly, with verbs like 'create', 'delete', 'list', and 'get' applied predictably across resources. This consistency makes the tool set easy to navigate and understand at a glance.
With 51 tools, the count is excessive for the Remnawave panel management domain, leading to a heavy and potentially overwhelming interface. While the tools cover various resources like hosts, nodes, users, and subscriptions, many operations (e.g., multiple 'get' methods for subscriptions) could be consolidated. This high number suggests over-fragmentation rather than a well-scoped set, making it harder for agents to manage efficiently.
The tool set provides comprehensive CRUD and lifecycle coverage for the Remnawave panel domain, including resources like hosts, nodes, users, subscriptions, squads, and system operations. It supports full management workflows with actions such as create, read, update, delete, enable/disable, restart, and traffic reset. No obvious gaps are present; agents can perform all essential operations without dead ends.