node-red-mcp-server
Related Servers
Alternatives to node-red-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceModel Context Protocol (MCP) server for Node-RED that allows language models to interact with Node-RED through a standardized API.27264MIT
- FlicenseNot gradedqualityAmaintenanceA Model Context Protocol server for Node-RED integration, enabling AI agents to manage flows, install modules, and monitor Node-RED instances via natural language.5-
- FlicenseNot gradedqualityBmaintenanceMinimal MCP server wrapping the Node-RED admin API, enabling flow management, node installation, and context retrieval via natural language.-
- AlicenseBqualityDmaintenanceAn MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).3348119MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that generates production-ready n8n workflows from natural language prompts. Transform simple descriptions into fully validated, deployable automation workflows using AI-powered code generation.1-
- AlicenseNot gradedqualityBmaintenanceTurns Node-RED flows into OAuth-protected MCP tools that AI assistants can call, with optional read-only access to the Node-RED admin API.ISC
TDQS
Scored across 20 tools
Without descriptions, several tools appear to have overlapping purposes (e.g., get-flows, get-flows-formatted, get-flows-state; search-nodes and find-nodes-by-type). This ambiguity could cause an agent to select the wrong tool.
All tool names follow a consistent hyphen-case pattern with a clear verb_noun structure (e.g., create-flow, get-flows, set-flows-state). The naming is uniform and predictable.
With 20 tools, the server covers a broad range of Node-RED operations. While the count is slightly high, it remains within a reasonable scope for a comprehensive administration tool.
The tool set includes flow CRUD, node management, state control, diagnostics, and settings. However, operations like flow export/import or detailed debugging are missing, leaving notable gaps for full lifecycle management.