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

Bring Low Code
to LlamaIndex

Learn how to connect Node-RED to LlamaIndex 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 LlamaIndex?

LlamaIndex agents combine Node-RED tool responses with indexed documents for comprehensive, grounded answers. Connect 11 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine Node-RED tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain Node-RED tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query Node-RED, a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what Node-RED tools were called, what data was returned, and how it influenced the final answer

L
See it in action

Node-RED in LlamaIndex

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 LlamaIndex 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 LlamaIndex

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 LlamaIndex 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 LlamaIndex

Every tool call from LlamaIndex 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

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

05

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Node-RED tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →