4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Node-RED MCP Server

Bring Low Code
to Cursor

Learn how to connect Node-RED to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add FlowDelete FlowGet DiagnosticsGet FlowGet FlowsGet NodesGet SettingsInstall NodeRemove NodeSet FlowsUpdate Flow

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Node-RED

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, and delete_flow.
  • Node Operations — List all installed node modules and dynamically install or remove npm packages with install_node and remove_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

  1. Subscribe to this server
  2. Provide your Node-RED Base URL and Access Token
  3. 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_flow

Add a new flow to the configuration

delete_flow

Delete an individual flow

get_diagnostics

js, and memory usage. Get Node-RED system diagnostics

get_flow

Get an individual flow (tab) configuration

get_flows

Get active flow configuration

get_nodes

Get list of installed nodes

get_settings

Get Node-RED runtime settings

install_node

Install a new node module

remove_node

Remove a node module

set_flows

Set active flow configuration

update_flow

Update an individual flow

Why Cursor?

Cursor's Agent mode turns Node-RED into an in-editor superpower. Ask Cursor to generate code using live data from Node-RED and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Node-RED in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Node-RED and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Node-RED to Cursor 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Node-RED in Cursor

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 Cursor 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.

Node-RED
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Node-RED for Cursor

Every tool call from Cursor to the Node-RED MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →