Skip to main content
Glama

mcp-remnawave

MCP server for the Remnawave VPN panel — tools generated from the panel's own API contract

Remnawave 3.4 Node.js 22+ MCP License: MIT Version

English · Русский


Lets an MCP client — Claude Code, Claude Desktop, Cursor or any other — read and manage users, nodes, hosts, config profiles, squads, subscriptions, node plugins, traffic statistics, billing and HWID devices through the panel's REST API.

Every tool is built from @remnawave/backend-contract — the package the panel itself validates requests with. Route, HTTP method and arguments come from the contract, so a tool cannot drift away from the API: updating for a new panel version means bumping one dependency.

Maintained fork of TrackLine/mcp-remnawave.

✨ Highlights

📜 Generated from the contract

203 tools cover the whole API of Remnawave 3.4. A test fails when the contract gains a command that has no tool

🚦 Three access levels

Read only · read + write · read + write + destructive. Tools above the chosen level are not registered at all

🧩 Toolsets

Register only the groups you need (users, nodes, hosts, …) to keep the client's tool list short

🧾 Nothing is dropped silently

An argument the endpoint does not know is an error, not an update that quietly did nothing. Validation errors name the field

🗂 One install, many panels

Panel config is looked up in the current project first — the active panel is whichever project you are working in

🪶 Compact answers

List tools leave out xray configs and raw inbound objects unless asked (full: true)

Related MCP server: remnawave-mcp

🚀 Quick start

git clone https://github.com/Maaagiic/mcp-remnawave.git
cd mcp-remnawave
npm install && npm run build

cp .env.example .env          # set REMNAWAVE_BASE_URL and REMNAWAVE_API_TOKEN

# Claude Code — available in every project:
claude mcp add --scope user remnawave -- node "$PWD/dist/index.js"

That's it. Ask your client to call system_metadata — it should answer with the panel version.

{
  "mcpServers": {
    "remnawave": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-remnawave/dist/index.js"]
    }
  }
}

The server speaks MCP over stdio, so the client starts one container per session — there is no port to expose and nothing to keep running.

docker build -t remnawave-mcp .
claude mcp add --scope user remnawave -- docker run -i --rm --env-file /absolute/path/to/.env remnawave-mcp

Any stdio MCP client works — point it at node dist/index.js and pass the environment variables from the table below (or rely on the config file lookup).

⚙️ Configuration

Variable

Default

Description

REMNAWAVE_BASE_URL

— (required)

Panel URL, e.g. https://panel.example.com

REMNAWAVE_API_TOKEN

— (required)

API token (Bearer) — Panel → API tokens

REMNAWAVE_READONLY

false

true = only tools that read are registered (recommended to start with)

REMNAWAVE_ALLOW_DESTRUCTIVE

true

false = tools that delete data or act on every user/node are not registered

REMNAWAVE_TOOLSETS

all

Comma-separated toolsets to register, e.g. users,nodes,hosts

REMNAWAVE_TOOLS_EXCLUDE

—

Comma-separated tool names to leave out; * is a wildcard (users_bulk_*)

REMNAWAVE_TIMEOUT_MS

30000

Timeout for one request to the panel

REMNAWAVE_API_KEY

—

X-Api-Key for a reverse proxy in front of the panel

REMNAWAVE_ENV_FILE

—

Explicit path to a config file

Where the config comes from

The server stops at the first file that provides REMNAWAVE_BASE_URL and REMNAWAVE_API_TOKEN:

1. $REMNAWAVE_ENV_FILE          explicit path
2. <cwd>/.remnawave.env         per-project — add it to .gitignore
3. <cwd>/.env
4. <package>/.env               fallback

MCP clients launch stdio servers with cwd set to the project root, so with a single global install the active panel is whichever project you are working in. To add a panel, drop a .remnawave.env into its project — nothing to change on the server side. Variables already present in the environment are never overridden, so env passed by the client registration always wins. If nothing is found, the server exits with a message that lists the files it looked at.

Access levels

Every tool has a kind, shown to the client as MCP annotations (readOnlyHint, destructiveHint):

Kind

What it is

Registered when

read

Does not change the panel (includes POST endpoints that only look things up)

always

write

Creates or changes something

REMNAWAVE_READONLY is not true

destructive

Deletes data, or acts on every user or node at once

write mode and REMNAWAVE_ALLOW_DESTRUCTIVE is not false

Tools above the chosen level are not registered, so the client cannot even attempt them; calling one by name answers with the reason it is off. A sensible setup for daily work is write mode with REMNAWAVE_ALLOW_DESTRUCTIVE=false.

🧰 Tools

203 contract tools in 12 toolsets, plus api_request.

Toolset

Read

Write

Destructive

users

users_list, users_stream, users_get, users_get_by_username, users_get_by_short_uuid, users_resolve, users_tags_list, users_accessible_nodes, users_subscription_request_history

