@supcon-international/node-red-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_RED_URL | Yes | URL of your Node-RED instance | |
| NODE_RED_TOKEN | No | API access token (optional if not required by Node-RED) | |
| MCP_BACKUP_PATH | No | Custom backup directory path (optional) | |
| MCP_MAX_BACKUPS | No | Maximum number of backups to keep (optional, default 10) | |
| NODE_MCP_PREFIX | No | API path prefix for reverse proxy (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-flowsA | Retrieves the complete list of flows from the Node-RED instance. |
| update-flowsA | Updates the entire flow configuration of the Node-RED instance. Args: flowsJson (e.g.'[{type: 'tab', id: '396c2376c693d', label: 'Sheet 1'}]') |
| get-flowA | Retrieves the configuration of a specific flow by its ID. Args: id (e.g.'396c237c693dc') |
| update-flowB | Updates the configuration of a specific flow by its id. Args: id (e.g.'396c237c693dc') flowJson (e.g.'{id: '91ad456e52b8', label: 'Sheet 1', nodes: [], configs: []}') |
| list-tabsA | Lists all flow tabs (workspaces) in the Node-RED instance. |
| create-flowA | Creates a new flow in the Node-RED instance. Args: flowJson (e.g.'{id: '91ad456e52b8', label: 'Sheet 1', nodes: [], configs: []}') |
| delete-flowB | Deletes a specific flow from the Node-RED instance by its ID. Args: id (e.g.'396c237c693dc') |
| get-flows-stateA | Retrieves the current deployment state of all flows in the Node-RED instance. This tool returns the runtime state of the flows, including their active status. |
| set-flows-stateB | Updates the deployment state of all flows in the Node-RED instance. |
| get-flows-formattedA | Retrieves a human-readable, formatted list of all flows in the Node-RED instance. |
| visualize-flowsA | Generates a graph-like visualization of the flows in the Node-RED instance. |
| injectA | Triggers an inject node in the Node-RED instance by its ID. This tool simulates an input event for the specified inject node. |
| get-available-nodesA | Retrieves a list of all installed nodes their information (name,help,module) in the Node-RED instance. |
| get-node-detailed-infoB | Retrieves source code about a specific node module by its name. Args: module (e.g.'node-red/inject') |
| get-node-set-detailed-infoB | Retrieves source code about a specific node module by its name. Args: module (e.g.'@supcon-international/node-red-function-gpt-with-memory') set (e.g.'function-gpt') |
| install-node-moduleB | Install a specific node module in the Node-RED instance. Args: module (e.g.'node-red-dashboard') |
| toggle-node-moduleA | Enables or disables a specific node module in the Node-RED instance. Args: module (e.g.'node-red/inject') enabled (e.g.'true') |
| toggle-node-module-setA | Enables or disables a specific node module set in the Node-RED instance. Args: module (e.g.'@supcon-international/node-red-function-gpt-with-memory') set (e.g.'function-gpt') enabled (e.g.'true') |
| find-nodes-by-typeB | Searches for nodes in the Node-RED instance by their type. Args: nodeType (e.g.'inject') |
| search-nodesB | Searches for nodes in the Node-RED instance by a query string, optionally filtering by a specific property. Args: query (e.g.'inject') property (e.g.'type') (optional) |
| get-settingsB | Retrieves the runtime settings of the Node-RED instance. This tool returns the current configuration settings of the Node-RED server. |
| get-diagnosticsA | Retrieves diagnostic information from the Node-RED instance. This tool returns detailed runtime diagnostics, including system status and performance metrics. |
| api-helpA | Displays a help table of all available Node-RED Admin API methods, including their implementation status in the MCP server. This tool provides a quick reference for available API endpoints. |
| backup-flowsB | Create a named backup of current Node-RED flows with optional reason |
| list-backupsB | List all available flow backups with details |
| get-backup-flowsB | Get the specific flows content from a backup by name |
| backup-healthB | Check backup system health and provide recommendations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Some tools overlap in purpose, e.g., 'find-nodes-by-type' and 'search-nodes' both search nodes, and there are multiple 'get-flows' variants (get-flows, get-flows-formatted, get-flows-state) which could confuse an agent. However, most tools target distinct operations.
Naming is inconsistent: most tools use verb_noun (e.g., create-flow, delete-flow), but some deviate with prepositions (find-nodes-by-type), adjectives (get-flows-formatted), or single verbs (inject). The pattern is not uniform.
27 tools is on the high side for a server, but the domain (Node-RED administration) is broad enough to warrant many tools. However, some tools like get-node-detailed-info and get-node-set-detailed-info could be consolidated.
The tool set covers most common Node-RED admin operations: flow CRUD, backups, node management, diagnostics, and settings. Missing uninstall-node-module and maybe credential management, but these are minor gaps.