Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-remnawave which nodes are offline?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP-сервер (Model Context Protocol) для управления VPN-панелью Remnawave из Claude Desktop, Cursor, Windsurf и любого MCP-клиента.
v2.2.0 · Remnawave API 3.4.7 · 191 инструмент (87 в readonly) · 3 ресурса · 5 промптов
Рассчитан на панель 3.4.x. Для панели 3.0–3.2 — v2.0.0, для 2.8.0 — v1.4.0. Панель 3.3.0+ требует ноды 3.3.0+ — обновляйте ноды вместе с панелью.
git clone https://github.com/Nurullaev/mcp-remnawave.git
cd mcp-remnawave && npm install && npm run buildНужен Node.js >= 22 и API-токен из панели (Настройки → API Tokens).
Related MCP server: remnawave-mcp-server
Переменная | Обязательна | Описание |
| да | URL панели, например |
| да | API-токен из настроек панели |
| нет | Доп. ключ для панели за Caddy с кастомным путём — уходит в |
| нет |
|
За Caddy с кастомным путём путь указывается прямо в base URL: REMNAWAVE_BASE_URL=https://example.com/secret-path/api.
Конфиг для Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json на macOS). Cursor и Windsurf используют такой же JSON в .cursor/mcp.json / .windsurf/mcp.json:
{
"mcpServers": {
"remnawave": {
"command": "node",
"args": ["/absolute/path/to/mcp-remnawave/dist/index.js"],
"env": {
"REMNAWAVE_BASE_URL": "https://vpn.example.com",
"REMNAWAVE_API_TOKEN": "your-api-token-here"
}
}
}
}Docker: npm run build && docker compose up -d (переменные через .env или docker-compose.yml).
Пользователи адресуются числовым id (в API 3.x пользовательские UUID убраны). Полный список с описанием параметров отдаёт сам клиент — ниже только распределение по категориям.
Категория | Кол-во | Категория | Кол-во | |
Пользователи | 30 | Страницы подписок | 7 | |
Плагины нод и shared lists | 18 | HWID-устройства | 7 | |
Ноды | 15 | Соединения | 7 | |
Система и статистика | 14 | Шаблоны подписок | 6 | |
Биллинг инфраструктуры | 12 | Сниппеты | 5 | |
Хосты | 12 | Интеграции нод | 5 | |
Внутренние группы | 11 | API-токены | 4 | |
Подписки | 10 | Метаданные | 4 | |
Конфиг-профили и inbounds | 9 | Настройки / Настройки подписок | 2 + 2 | |
Внешние группы | 8 | Теги · Keygen | 2 · 1 |
Ресурсы: remnawave://stats, remnawave://nodes, remnawave://health, remnawave://users/{userId}
Промпты: create_user_wizard, node_diagnostics, traffic_report, user_audit, bulk_user_cleanup
Примеры запросов: «покажи пользователей с истёкшей подпиской», «создай пользователя vasya на 50 ГБ на месяц», «перезапусти ноду amsterdam-01», «какие ноды офлайн?»
src/client/index.ts — HTTP-клиент (по методу на эндпоинт), src/tools/*.ts — регистрация инструментов, по файлу на домен. @remnawave/backend-contract держим запиненным ровно на версию панели.
MIT. Проект вырос из TrackLine/mcp-remnawave.
Create a new API token (API 3.x: tokens are scoped)
Inputs: name (required), expiresInDays (required), scopes.
Delete an API token
Inputs: uuid (required).
List all API tokens
Inputs: no named parameters.
List all valid API token scopes
Inputs: no named parameters.
Check current authentication status with Remnawave panel
Inputs: no named parameters.
Get top per-user bandwidth usage across the given nodes for a date range
Inputs: end (required), start (required), nodesUuids (required), topUsersLimit.
Create a billing history entry
Inputs: amount (required), providerUuid (required), description.
Delete a billing history entry
Inputs: uuid (required).
List billing history
Inputs: no named parameters.
Create a billing node
Inputs: nodeUuid (required), providerUuid (required), pricePerMonth.
Delete a billing node
Inputs: uuid (required).
List all billing nodes
Inputs: no named parameters.
Update a billing node
Inputs: uuid (required), pricePerMonth.
Create a new billing provider
Inputs: name (required), description.
Delete a billing provider
Inputs: uuid (required).
Get a billing provider by UUID
Inputs: uuid (required).
List all infrastructure billing providers
Inputs: no named parameters.
Update a billing provider
Inputs: uuid (required), name, description.
Create a new config profile
Inputs: name (required).
Delete a config profile
Inputs: uuid (required).
Get a config profile by UUID
Inputs: uuid (required).
Get computed configuration for a config profile
Inputs: uuid (required).
Get inbounds for a specific config profile
Inputs: uuid (required).
List all config profiles
Inputs: no named parameters.
Reorder config profiles by providing each profile UUID with its new position
Inputs: items (required).
Update a config profile
Inputs: uuid (required), name, config.
Drop active connections by user IDs or IP addresses on all or specific nodes (async, 202)
Inputs: userIds, nodeUuids, ipAddresses.
Fetch connections for all users on a node (async job, returns jobId)
Inputs: nodeUuid (required).
Fetch active connections for a user (async job, returns jobId)
Inputs: userId (required).
Run a geolocation check from a node (async job; requires node 3.3.0+)
Inputs: nodeUuid (required), ip, interface.
Get result of a geocheck job
Inputs: jobId (required).
Get result of a node connections fetch job
Inputs: jobId (required).
Get result of a user connections fetch job
Inputs: jobId (required).
Add ALL users to an external squad (async 202)
Inputs: squadUuid (required).
Create a new external squad
Inputs: name (required).
Delete an external squad
Inputs: uuid (required).
Get an external squad by UUID
Inputs: uuid (required).
List all external squads
Inputs: no named parameters.
Remove ALL users from an external squad (async 202)
Inputs: squadUuid (required).
Reorder external squads
Inputs: uuids (required).
Update an external squad
Inputs: uuid (required), name.
Bulk delete selected hosts
Inputs: uuids (required).
Bulk disable selected hosts
Inputs: uuids (required).
Bulk enable selected hosts
Inputs: uuids (required).
Bulk update fields on selected hosts (replaces the removed set-inbound / set-port endpoints)
Inputs: uuids (required), sni, alpn, host, +12 more.
Create a new host in Remnawave
Inputs: port (required), remark (required), address (required), configProfileUuid (required), +17 more.
Delete a host from Remnawave
Inputs: uuid (required).
Get a specific host by UUID
Inputs: uuid (required).
List all Remnawave hosts
Inputs: no named parameters.
Reorder hosts by providing each host UUID with its new position
Inputs: hosts (required).
List all host tags
Inputs: no named parameters.
Update an existing host
Inputs: uuid (required), sni, alpn, host, +15 more.
Create a HWID device entry for a user
Inputs: hwid (required), userId (required), platform, osVersion, +2 more.
Delete a specific HWID device (identified by user ID + hardware ID)
Inputs: hwid (required), userId (required).
Delete all HWID devices for a user
Inputs: userId (required).
List HWID devices for a specific user
Inputs: userId (required).
List all HWID devices across all users
Inputs: no named parameters.
Get HWID device statistics
Inputs: no named parameters.
Get users with most HWID devices
Inputs: no named parameters.
List all inbounds from all config profiles
Inputs: no named parameters.
Generate a new SECRET_KEY for node configuration
Inputs: no named parameters.
Get metadata for a specific node
Inputs: uuid (required).
Create or update metadata for a node
Inputs: uuid (required), metadata (required).
Get metadata for a specific user
Inputs: userId (required).
Create or update metadata for a user
Inputs: userId (required), metadata (required).
Create a node integration
Inputs: name (required), config (required), description.
Delete a node integration
Inputs: uuid (required).
Get a node integration by UUID
Inputs: uuid (required).
List all node integrations
Inputs: no named parameters.
Update a node integration
Inputs: uuid (required), name, config, description, +1 more.
Clone a node plugin
Inputs: uuid (required).
Create a new node plugin
Inputs: name (required).
Delete a node plugin
Inputs: uuid (required).
Execute a node plugin
Inputs: uuid (required).
Get a node plugin by UUID
Inputs: uuid (required).
List all node plugins
Inputs: no named parameters.
Reorder node plugins
Inputs: uuids (required).
Sync a node plugin to its nodes (async, 202)
Inputs: uuid (required).
Get torrent blocker reports
Inputs: no named parameters.
Get torrent blocker statistics
Inputs: no named parameters.
Truncate all torrent blocker reports
Inputs: no named parameters.
Update a node plugin
Inputs: uuid (required), name.
Bulk actions on selected nodes (enable/disable/restart)
Inputs: action (required), nodeUuids (required).
Bulk modify config profile for selected nodes
Inputs: nodeUuids (required), configProfileUuid (required).
Bulk update properties for selected nodes
Inputs: uuids (required), note, tags, countryCode, +2 more.
Create a new node in Remnawave
Inputs: name (required), address (required), activeInbounds (required), activeConfigProfileUuid (required), +12 more.
Delete a node from Remnawave
Inputs: uuid (required).
Disable a node
Inputs: uuid (required).
Enable a disabled node
Inputs: uuid (required).
Get a specific node by UUID
Inputs: uuid (required).
List all Remnawave nodes
Inputs: no named parameters.
Reorder nodes by providing each node UUID with its new position
Inputs: nodes (required).
Reset traffic counter for a node
Inputs: uuid (required).
Restart a specific node
Inputs: uuid (required), forceRestart.
Restart all nodes
Inputs: forceRestart.
List all node tags
Inputs: no named parameters.
Update an existing node
Inputs: uuid (required), ips, name, note, +11 more.
Get Remnawave panel settings
Inputs: no named parameters.
Update Remnawave panel settings
Inputs: settings (required).
Create a new configuration snippet
Inputs: name (required), snippet (required).
Delete a snippet by name
Inputs: name (required).
List all configuration snippets
Inputs: no named parameters.
Sync a snippet to the config profiles using it (async, 202)
Inputs: name (required).
Update an existing snippet (identified by name)
Inputs: name (required), newName, snippet.
Get nodes accessible to a specific squad
Inputs: uuid (required).
Add ALL users to an internal squad (async 202)
Inputs: squadUuid (required).
Add specific users to an internal squad (1-1000 per call, async 202)
Inputs: userIds (required), squadUuid (required).
Create a new internal squad
Inputs: name (required).
Delete an internal squad
Inputs: uuid (required).
Get a specific internal squad by UUID
Inputs: uuid (required).
List all internal squads
Inputs: no named parameters.
Remove ALL users from an internal squad (async 202)
Inputs: squadUuid (required).
Remove specific users from an internal squad (1-1000 per call, async 202)
Inputs: userIds (required), squadUuid (required).
Reorder internal squads by providing each squad UUID with its new position
Inputs: items (required).
Update an internal squad
Inputs: uuid (required), name.
Clone a subscription page configuration
Inputs: uuid (required).
Create a subscription page configuration
Inputs: name (required).
Delete a subscription page configuration
Inputs: uuid (required).
Get a subscription page config by UUID
Inputs: uuid (required).
List all subscription page configurations
Inputs: no named parameters.
Reorder subscription page configurations
Inputs: uuids (required).
Update a subscription page configuration
Inputs: uuid (required), name.
Get subscription info by short UUID (public endpoint)
Inputs: shortUuid (required).
List subscription request history
Inputs: no named parameters.
Get subscription request history statistics
Inputs: no named parameters.
Get Remnawave subscription settings
Inputs: no named parameters.
Update Remnawave subscription settings (API 3.x: profile title/support link/update interval/HAPP fields moved to custom response headers)
Inputs: uuid (required), hwidSettings, customRemarks, responseRules, +4 more.
Get subscription details by user numeric ID
Inputs: userId (required).
Get subscription details by short UUID
Inputs: shortUuid (required).
Get subscription details by username
Inputs: username (required).
Get connection keys for a user subscription
Inputs: userId (required).
Get raw subscription config by short UUID
Inputs: shortUuid (required).
Get subscription page configuration
Inputs: shortUuid (required).
List all subscriptions with pagination
Inputs: size, start.
Create a new subscription template
Inputs: name (required), templateType (required).
Delete a subscription template
Inputs: uuid (required).
Get a subscription template by UUID
Inputs: uuid (required).
List all subscription templates
Inputs: no named parameters.
Reorder subscription templates by providing each template UUID with its new position
Inputs: items (required).
Update an existing subscription template
Inputs: uuid (required), name, templateJson, encodedTemplateYaml.
Get bandwidth statistics
Inputs: no named parameters.
Get Remnawave panel configuration
Inputs: no named parameters.
Generate X25519 key pair for VLESS Reality
Inputs: no named parameters.
Check Remnawave panel health status
Inputs: no named parameters.
Get Remnawave panel metadata and version information
Inputs: no named parameters.
Get detailed node metrics
Inputs: no named parameters.
Get node statistics
Inputs: no named parameters.
Test subscription request routing rules
Inputs: input (required).
Get overall Remnawave panel statistics (users, nodes, traffic, memory, CPU)
Inputs: no named parameters.
Get system statistics digest for a date-time range
Inputs: end (required), start (required).
Get HTTP request statistics
Inputs: no named parameters.
Get system statistics recap
Inputs: no named parameters.
Replace the tags of one entity in a domain (config profiles, internal/external squads, node plugins, subscription page configs, subscription templates)
Inputs: tags (required), uuid (required), domain (required).
List all tags used in a domain (config profiles, internal/external squads, node plugins, subscription page configs, subscription templates)
Inputs: domain (required).
Get nodes accessible to a specific user
Inputs: userId (required).
Extend expiration date for ALL users
Inputs: days (required).
Reset traffic counters for ALL users
Inputs: no named parameters.
Update ALL users at once (async, returns 202)
Inputs: tag, email, status, expireAt, +5 more.
Bulk delete selected users
Inputs: userIds (required).
Bulk delete users by status
Inputs: status (required).
Bulk extend expiration date for selected users
Inputs: days (required), userIds (required).
Bulk reset traffic for selected users
Inputs: userIds (required).
Bulk revoke subscriptions for selected users
Inputs: userIds (required).
Bulk update selected users (async, returns 202)
Inputs: userIds (required), tag, email, status, +7 more.
Bulk update internal squad assignments for selected users
Inputs: userIds (required), activeInternalSquads (required).
Create a new VPN user in Remnawave
Inputs: expireAt (required), username (required), tag, email, +8 more.
Permanently delete a Remnawave user
Inputs: userId (required).
Disable a Remnawave user (block VPN access)
Inputs: userId (required).
Enable a disabled Remnawave user (restore VPN access)
Inputs: userId (required).
Extend user subscription by N days (expired users become ACTIVE with +N days from now; active users get +N days added)
Inputs: days (required), userId (required).
Get a specific Remnawave user by their numeric ID (API 3.x: uuid is gone, id is the primary key)
Inputs: userId (required).
Find Remnawave users by their email (via the users stream filter)
Inputs: email (required).
Get a Remnawave user by their short UUID
Inputs: shortUuid (required).
Find Remnawave users by tag (via the users stream filter)
Inputs: tag (required).
Find Remnawave users by their Telegram ID (via the users stream filter)
Inputs: telegramId (required).
Get a Remnawave user by their username
Inputs: username (required).
List all Remnawave VPN users with pagination
Inputs: size, start.
Reset traffic counter for a Remnawave user
Inputs: userId (required).
Resolve a single user by numeric ID, short UUID, or username (provide exactly one)
Inputs: id, username, shortUuid.
Revoke subscription for a Remnawave user (generates new subscription link)
Inputs: userId (required).
Stream users with cursor pagination and filters (status, traffic strategy, telegramId, email, tag, external squad)
Inputs: tag, size, email, cursor, +4 more.
Get subscription request history for a specific user
Inputs: userId (required).
List all user tags
Inputs: no named parameters.
Update an existing Remnawave user (identified by numeric ID)
Inputs: id (required), tag, email, status, +9 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 190 tools
Numerous tools have overlapping purposes, such as multiple lookup methods for users (users_get, users_get_by_username, users_get_by_short_uuid, users_get_by_telegram_id, users_get_by_email, users_stream, users_resolve) and several bulk operation tools that vary only slightly. This makes it difficult for an agent to select the correct tool, leading to frequent misselection.
The naming pattern is largely consistent, using a resource_action convention (e.g., users_list, nodes_create, hosts_delete). Most tools follow this pattern, though there are minor deviations such as 'subscription_info' vs 'subscriptions_get_by_id' and 'keygen_get' which uses 'get' for generation. Overall, the pattern is predictable.
With 190 tools, this is far beyond any reasonable scope for a single MCP server. The calibration indicates that 50+ tools are extreme, and this server has nearly four times that amount. The tool surface is overwhelming and would likely cause confusion and inefficiency for agents.
The tool set covers all major resources (users, nodes, hosts, squads, subscriptions, billing, config profiles, plugins, etc.) with full CRUD operations and lifecycle management. There are no obvious missing operations for the domain; the massive number of tools suggests thorough coverage. Minor gaps may exist (e.g., password management), but overall the surface is complete.
Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.
Cloud-hosted MCP server for URnetwork VPN and Proxy
Official xCloud MCP: manage servers, sites, WordPress, SSL, backups and deploys from any MCP client.
Remote MCP server for Web3TV creators — manage your account over MCP.