users_create, users_update, users_enable, users_disable, users_revoke_subscription, users_reset_traffic, users_extend_expiration, users_bulk_update, users_bulk_update_squads, users_bulk_extend_expiration, users_bulk_reset_traffic, users_bulk_revoke_subscription

users_delete, users_bulk_delete, users_bulk_delete_by_status, users_bulk_all_update, users_bulk_all_reset_traffic, users_bulk_all_extend_expiration

nodes

nodes_list, nodes_get, nodes_tags_list, keygen_get, node_integrations_list, node_integrations_get

nodes_create, nodes_update, nodes_enable, nodes_disable, nodes_restart, nodes_reset_traffic, nodes_reorder, nodes_bulk_actions, nodes_bulk_update, nodes_bulk_profile_modification, node_integrations_create, node_integrations_update

nodes_delete, nodes_restart_all, node_integrations_delete

hosts

hosts_list, hosts_get, hosts_tags_list

hosts_create, hosts_update, hosts_clone, hosts_reorder, hosts_bulk_enable, hosts_bulk_disable, hosts_bulk_update

hosts_delete, hosts_bulk_delete

config_profiles

config_profiles_list, config_profiles_get, config_profiles_get_computed_config, config_profiles_get_inbounds, inbounds_list, config_profiles_tags_list, snippets_list

config_profiles_create, config_profiles_update, config_profiles_set_tags, config_profiles_reorder, snippets_create, snippets_update, snippets_sync

config_profiles_delete, snippets_delete

squads

squads_list, squads_get, squads_accessible_nodes, squads_tags_list, external_squads_list, external_squads_get, external_squads_tags_list

squads_create, squads_update, squads_set_tags, squads_reorder, squads_add_many_users, squads_remove_many_users, external_squads_create, external_squads_update, external_squads_set_tags, external_squads_reorder

squads_add_all_users, squads_remove_all_users, squads_delete, external_squads_add_all_users, external_squads_remove_all_users, external_squads_delete

hwid

hwid_devices_list, hwid_devices_list_all, hwid_stats, hwid_top_users

hwid_device_create

hwid_device_delete, hwid_devices_delete_all

subscriptions

subscriptions_list, subscriptions_get_by_user_id, subscriptions_get_by_username, subscriptions_get_by_short_uuid, subscriptions_get_raw_by_short_uuid, subscriptions_get_connection_keys, subscription_info, subscription_request_history_list, subscription_request_history_stats, subscription_settings_get, subscription_templates_list, subscription_templates_get, subscription_templates_tags_list, sub_page_configs_list, sub_page_configs_get, sub_page_configs_tags_list

subscription_settings_update, subscription_templates_create, subscription_templates_update, subscription_templates_set_tags, subscription_templates_reorder, sub_page_configs_create, sub_page_configs_update, sub_page_configs_clone, sub_page_configs_set_tags, sub_page_configs_reorder

subscription_templates_delete, sub_page_configs_delete

node_plugins

node_plugins_list, node_plugins_get, node_plugins_tags_list, node_plugins_torrent_reports, node_plugins_torrent_stats, shared_lists_list, shared_lists_get

node_plugins_create, node_plugins_update, node_plugins_clone, node_plugins_set_tags, node_plugins_reorder, node_plugins_sync, node_plugins_execute, shared_lists_create, shared_lists_update, shared_lists_sync

node_plugins_delete, node_plugins_torrent_truncate, shared_lists_delete

connections

connections_by_user_request, connections_by_user_result, connections_by_node_request, connections_by_node_result, connections_geocheck_request, connections_geocheck_result

—

connections_drop

stats

system_stats, system_stats_recap, system_stats_digest, system_http_stats, system_bandwidth_stats, system_nodes_statistics, system_nodes_metrics, bandwidth_nodes_usage, bandwidth_node_users, bandwidth_nodes_users, bandwidth_nodes_usage_threshold, bandwidth_user_usage, bandwidth_squad_usage, bandwidth_squad_user_usage

—

—

system

system_health, system_metadata, system_configuration, system_generate_x25519, system_srr_matcher, auth_status, settings_get, api_tokens_list, api_tokens_scopes, metadata_node_get, metadata_user_get

settings_update, api_tokens_create, metadata_node_upsert, metadata_user_upsert

api_tokens_delete

billing

billing_providers_list, billing_provider_get, billing_nodes_list, billing_history_list

billing_provider_create, billing_provider_update, billing_node_create, billing_node_update, billing_history_create

billing_provider_delete, billing_node_delete, billing_history_delete

raw

api_request (GET)

—

api_request (any method)

