From 754eab96099fb9e05185b163790c3a98f44ac8c3 Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Sun, 14 Jun 2026 13:41:04 +0800 Subject: [PATCH] docs: Clarify why nodes must be started for device config tools --- docs/features/mcp-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/mcp-service.md b/docs/features/mcp-service.md index 64a76fffe..301d1cb84 100644 --- a/docs/features/mcp-service.md +++ b/docs/features/mcp-service.md @@ -213,7 +213,7 @@ Both JWT tokens and API keys work for MCP and REST API endpoints interchangeably | `device_command_run` | Run read-only show commands on devices. Supports Jinja2 `template` + `vars` | | `vpcs_config_set` | Configure VPCS devices (IP, gateway, etc.) | -Requires nodes to be started first. Device type is auto-detected from the node's `device_type:` tag. +The tool connects to each device's console via telnet/SSH. Nodes must be in the `started` state (use `node_start` or `node_start_all`). Device type is auto-detected from the node's `device_type:` tag in GNS3. #### Jinja2 Template Mode