Bring Low Code
to Claude Desktop
Learn how to connect Node-RED to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Node-RED MCP Server?
Connect your Node-RED instance to any AI agent to orchestrate your event-driven applications and IoT workflows through natural language.
What you can do
- Flow Management — Retrieve, create, update, or delete entire flow configurations and individual tabs using
get_flows,add_flow, anddelete_flow. - Node Operations — List all installed node modules and dynamically install or remove npm packages with
install_nodeandremove_node. - System Diagnostics — Monitor runtime health, including OS details, Node.js version, and memory usage via
get_diagnostics. - Configuration Control — Fetch runtime settings and user information to understand your environment's constraints.
How it works
- Subscribe to this server
- Provide your Node-RED Base URL and Access Token
- Start automating your low-code environment from Claude, Cursor, or any MCP client
Who is this for?
- IoT Developers — monitor and modify edge computing flows without leaving the terminal or editor.
- Automation Engineers — deploy new flow logic and manage node dependencies via conversation.
- DevOps Teams — check system diagnostics and runtime settings across multiple Node-RED instances.
Built-in capabilities (11)
Add a new flow to the configuration
Delete an individual flow
js, and memory usage. Get Node-RED system diagnostics
Get an individual flow (tab) configuration
Get active flow configuration
Get list of installed nodes
Get Node-RED runtime settings
Install a new node module
Remove a node module
Set active flow configuration
Update an individual flow
Why Claude Desktop?
Claude Desktop is the definitive way to connect Node-RED to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Node-RED in Claude Desktop
Node-RED and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Node-RED to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Node-RED in Claude Desktop
The Node-RED MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Node-RED for Claude Desktop
Every tool call from Claude Desktop to the Node-RED MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I install new nodes from npm using this server?
Yes. Use the install_node tool and provide the npm module name. The server will trigger the installation in your Node-RED instance.
How can I check if my Node-RED server is running out of memory?
You can run the get_diagnostics tool. It returns real-time system metrics including memory usage, Node.js version, and OS information.
Is it possible to delete a specific flow tab?
Yes, by using the delete_flow tool with the specific Flow ID. Be careful, as this action will permanently remove that flow configuration.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Measured
8 toolsMarketing performance and incrementality analytics via Measured — track ROAS and cross-channel impact.
GameScorekeeper
10 toolsAccess live sports scores, fixtures, lineups, team form, and player statistics via AI — covering major football competitions worldwide.
National Park Service
10 toolsAccess authoritative data about U.S. National Parks via NPS — track alerts, parks, and events directly from your AI agent.
PubChem
3 toolsSearch 116M+ chemical compounds with molecular properties, SMILES notation, formulas, and drug-like properties from the world's largest free chemistry database.