Good to know:

  • Users are identified by a numeric id, not a uuid. To search by telegramId, email, tag or status use users_list with filters: [{"id": "telegramId", "value": 123456789}].

  • A tool takes exactly the fields of its endpoint. Unknown arguments are rejected before anything is sent; values are forwarded as given, with no defaults added.

  • config_profiles_update with config replaces the whole xray config of the profile — read it, patch it, write it back. Nodes using the profile restart xray to apply it.

  • Compact lists: nodes_list, config_profiles_list, squads_list and inbounds_list leave out bulky parts by default; pass full: true for the raw panel response.

  • squads_add_all_users / squads_remove_all_users act on every user. For selected users use squads_add_many_users / squads_remove_many_users.

  • connections_*_request start a job on the node and return a jobId; fetch the outcome with the matching *_result tool.

  • api_request sends a raw request for endpoints the installed contract does not describe yet. GET works in every mode; other methods need write mode with destructive tools allowed.

  • api_tokens_* and settings_* need an API token with the matching scope — otherwise the panel answers Forbidden.

🔁 Panel versions

Tools describe the API of contract 3.4.15 (checked against a live 3.4.4 panel). The server targets Remnawave 3.4; for a 2.x or 3.0–3.3 panel use release v2.1.0.

To follow a new panel release:

npm install --save-exact @remnawave/backend-contract@<version> zod@<the zod version it depends on>
npm run check

npm run check fails with the list of contract commands that have no tool yet (add them to src/tools/registry.ts) and shows every changed argument as a snapshot diff.

⬆️ Upgrading from 2.x

3.0 is a breaking release: tools now follow the 3.4 API exactly.

  • Removed: ip_control_* (the panel moved these routes — use connections_*), hosts_bulk_set_inbound / hosts_bulk_set_port (use hosts_bulk_update), subscriptions_get_subpage_config.

  • Renamed, because the old names promised something else: squads_add_users / squads_remove_users and external_squads_add_users / _remove_users → *_add_all_users / *_remove_all_users. The endpoints take no user list and affect every user; selected users go through the new squads_add_many_users / squads_remove_many_users.

  • Arguments changed wherever 2.x had drifted from the panel: hosts take tags (array) and internalSquads instead of tag and excludedInternalSquads; nodes_restart takes forceRestart; nodes_bulk_* take uuids; *_reorder take a list of {uuid, viewPosition}; *_clone take cloneFromUuid; HWID tools take userId; tools that address one user (users_get, users_delete, …) take userId instead of id.

  • New: traffic statistics (bandwidth_*), geocheck, shared lists, node integrations, subscription settings, tags for profiles/squads/templates, hosts_clone, hosts_reorder, hosts_bulk_update, users_stream, api_request.

  • docker-compose.yml is gone: the server is a stdio process, see the Docker section above.

🛠 Development

npm run dev         # tsup --watch
npm run build       # tsup → dist/index.js
npm run check       # typecheck + tests

The tests run the real server in-process against a mocked panel: they snapshot the tool surface (names, schemas, annotations) and the HTTP request of every tool, so any change to what a tool sends shows up in review. Accept intended changes with UPDATE_SNAPSHOTS=1 npm test.

Two scripts check a real panel, without changing anything on it:

node scripts/smoke.mjs path/to/.env         # calls every read tool, reports routes the panel does not serve
node scripts/stdio-check.mjs path/to/project   # starts dist/index.js over stdio like a client would

The source is small on purpose: src/tools/registry.ts maps tool names to contract commands, src/tools/contract.ts turns a command into a tool.

📄 License

MIT. Upstream authorship: TrackLine/mcp-remnawave.

Available Tools

204 tools
api_requestA
Destructive

Send a raw request to the panel REST API with the configured token. Use it only for endpoints no dedicated tool covers. All methods are allowed.

Inputs: path (required), body, query, method.

api_tokens_createA

Create a new API token. This endpoint is forbidden to use via "API-key". It can only be used with an admin JWT-token.

Inputs: name (required), expiresInDays (required), scopes.

api_tokens_deleteA
Destructive

Delete API token. This endpoint is forbidden to use via "API-key". It can be used only with an admin JWT-token.

Inputs: uuid (required).

api_tokens_listA
Read-only

Get all API tokens. This endpoint is forbidden to use via "API-key". It can only be used with admin JWT-token.

Inputs: no named parameters.

api_tokens_scopesA
Read-only

Get available API token scopes. Returns the catalog of scopes that can be granted to an API token, grouped by resource. Forbidden via "API-key", admin JWT only.

Inputs: no named parameters.

auth_statusC
Read-only

Get the status of the authentication

Inputs: no named parameters.

bandwidth_nodes_usageC
Read-only

Get Nodes Usage by Range

Inputs: end (required), start (required), topNodesLimit.

bandwidth_nodes_usage_thresholdA
Read-only

