# Node-RED MCP for AI Agents AI Agent Connect

> Node-RED MCP lets you manage your flows, install npm modules, and check system health directly through your AI agent. Instead of clicking through the editor, you can just tell your agent to add a flow, update a config, or see how much memory your instance is using. It turns your low-code environment into a conversational workspace.

## Overview
- **Category:** loved-by-devs
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_eUM0NzEFChIwjVZZEypCDQUUJJ4ngVzPtB8M70nY/ai-agent-connect
- **Tags:** low-code, event-driven, workflow-automation, flow-management, system-diagnostics, api-orchestration

## Description

Think about what it feels like to manage a large Node-RED setup. You have dozens of tabs open, you're hunting for a specific flow to tweak, or you're stuck trying to figure out why a node isn't loading or why a specific trigger is failing. This Connector changes that by making your Node-RED instance accessible to your AI agent. You can ask your agent to pull up a specific flow configuration, push updates to your logic, or swap out node modules without ever opening a browser tab. It's built for people who live in event-driven architectures and need to move faster. Whether you're debugging a memory leak on an edge device or deploying a new automation sequence for a home project, you can just describe the change and let the agent handle the heavy lifting. It makes managing complex IoT workflows feel like a conversation rather than a series of tedious clicks and manual JSON editing. You'll find this in the Vinkius catalog alongside other high-utility developer tools, making it easy to plug into your existing stack and get straight to work without the usual friction of navigating nested menus.

## Tools

### get_diagnostics
Get your system's Node.js version, OS details, and current memory usage. This helps you spot performance issues quickly.

### get_flow
Pull the configuration for a specific flow or tab to inspect its logic. It's the fastest way to see how a specific automation is wired up.

### get_flows
List all active flow configurations currently running in your instance. Use this to get a bird's-eye view of your entire setup.

### get_nodes
See a list of all installed node modules available in your palette. This lets you know what capabilities you already have ready to go.

### install_node
Install new npm packages to expand your Node-RED capabilities. You can add new functionality to your instance without leaving your chat.

### remove_node
Uninstall and remove node modules you no longer need. This keeps your environment clean and prevents clutter in your palette.

### set_flows
Apply a new flow configuration to your active environment. It's perfect for pushing updates across your setup instantly.

### get_settings
View your Node-RED runtime settings and environment constraints. This gives you the context you need to understand your system's limits.

### update_flow
Modify an existing flow configuration with specific changes. Use this to tweak individual parts of your logic without rewriting everything.

### add_flow
Create and add a new flow configuration to your instance. This makes it easy to spin up new automations on the fly.

### delete_flow
Remove a specific flow configuration from your active workspace. Use this to clean up old logic or delete unused tabs.

## Prompt Examples

**Prompt:** 
```
Show me all active flows.
```

**Response:** 
```
I've retrieved your flows. You have 3 main tabs: **Home Automation** (ID: f123), **Data Logger** (ID: f456), and **Alerts** (ID: f789). Would you like to inspect a specific one?
```

**Prompt:** 
```
Check the system diagnostics and memory usage.
```

**Response:** 
```
Diagnostics report:
- **Node.js**: v18.16.0
- **OS**: Linux
- **Memory**: 150MB of 512MB allocated

The system is healthy.
```

**Prompt:** 
```
Install the 'node-red-node-email' module.
```

**Response:** 
```
Starting installation of 'node-red-node-email'... 

✅ The module has been successfully installed and is now available in your palette.
```

## Capabilities

### Update flow configurations
Modify specific parts of your automation logic without manual JSON editing.

### Install npm node modules
Add new functionality to your palette via natural language commands.

### Check system health
See memory usage and Node.js versions instantly to spot performance issues.

### Add new flows
Create and add new automation tabs to your instance on the fly.

### Delete old flows
Remove unused logic and clean up your workspace by deleting flows.

## Use Cases

### Checking for memory spikes
An engineer asks their agent to check if the system is overloaded. The agent runs get_diagnostics and reports memory usage on the Linux instance.

### Adding a new automation tab
A user needs a new flow for a garage door. They tell the agent to add a flow, and it creates the configuration automatically.

### Installing missing modules
A developer needs to send emails but doesn't have the node. They ask the agent to install the 'node-red-node-email' module into the palette.

### Inspecting specific flow logic
Someone wants to see how the 'Alerts' tab is wired. The agent uses get_flow to pull the configuration and explain the triggers.

## Benefits

- Stop hunting through tabs. Use get_flows and get_flow to find exactly what you need in seconds.
- Deploy logic faster. Use add_flow and set_flows to push updates without manual copy-pasting.
- Manage dependencies easily. Use install_node and remove_node to keep your palette clean and updated.
- Monitor health instantly. Use get_diagnostics to check memory and OS stats without opening the dashboard.
- Understand your environment. Use get_settings to see runtime constraints and user info at a glance.
- Simplify debugging. Use get_nodes and get_flow to quickly verify that the right modules are active and configured correctly.

## How It Works

The bottom line is you can manage your entire Node-RED setup through a simple conversation.

1. Subscribe to this Connector and grab your Node-RED Base URL and Access Token.
2. Connect your AI client to the Connector and provide the credentials.
3. Start asking your agent to modify flows or check system stats.

## Frequently Asked Questions

**Can I use Node-RED MCP to manage my IoT flows?**
Yes, it lets you interact with flows via your AI client. You can add, update, or delete flows using natural language instead of clicking through the dashboard.

**How do I install new nodes using Node-RED MCP?**
Just ask your agent to install a specific npm package. It will handle the installation for you and make it available in your palette.

**Can Node-RED MCP check my server's memory?**
Yes, it pulls system diagnostics including memory usage. This helps you monitor your instance's performance in real time.

**Is this good for managing multiple Node-RED instances?**
Yes, you can query settings and flows across different environments. It makes managing a fleet of instances much faster.

**Do I need to open the Node-RED editor to see my flows?**
No, your AI agent can fetch and display them for you. This saves you from having to navigate the visual editor for every check.

**Can I add new flows to my Node-RED instance?**
Yes, your agent can create and add new flow configurations directly. Just describe what you want the new flow to do.

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