Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"remnawave": {
"env": {
"REMNAWAVE_API_KEY": "your-caddy-api-key",
"REMNAWAVE_BASE_URL": "https://vpn.example.com",
"REMNAWAVE_READONLY": "false",
"REMNAWAVE_API_TOKEN": "your-api-token-here"
},
"args": [
"/absolute/path/to/remnawave-mcp/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server (Model Context Protocol) providing LLM clients (Claude Desktop, Cursor, Windsurf, etc.) with tools to manage a Remnawave VPN panel.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for Mcp Remnawave and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server (Model Context Protocol) providing LLM clients (Claude Desktop, Cursor, Windsurf, etc.) with tools to manage a Remnawave VPN panel.
Version: 1.2.0 | Remnawave API: 2.7.4
X-Api-Key header for panels behind Caddy with custom pathgit clone https://github.com/TrackLine/mcp-remnawave.git
cd mcp-remnawave
npm install
npm run build
Create a .env file or pass environment variables:
| Variable | Required | Description |
|---|---|---|
REMNAWAVE_BASE_URL | Yes | Panel URL (e.g. https://vpn.example.com) |
REMNAWAVE_API_TOKEN | Yes | API token from panel settings |
REMNAWAVE_API_KEY | No | API key for Caddy reverse proxy authentication |
REMNAWAVE_READONLY | No | Set to true to enable readonly mode |
REMNAWAVE_BASE_URL=https://vpn.example.com
REMNAWAVE_API_TOKEN=your-api-token-here
If your Remnawave panel is deployed behind Caddy with a custom path and API key protection, set the base URL to include the custom path and provide the API key:
REMNAWAVE_BASE_URL=https://example.com/your-secret-path/api
REMNAWAVE_API_KEY=your-caddy-api-key
The X-Api-Key header will be added to every request automatically.
Set REMNAWAVE_READONLY=true to disable all write operations (create, update, delete, enable, disable, restart, revoke, reset). Only read/list tools will be registered.
Useful for monitoring dashboards or shared environments where you want to prevent accidental changes.
In readonly mode, the available tools are reduced from 153 to 69:
| Category | Available tools |
|---|---|
| Users (10) | users_list, users_get, users_get_by_username, users_get_by_short_uuid, users_get_by_telegram_id, users_get_by_email, users_get_by_tag, users_get_by_subscription_uuid, users_tags_list, users_resolve |
| Nodes (3) | nodes_list, nodes_get, nodes_tags_list |
| Hosts (3) | hosts_list, hosts_get, hosts_tags_list |
| System (10) | all tools (read-only by nature) |
| Subscriptions (10) | all tools (read-only by nature) |
| Config Profiles & Inbounds (5) | config_profiles_list, config_profiles_get, inbounds_list, config_profiles_get_inbounds, config_profiles_get_computed_config |
| Internal Squads (2) | squads_list, squads_accessible_nodes |
| HWID (4) | hwid_devices_list, hwid_devices_list_all, hwid_stats, hwid_top_users |
| API Tokens (1) | api_tokens_list |
| Keygen (1) | keygen_get |
| Infra Billing (4) | billing_providers_list, billing_provider_get, billing_nodes_list, billing_history_list |
| Snippets (1) | snippets_list |
| External Squads (2) | external_squads_list, external_squads_get |
| Settings (1) | settings_get |
| Sub Page Configs (2) | sub_page_configs_list, sub_page_configs_get |
| Node Plugins (4) | `node_plugins_lis |