Get users exceeding a traffic threshold on the given nodes for a period. Returns users whose total usage over the period on the given nodes is >= minTotalBytes. Underlying usage data is flushed to the database roughly every 2 minutes.

Inputs: end (required), start (required), nodesUuids (required), minTotalBytes.

bandwidth_nodes_usersC
Read-only

Get Nodes Users Usage by Nodes UUIDs

Inputs: end (required), start (required), nodesUuids (required), topUsersLimit.

bandwidth_node_usersC
Read-only

Get Node Users Usage by Node UUID

Inputs: end (required), uuid (required), start (required), topUsersLimit.

bandwidth_squad_usageA
Read-only

Get internal squad users traffic usage for a period. Returns users whose total usage over the period on the given nodes is >= minTotalBytes, scoped to the nodes reachable via the internal squad inbounds. Underlying usage data is flushed to the database roughly every 2 minutes.

Inputs: end (required), uuid (required), start (required), limit, +2 more.

bandwidth_squad_user_usageC
Read-only

Get a single user daily traffic usage on the internal squad nodes for a period. Returns users whose total usage over the period on the given nodes is >= minTotalBytes, scoped to the nodes reachable via the Internal Squad inbounds. Every day in the range is present (zero-filled). Underlying usage data is flushed to the database roughly every 2 minutes.

Inputs: end (required), start (required), userId (required), squadUuid (required).

bandwidth_user_usageC
Read-only

Get User Usage by Range

Inputs: end (required), start (required), userId (required), topNodesLimit.

billing_history_createC

Create infra billing history

Inputs: amount (required), billedAt (required), providerUuid (required).

billing_history_deleteC
Destructive

Delete infra billing history

Inputs: uuid (required).

billing_history_listC
Read-only

Get infra billing history

Inputs: size, start.

billing_node_createC

Create infra billing node

Inputs: name (required), nodeUuid (required), providerUuid (required), nextBillingAt (required).

billing_node_deleteC
Destructive

Delete infra billing node

Inputs: uuid (required).

billing_nodes_listC
Read-only

Get infra billing nodes

Inputs: no named parameters.

billing_node_updateC

Update infra billing nodes

Inputs: uuids (required), nextBillingAt (required).

billing_provider_createC

Create infra provider

Inputs: name (required), loginUrl, faviconLink.

billing_provider_deleteC
Destructive

Delete infra provider by uuid

Inputs: uuid (required).

billing_provider_getC
Read-only

Get infra provider by uuid

Inputs: uuid (required).

billing_providers_listB
Read-only

Get all infra providers

Inputs: no named parameters.

billing_provider_updateD

Update infra provider

Inputs: uuid (required), name, loginUrl, faviconLink.

config_profiles_createC

Create config profile

Inputs: name (required), config (required).

config_profiles_deleteC
Destructive

Delete config profile

Inputs: uuid (required).

config_profiles_getB
Read-only

Get config profile by uuid

Inputs: uuid (required).

config_profiles_get_computed_configB
Read-only

Get computed config profile by uuid

Inputs: uuid (required).

config_profiles_get_inboundsC
Read-only

Get inbounds by profile uuid

Inputs: uuid (required).

config_profiles_listA
Read-only

List config profiles with their inbounds and nodes. The xray config itself is left out: use config_profiles_get for one profile, or full=true.

Inputs: full.

config_profiles_reorderC

Reorder config profiles

Inputs: items (required).

config_profiles_set_tagsC

Set tags of Config Profile

Inputs: tags (required), uuid (required).

config_profiles_tags_listB
Read-only

Get tags of Config Profiles

Inputs: no named parameters.

config_profiles_updateA

Update a config profile: name and/or the full xray config. Nodes that use the profile restart xray to apply it.

Inputs: uuid (required), name, config.

connections_by_node_requestA
Read-only

Request the active connections on a node. Starts a job on the node(s) and returns a jobId — fetch the outcome with connections_by_node_result.

Inputs: nodeUuid (required).

connections_by_node_resultC
Read-only

Get Connections for Node by Job ID

Inputs: jobId (required).

connections_by_user_requestA
Read-only

Request the active connections (IPs) of a user. Starts a job on the node(s) and returns a jobId — fetch the outcome with connections_by_user_result.

Inputs: userId (required).

connections_by_user_resultC
Read-only

Get Connections for User by Job ID

Inputs: jobId (required).

connections_dropC
Destructive

Drop Connections for Users or IPs

Inputs: dropBy (required), targetNodes (required).

connections_geocheck_requestA
Read-only

Check how a node's exit IP is geolocated. Starts a job on the node(s) and returns a jobId — fetch the outcome with connections_geocheck_result.

Inputs: nodeUuid (required), ip, interface.

connections_geocheck_resultC
Read-only

Get Geocheck for Node by Job ID

Inputs: jobId (required).

external_squads_add_all_usersB
Destructive

