Node-RED MCP Server for CrewAIGive CrewAI instant access to 11 tools to Add Flow, Delete Flow, Get Diagnostics, and more

Name: Node-RED
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to Node-RED through Vinkius, pass the Edge URL in the `mcps` parameter and every Node-RED tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Node-RED MCP Server for CrewAI is a standout in the Loved By Devs category — giving your AI agent 11 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Node-RED Specialist",
    goal="Help users interact with Node-RED effectively",
    backstory=(
        "You are an expert at leveraging Node-RED tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Node-RED "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

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

When paired with CrewAI, Node-RED becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Node-RED tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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.

The Node-RED MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 11 Node-RED tools available for CrewAI

When CrewAI connects to Node-RED through Vinkius, your AI agent gets direct access to every tool listed below — spanning low-code, event-driven, workflow-automation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add flow on Node-RED

Add a new flow to the configuration

delete

Delete flow on Node-RED

Delete an individual flow

get

Get diagnostics on Node-RED

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

get

Get flow on Node-RED

Get an individual flow (tab) configuration

get

Get flows on Node-RED

Get active flow configuration

get

Get nodes on Node-RED

Get list of installed nodes

get

Get settings on Node-RED

Get Node-RED runtime settings

install

Install node on Node-RED

Install a new node module

remove

Remove node on Node-RED

Remove a node module

set

Set flows on Node-RED

Set active flow configuration

update

Update flow on Node-RED

Update an individual flow

Connect Node-RED to CrewAI via MCP

Follow these steps to wire Node-RED into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from Node-RED

Why Use CrewAI with the Node-RED MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Node-RED through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Node-RED + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Node-RED MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Node-RED for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Node-RED, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Node-RED tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Node-RED against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Node-RED in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Node-RED immediately.

"Show me all active flows in my Node-RED instance."

"Check the system diagnostics and memory usage."

"Install the 'node-red-node-email' module."

Troubleshooting Node-RED MCP Server with CrewAI

Common issues when connecting Node-RED to CrewAI through Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Node-RED + CrewAI FAQ

Common questions about integrating Node-RED MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →

JSONPlaceholder

21 tools

Access fake online REST API for testing and prototyping — manage posts, comments, albums, photos, and todos directly from your AI agent.

Text Readability Scorer

1 tools

Calculate mathematically accurate readability metrics (Flesch-Kincaid, Gunning Fog, SMOG) for any text. Stop relying on AI 'feelings' — get exact US grade levels for SEO and compliance.