@supcon-international/node-red-mcp-server
Allows AI agents to interact with a Node-RED instance, providing tools for managing flows, nodes, tabs, backups, settings, and triggering injections, enabling automated workflow management and deployment.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@supcon-international/node-red-mcp-server list all flows in Node-RED"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@supcon-international/node-red-mcp-server
Model Context Protocol (MCP) server for Node-RED — allows language models (like Claude, GPT) to interact with Node-RED through a standardized API.
This is an enhanced version based on karavaev-evgeniy/node-red-mcp-server
Description
node-red-mcp-server Node-RED-MCP-Server for handling complex Node-RED tasks autonomously
Enhanced Key Features
Retrieve and update Node-RED flows via MCP
Multi-version flow backup system with integrity validation
Add detailed argument descriptions for tools, making it better for LLM usage and handling complicated tasks
get available nodes information (name,help,module name) instead of raw code
install new node via llm
check module and node set module information and manage states
Manage tabs and individual nodes
Search for nodes by type or properties
Access settings and runtime state
Trigger inject nodes remotely
Output and visualize flows and stats
Related MCP server: n8n Workflow Builder MCP Server
Installation
Global Installation
npm install -g @supcon-international/node-red-mcp-serverLocal Installation
npm install @supcon-international/node-red-mcp-serverUsage
Command Line
node-red-mcp --url http://localhost:1880 --token YOUR_TOKENConfiguration via .env
Create a .env file:
NODE_RED_URL=http://localhost:1880
NODE_RED_TOKEN=YOUR_TOKEN
NODE_MCP_PREFIX=/api/v1 # Optional: API path prefix (e.g., /nodered-api /eventflow-api)
MCP_BACKUP_PATH=/custom/backup/path
MCP_MAX_BACKUPS=10Then run:
node-red-mcpIntegration with Claude or Other LLMs
Start the MCP server or configure Claude Desktop to start it automatically with the tool configuration below.
Configure Claude Desktop:
Open Claude Desktop app
Go to Settings → Advanced → Tool Configuration
Add a new tool configuration:
{
"node-red": {
"command": "npx",
"args": ["@supcon-international/node-red-mcp-server", "--verbose"],
"env(Optional,if None then use default value)": {
"NODE_RED_URL": "http://your-node-red-url:1880",
"NODE_RED_TOKEN": "your-token-if-needed",
"NODE_MCP_PREFIX": "/nodered-api",
"MCP_BACKUP_PATH": "/custom/backup/path",
"MCP_MAX_BACKUPS": "10"
}
}
}or
{
"node-red": {
"command": "node",
"args": [
"/path/to/node-red-mcp-server/bin/node-red-mcp-server.mjs",
"--verbose"
],
"env(Optional,if None then use default value)": {
"NODE_RED_URL": "http://your-node-red-url:1880",
"NODE_RED_TOKEN": "your-token-if-needed",
"NODE_MCP_PREFIX": "/nodered-api",
"MCP_BACKUP_PATH": "/custom/backup/path",
"MCP_MAX_BACKUPS": "10"
}
}
}Replace
/path/to/node-red-mcp-serverwith the actual path to your installationUpdate
NODE_RED_URLto point to your Node-RED instanceSet
NODE_RED_TOKENif your Node-RED instance requires authenticationSet
NODE_MCP_PREFIXif your Node-RED API is behind a reverse proxy or requires a path prefix (e.g.,/nodered-api,/eventflow-api). If not set, it defaults to the standard Node-RED API paths
After configuration, Claude can interact with your Node-RED instance through the MCP tools.
For more information about the Model Context Protocol, visit the official MCP documentation.
Programmatic Usage
import { createServer } from "node-red-mcp-server";
const server = createServer({
nodeRedUrl: "http://localhost:1880",
nodeRedToken: "YOUR_TOKEN",
verbose: true,
});
await server.start();Configuration Options
CLI Parameters
Parameter | Short | Description |
|
| Node-RED base URL |
|
| API access token |
|
| Enable verbose logging |
| Custom backup directory path | |
| Maximum number of backups to keep (default: 10) | |
|
| Show help |
|
| Show version number |
Environment Variables
Variable | Description |
| URL of your Node-RED instance |
| API access token |
| Custom backup directory path |
| Maximum number of backups to keep |
| API path prefix for reverse proxy |
MCP Tools
Flow Tools
get-flows— Get all flowsupdate-flows— Update all flowsget-flow— Get a specific flow by IDupdate-flow— Update a specific flow by IDlist-tabs— List all tabs (workspaces)create-flow— Create a new flow tabdelete-flow— Delete a flow tabget-flows-state— Get deployment stateset-flows-state— Change deployment stateget-flows-formatted— Get human-readable flow listvisualize-flows— Generate graph-like view of flows
Node Tools
inject— Trigger an inject nodeget-available-nodes— List available node summary information (name help-doc module)install-node-module- install new node moduleget-node-detailed-info— Detailed info about a node moduleget-node-set-detailed-info- Detailed source code about a node module settoggle-node-module— Enable/disable a node moduletoggle-node-module-set- Enable/disable a node module setfind-nodes-by-type— Locate nodes by typesearch-nodes— Find nodes by name or property
Backup Tools
backup-flows— Create a named backup of current flows with optional reasonlist-backups— List all available flow backups with detailsget-backup-flows— Get the specific flows content from a backup by namebackup-health— Check backup system health and provide recommendations
Settings Tools
get-settings— Get Node-RED runtime settingsget-diagnostics— Fetch diagnostics info
Utility Tools
api-help— Show Node-RED API help
Requirements
Node.js v16 or newer
A running Node-RED instance with HTTP API access
License
MIT License Copyright (c) 2025
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Available Tools
27 toolsapi-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.
Inputs: no named parameters.
backup-flowsB
Create a named backup of current Node-RED flows with optional reason
Inputs: name, reason.
backup-healthB
Check backup system health and provide recommendations
Inputs: no named parameters.
create-flowA
Creates a new flow in the Node-RED instance. Args: flowJson (e.g.'{id: '91ad456e52b8', label: 'Sheet 1', nodes: [], configs: []}')
Inputs: flowJson (required).
delete-flowB
Deletes a specific flow from the Node-RED instance by its ID. Args: id (e.g.'396c237c693dc')
Inputs: id (required).
find-nodes-by-typeB
Searches for nodes in the Node-RED instance by their type. Args: nodeType (e.g.'inject')
Inputs: nodeType (required).
get-available-nodesA
Retrieves a list of all installed nodes their information (name,help,module) in the Node-RED instance.
Inputs: no named parameters.
get-backup-flowsB
Get the specific flows content from a backup by name
Inputs: name (required).
get-diagnosticsA
Retrieves diagnostic information from the Node-RED instance. This tool returns detailed runtime diagnostics, including system status and performance metrics.
Inputs: no named parameters.
get-flowA
Retrieves the configuration of a specific flow by its ID. Args: id (e.g.'396c237c693dc')
Inputs: id (required).
get-flowsA
Retrieves the complete list of flows from the Node-RED instance.
Inputs: no named parameters.
get-flows-formattedA
Retrieves a human-readable, formatted list of all flows in the Node-RED instance.
Inputs: no named parameters.
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.
Inputs: no named parameters.
get-node-detailed-infoB
Retrieves source code about a specific node module by its name. Args: module (e.g.'node-red/inject')
Inputs: module (required).
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')
Inputs: module (required), set (required).
get-settingsB
Retrieves the runtime settings of the Node-RED instance. This tool returns the current configuration settings of the Node-RED server.
Inputs: no named parameters.
injectA
Triggers an inject node in the Node-RED instance by its ID. This tool simulates an input event for the specified inject node.
Inputs: id (required).
install-node-moduleB
Install a specific node module in the Node-RED instance. Args: module (e.g.'node-red-dashboard')
Inputs: module (required).
list-backupsB
List all available flow backups with details
Inputs: detailed.
list-tabsA
Lists all flow tabs (workspaces) in the Node-RED instance.
Inputs: no named parameters.
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)
Inputs: query (required), property.
set-flows-stateB
Updates the deployment state of all flows in the Node-RED instance.
Inputs: stateJson (required).
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')
Inputs: module (required), enabled (required).
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')
Inputs: module (required), set (required), enabled (required).
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: []}')
Inputs: id (required), flowJson (required).
update-flowsA
Updates the entire flow configuration of the Node-RED instance. Args: flowsJson (e.g.'[{type: 'tab', id: '396c2376c693d', label: 'Sheet 1'}]')
Inputs: flowsJson (required).
visualize-flowsA
Generates a graph-like visualization of the flows in the Node-RED instance.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).3365 npm119MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server for programmatically creating and managing n8n workflows.118MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server for Node-RED integration, enabling AI agents to manage flows, install modules, and monitor Node-RED instances via natural language.6MIT
- AlicenseDqualityFmaintenanceModel Context Protocol (MCP) server for Node-RED — allows language models (like Claude, GPT) to interact with Node-RED through a standardized API.201,457 npm39MIT