Add EVERY user to an external squad

Inputs: uuid (required).

external_squads_createC

Create external squad

Inputs: name (required).

external_squads_deleteC
Destructive

Delete external squad

Inputs: uuid (required).

external_squads_getC
Read-only

Get external squad by uuid

Inputs: uuid (required).

external_squads_listB
Read-only

Get all external squads

Inputs: no named parameters.

external_squads_remove_all_usersB
Destructive

Remove EVERY user from an external squad

Inputs: uuid (required).

external_squads_reorderC

Reorder external squads

Inputs: items (required).

external_squads_set_tagsC

Set tags of External Squad

Inputs: tags (required), uuid (required).

external_squads_tags_listB
Read-only

Get tags of External Squads

Inputs: no named parameters.

external_squads_updateD

Update external squad

Inputs: uuid (required), name, templates, hwidSettings, +6 more.

hosts_bulk_deleteC
Destructive

Delete hosts by UUIDs

Inputs: uuids (required).

hosts_bulk_disableC

Disable hosts by UUIDs

Inputs: uuids (required).

hosts_bulk_enableC

Enable hosts by UUIDs

Inputs: uuids (required).

hosts_bulk_updateB

Update many hosts at once: the given fields (same as hosts_update) are applied to every host in uuids

Inputs: uuids (required), sni, alpn, host, +28 more.

hosts_cloneC

Clone host

Inputs: cloneFromUuid (required).

hosts_createC

Create a new host

Inputs: port (required), remark (required), address (required), inbound (required), +27 more.

hosts_deleteC
Destructive

Delete a host by UUID

Inputs: uuid (required).

hosts_getC
Read-only

Get a host by UUID

Inputs: uuid (required).

hosts_listC
Read-only

Get hosts

Inputs: no named parameters.

hosts_reorderD

Reorder hosts

Inputs: hosts (required).

hosts_tags_listB
Read-only

Get tags of hosts

Inputs: no named parameters.

hosts_updateC

Update a host

Inputs: uuid (required), sni, alpn, host, +28 more.

hwid_device_createC

Create a user HWID device

Inputs: hwid (required), userId (required), platform, osVersion, +3 more.

hwid_device_deleteC
Destructive

Delete a user HWID device

Inputs: hwid (required), userId (required).

hwid_devices_delete_allB
Destructive

Delete all user HWID devices

Inputs: userId (required).

hwid_devices_listC
Read-only

Get user HWID devices

Inputs: userId (required).

hwid_devices_list_allB
Read-only

Get HWID devices. Please note that the filters here are primarily intended for use by the frontend and rely on expensive operators such as LIKE under the hood. Misusing these filters may negatively impact the performance of your database.

Inputs: size, start, filters, sorting, +2 more.

hwid_statsC
Read-only

Get HWID devices stats

Inputs: no named parameters.

hwid_top_usersB
Read-only

Get top users by HWID devices

Inputs: size, start.

inbounds_listA
Read-only

List inbounds of all config profiles (tag, type, port, squads). full=true adds the raw xray inbound objects.

Inputs: full.

keygen_getB
Read-only

Get SECRET_KEY for Remnawave Node

Inputs: no named parameters.

metadata_node_getC
Read-only

Get node metadata

Inputs: uuid (required).

metadata_node_upsertC

Update or create Node Metadata

Inputs: uuid (required), metadata (required).

metadata_user_getC
Read-only

Get user metadata

Inputs: userId (required).

metadata_user_upsertC

Update or create User Metadata

Inputs: userId (required), metadata (required).

node_integrations_createD

Create Node Integration

Inputs: name (required), config (required), description.

node_integrations_deleteC
Destructive

Delete Node Integration

Inputs: uuid (required).

node_integrations_getC
Read-only

Get Node Integration by uuid

Inputs: uuid (required).

node_integrations_listB
Read-only

Get all Node Integrations

Inputs: no named parameters.

node_integrations_updateD

Update Node Integration

Inputs: uuid (required), name, config, description, +1 more.

node_plugins_cloneD

Clone Node Plugin

Inputs: cloneFromUuid (required).

node_plugins_createC

Create Node Plugin

Inputs: name (required).

node_plugins_deleteC
Destructive

Delete Node Plugin

Inputs: uuid (required).

node_plugins_executeC

Execute command on node plugins

Inputs: command (required), targetNodes (required).

node_plugins_getC
Read-only

Get Node Plugin by uuid

Inputs: uuid (required).

node_plugins_listB
Read-only

Get all Node Plugins

Inputs: no named parameters.

node_plugins_reorderC

Reorder Node Plugins

Inputs: items (required).

node_plugins_set_tagsC

Set tags of Node Plugin

Inputs: tags (required), uuid (required).

node_plugins_syncA

