nodes_update
Modify configuration parameters for existing VPN nodes in the Remnawave panel, including network settings, traffic limits, and monitoring preferences.
Instructions
Update an existing node
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Node UUID to update | |
| name | No | New node name | |
| address | No | New address | |
| port | No | New port | |
| countryCode | No | New country code | |
| isTrafficTrackingActive | No | Enable/disable traffic tracking | |
| trafficLimitBytes | No | New traffic limit | |
| trafficResetDay | No | New traffic reset day | |
| notifyPercent | No | New notification threshold | |
| consumptionMultiplier | No | New consumption multiplier |
Implementation Reference
- src/tools/nodes.ts:111-149 (handler)Registration and handler implementation for the 'nodes_update' MCP tool.
server.tool( 'nodes_update', 'Update an existing node', { uuid: z.string().describe('Node UUID to update'), name: z.string().optional().describe('New node name'), address: z.string().optional().describe('New address'), port: z.number().optional().describe('New port'), countryCode: z.string().optional().describe('New country code'), isTrafficTrackingActive: z .boolean() .optional() .describe('Enable/disable traffic tracking'), trafficLimitBytes: z .number() .optional() .describe('New traffic limit'), trafficResetDay: z .number() .optional() .describe('New traffic reset day'), notifyPercent: z .number() .optional() .describe('New notification threshold'), consumptionMultiplier: z .number() .optional() .describe('New consumption multiplier'), }, async (params) => { try { const result = await client.updateNode(params); return toolResult(result); } catch (e) { return toolError(e); } }, );