Bring Low Code
to CrewAI
Learn how to connect Node-RED to CrewAI 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 CrewAI?
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.
- —
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
mcpsparameter 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 in CrewAI
Node-RED and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Node-RED to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 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.
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.
Explore More MCP Servers
View all →
WhatsApp Chat Export Parser
1 toolsTurn messy WhatsApp chat exports into clean, structured JSON instantly. Let your AI search years of conversations, find lost addresses, and summarize long threads local.
WakaTime (Coding Stats)
14 toolsTrack your coding activity and productivity metrics directly through WakaTime — monitor projects, goals, and time spent in your IDE.
Shippo
12 toolsGet the best shipping rates from top carriers, print labels, and track deliveries with an API that simplifies e-commerce shipping.
Cody AI
10 toolsEnable your AI agent to manage knowledge-base bots, import documents, and query trained AI assistants via the Cody AI API.