Sync Node Plugin to nodes. Push the current plugin config, including referenced shared lists, to every connected node this plugin is active on.

Inputs: uuid (required).

node_plugins_tags_listB
Read-only

Get tags of Node Plugins

Inputs: no named parameters.

node_plugins_torrent_reportsB
Read-only

Get Torrent Blocker Reports. Please note that the filters here are primarily intended for use by the frontend and rely on expensive operators such as LIKE under the hood. Misusing these filters may negatively impact the performance of your database.

Inputs: size, start, filters, sorting, +2 more.

node_plugins_torrent_statsC
Read-only

Get Torrent Blocker Reports Stats

Inputs: no named parameters.

node_plugins_torrent_truncateC
Destructive

Truncate Torrent Blocker Reports

Inputs: no named parameters.

node_plugins_updateD

Update Node Plugin

Inputs: uuid (required), name, pluginConfig.

nodes_bulk_actionsC

Perform actions for many nodes

Inputs: uuids (required), action (required).

nodes_bulk_profile_modificationC

Modify Inbounds & Profile for many nodes

Inputs: uuids (required), configProfile (required).

nodes_bulk_updateD

Update many nodes

Inputs: uuids (required), fields (required).

nodes_createD

Create a new node

Inputs: name (required), address (required), configProfile (required), ips, +14 more.

nodes_deleteC
Destructive

Delete a node

Inputs: uuid (required).

nodes_disableC

Disable a node

Inputs: uuid (required).

nodes_enableC

Enable a node

Inputs: uuid (required).

nodes_getC
Read-only

Get node by UUID

Inputs: uuid (required).

nodes_listA
Read-only

List all nodes. Compact by default: inbounds as tags, provider as name, system info trimmed. Pass full=true for the raw panel response, or use nodes_get for one node.

Inputs: full.

nodes_reorderD

Reorder nodes

Inputs: nodes (required).

nodes_reset_trafficC

Reset Node Traffic

Inputs: uuid (required).

nodes_restartC

Restart node

Inputs: uuid (required), forceRestart (required).

nodes_restart_allB
Destructive

Restart EVERY node

Inputs: forceRestart (required).

nodes_tags_listC
Read-only

Get nodes tags

Inputs: no named parameters.

nodes_updateD

Update node

Inputs: uuid (required), ips, name, note, +15 more.

settings_getC
Read-only

Get Remnawave settings

Inputs: no named parameters.

settings_updateC

Update Remnawave settings

Inputs: oauth2Settings, passkeySettings, brandingSettings, passwordSettings.

shared_lists_createC

Create Shared List

Inputs: name (required), config (required).

shared_lists_deleteC
Destructive

Delete Shared List by name

Inputs: name (required).

shared_lists_getC
Read-only

Get Shared List by name

Inputs: name (required).

shared_lists_listA
Read-only

Get Shared Lists (Preview). Returns only the name, type and item count of every shared list. Use "Get Shared List by name" to fetch the items themselves.

Inputs: no named parameters.

shared_lists_syncB

Sync Shared List to nodes. Push every plugin referencing this shared list to the nodes it is active on.

Inputs: name (required).

shared_lists_updateD

Update Shared List

Inputs: name (required), config (required).

snippets_createD

Create snippet

Inputs: name (required), snippet (required).

snippets_deleteC
Destructive

Delete snippet

Inputs: name (required).

snippets_listC
Read-only

Get snippets

Inputs: no named parameters.

snippets_syncB

Sync snippet to affected config profiles. Trigger the sync of a snippet to all config profiles that reference it. Nodes which use affected config profiles will be restarted.

Inputs: name (required).

snippets_updateD

Update snippet

Inputs: name (required), snippet (required).

squads_accessible_nodesD
Read-only

Get internal squad accessible nodes

Inputs: uuid (required).

squads_add_all_usersA
Destructive

Add EVERY user to an internal squad. For selected users use squads_add_many_users.

Inputs: uuid (required).

squads_add_many_usersC

Add many users to internal squad

Inputs: uuid (required), userIds (required).

squads_createC

Create internal squad

Inputs: name (required), inbounds (required).

squads_deleteC
Destructive

Delete internal squad

Inputs: uuid (required).

squads_getB
Read-only

Get internal squad by uuid

Inputs: uuid (required).

squads_listB
Read-only

List internal squads with their inbounds. full=true adds the raw xray inbound objects.

Inputs: full.

squads_remove_all_usersA
Destructive

Remove EVERY user from an internal squad. For selected users use squads_remove_many_users.

Inputs: uuid (required).

squads_remove_many_usersC

Delete many users from internal squad

Inputs: uuid (required), userIds (required).

squads_reorderC

Reorder internal squads

Inputs: items (required).

squads_set_tagsC

Set tags of Internal Squad

Inputs: tags (required), uuid (required).

squads_tags_listB
Read-only

