# MCP server that lets AI agents read, edit, and deploy Node-RED flows

**URL:** <https://discourse.nodered.org/t/mcp-server-that-lets-ai-agents-read-edit-and-deploy-node-red-flows/101890>\
**Category:** Share Your Projects\
**Created:** [9 October 2026 23:30 UTC](https://discourse.nodered.org/t/mcp-server-that-lets-ai-agents-read-edit-and-deploy-node-red-flows/101890 "2026-10-09T23:30:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ljmerza](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ljmerza/32/108519_2.png) [@ljmerza](https://discourse.nodered.org/u/ljmerza)\
**Post date:** [9 October 2026 23:30 UTC](https://discourse.nodered.org/t/mcp-server-that-lets-ai-agents-read-edit-and-deploy-node-red-flows/101890/1 "2026-10-09T23:30:00Z")

</div>

An open-source MCP server that lets AI clients interact with Node-RED through structured tools.

What it can do:

- 🔎 Understand existing flows — search nodes, inspect connections, trace wires, and explore tabs and groups.
- 🛠 Edit flows — create, update, delete, duplicate, and rewire nodes.
- 📐 Manage layouts — find free canvas space, detect overlapping nodes, and organize groups.
- 📦 Batch changes — make multiple edits and deploy them together instead of applying every change immediately.
- ↩ Review and undo — inspect diffs before deployment and roll back individual edits.
- 🛡 Prevent accidental overwrites — detect stale changes and block edits that introduce new layout collisions.

It connects directly to a running Node-RED instance through the Admin API, so you don't need filesystem access to the Node-RED host. It also supports working directly with a "flows.json" file.

You can run it with "uvx nodered-mcp", and it works with MCP-compatible clients.

GitHub: [GitHub - ljmerza/nodered-mcp: MCP server for reading, querying, and editing a Node-RED flows.json · GitHub](https://github.com/ljmerza/nodered-mcp)