Get tags of Internal Squads

Inputs: no named parameters.

squads_updateC

Update internal squad

Inputs: uuid (required), name, inbounds.

sub_page_configs_cloneC

Clone subscription page config

Inputs: cloneFromUuid (required).

sub_page_configs_createC

Create subscription page config

Inputs: name (required).

sub_page_configs_deleteC
Destructive

Delete subscription page config

Inputs: uuid (required).

sub_page_configs_getC
Read-only

Get subscription page config by uuid

Inputs: uuid (required).

sub_page_configs_listB
Read-only

Get all subscription page configs

Inputs: no named parameters.

sub_page_configs_reorderC

Reorder subscription page configs

Inputs: items (required).

sub_page_configs_set_tagsC

Set tags of Subpage Config

Inputs: tags (required), uuid (required).

sub_page_configs_tags_listB
Read-only

Get tags of Subpage Configs

Inputs: no named parameters.

sub_page_configs_updateC

Update subscription page config

Inputs: uuid (required), name, config.

subscription_infoC
Read-only

Get Subscription Info by Short UUID

Inputs: shortUuid (required).

subscription_request_history_listA
Read-only

Get all subscription request history. Please note that the filters here are primarily intended for use by the frontend and rely on expensive operators such as LIKE under the hood. Misusing these filters may negatively impact the performance of your database.

Inputs: size, start, filters, sorting, +2 more.

subscription_request_history_statsC
Read-only

Get subscription request history stats

Inputs: no named parameters.

subscription_settings_getC
Read-only

Get subscription settings

Inputs: no named parameters.

subscription_settings_updateD

Update subscription settings

Inputs: uuid (required), hwidSettings, customRemarks, responseRules, +4 more.

subscriptions_get_by_short_uuidB
Read-only

Get subscription by short uuid (protected route)

Inputs: shortUuid (required).

subscriptions_get_by_user_idC
Read-only

Get subscription by User ID

Inputs: userId (required).

subscriptions_get_by_usernameC
Read-only

Get subscription by username

Inputs: username (required).

subscriptions_get_connection_keysB
Read-only

Get connection keys (base64 format) by user id

Inputs: userId (required).

subscriptions_get_raw_by_short_uuidD
Read-only

Get Raw Subscription by Short UUID

Inputs: shortUuid (required), withDisabledHosts.

subscriptions_listC
Read-only

Get all subscriptions

Inputs: size, start.

subscription_templates_createC

Create subscription template

Inputs: name (required), templateType (required).

subscription_templates_deleteC
Destructive

Delete subscription template

Inputs: uuid (required).

subscription_templates_getC
Read-only

Get subscription template by uuid

Inputs: uuid (required).

subscription_templates_listB
Read-only

Get all subscription templates (wihout content)

Inputs: no named parameters.

subscription_templates_reorderC

Reorder subscription templates

Inputs: items (required).

subscription_templates_set_tagsC

Set tags of Subscription Template

Inputs: tags (required), uuid (required).

subscription_templates_tags_listB
Read-only

Get tags of Subscription Templates

Inputs: no named parameters.

subscription_templates_updateC

Update subscription template

Inputs: uuid (required), name, templateJson, encodedTemplateYaml.

system_bandwidth_statsC
Read-only

Get Bandwidth Stats

Inputs: tz.

system_configurationB
Read-only

Get Remnawave Configuration. Returns some of the configuration values.

Inputs: no named parameters.

system_generate_x25519B
Read-only

Generate 30 X25519 keypairs

Inputs: no named parameters.

system_healthC
Read-only

Get Remnawave Health

Inputs: no named parameters.

system_http_statsC
Read-only

Get HTTP Stats

Inputs: no named parameters.

system_metadataA
Read-only

Get panel version and build information

Inputs: no named parameters.

system_nodes_metricsC
Read-only

Get Nodes Metrics

Inputs: no named parameters.

system_nodes_statisticsC
Read-only

Get Nodes Statistics

Inputs: tz.

system_srr_matcherB
Read-only

Validate a subscription response rules (SRR) config against the panel matcher. The body is the full responseRules config object, not an input string.

Inputs: responseRules (required).

system_statsD
Read-only

Get Stats

Inputs: tz.

system_stats_digestA
Read-only

Get Stats Digest. Aggregated statistics for a datetime range [start, end): created and expired users, total traffic, traffic spent by users created within the range and new HWID devices. Per-user traffic history is stored with daily granularity (UTC), so the "traffic by new users" metric snaps to whole days at the range edges.

Inputs: end (required), start (required).

system_stats_recapD
Read-only

Get Recap

Inputs: no named parameters.

users_accessible_nodesA
Read-only

Which nodes a user can actually reach: per node — config profile, active squads and their inbounds. Handy for debugging squad/inbound routing.

Inputs: userId (required).

users_bulk_all_extend_expirationA
Destructive

Extend expiration date for EVERY user by days

Inputs: extendDays (required).

users_bulk_all_reset_trafficA
Destructive

Reset used traffic for EVERY user

Inputs: no named parameters.

users_bulk_all_updateC
Destructive

Update EVERY user at once

Inputs: tag, email, status, expireAt, +5 more.

users_bulk_deleteC
Destructive

Bulk delete users by User IDs

Inputs: userIds (required).

users_bulk_delete_by_statusB
Destructive

Delete ALL users that have the given status

Inputs: status (required).

users_bulk_extend_expirationC

Extend expiration date for specified users by days

Inputs: userIds (required), extendDays (required).

users_bulk_reset_trafficC

Bulk reset traffic users by User IDs

Inputs: userIds (required).

users_bulk_revoke_subscriptionC

Revoke users subscription by User IDs

Inputs: userIds (required).

users_bulk_updateC

Bulk update users by User IDs

Inputs: fields (required), userIds (required).

users_bulk_update_squadsC

Bulk update users internal squads by User IDs

Inputs: userIds (required), activeInternalSquads (required).

users_createA

Create a user. Credentials (vlessUuid/ssPassword/trojanPassword/shortUuid) are generated by the panel unless given — pass them explicitly for service users.

Inputs: expireAt (required), username (required), tag, email, +14 more.

users_deleteC
Destructive

Delete user

Inputs: userId (required).

users_disableC

Disable user

Inputs: userId (required).

users_enableC

Enable user

Inputs: userId (required).

users_extend_expirationA

Extend user expiration date. If user status is EXPIRED, the new expiration date is calculated from the current date and the user becomes ACTIVE. If user status is ACTIVE, the given number of days is added to the existing expiration date. DISABLED and LIMITED users will be extended, but their status will not change.

Inputs: days (required), userId (required).

users_getC
Read-only

Get user by ID

Inputs: userId (required).

users_get_by_short_uuidC
Read-only

Get user by Short UUID

Inputs: shortUuid (required).

users_get_by_usernameC
Read-only

Get user by username

Inputs: username (required).

users_listB
Read-only

List users with offset pagination and optional TanStack-style filters. To find users by telegramId, email, tag, status etc. pass filters, e.g. [{"id":"telegramId","value":123456789}]. Users are identified by numeric id.

Inputs: size, start, filters, sorting, +2 more.

users_reset_trafficC

Reset user traffic

Inputs: userId (required).

users_resolveA
Read-only

Resolve a user by EXACTLY ONE of: id, shortUuid, username

Inputs: id, username, shortUuid.

users_revoke_subscriptionB

Revoke user subscription: rotates the subscription link (and credentials unless told otherwise)

Inputs: userId (required), shortUuid, revokeOnlyPasswords.

users_streamB
Read-only

Get all users using cursor-based (keyset) pagination with filtering options

Inputs: tag, size, email, cursor, +4 more.

users_subscription_request_historyA
Read-only

Get user subscription request history, recent 24 records

Inputs: userId (required).

users_tags_listC
Read-only

Get users tags

Inputs: no named parameters.

users_updateC

Update a user. Identify by id OR username.

Inputs: id, tag, email, status, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.5/5.0

    Scored across 204 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    • Rent Manager MCP server for ChatGPT, Claude and any AI agent: post charge, create work order, message tenant and list tenants in your own Rent Manager account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Rent Manager yourself; Cotlet does not store your password and you need no Rent Manager API key. About the official Rent Manager API: Rent Manager has an API that reads and writes your database, but it is not self-serve (checked 11 Oct 2026). Its public pages offer no key signup: access goes through the Integrations Partner Program or an API support request, and a developer then builds the connector. Setup and FAQ: https://cotlet.dev/integrations/rent-manager-api-mcp-server

    • Control newsletters, contacts and automations of Inviomail (German newsletter & email automation tool) from Claude, ChatGPT or your own agents. Hosted in Germany. Remote MCP server with 90+ tools for contacts, lists, tags, newsletters, automation flows and reports. OAuth or Bearer MCP key. Docs: https://admin.inviomail.de/api/docs/mcp

      https://mcp.inviomail.de/mcp
    • ResMan MCP server for ChatGPT, Claude and any AI agent: list work orders, create work order, update work order status, list units and make-ready status, list leases, list move-outs, list prospects and list aged receivables in your own ResMan account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ResMan yourself; Cotlet does not store your password and you need no ResMan API key. About the official ResMan API: ResMan has an API, but only for approved Integration Partners (checked 23 Oct 2026). A property manager cannot get a key for their own account, and ResMan has no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/resman-api-mcp-server

      https://cotlet.dev/mcp/v1/resman
    • Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      18 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      190
      13 npm
      MIT
    • 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