node-red-contrib

This MCP server package for Node-RED provides nodes to manage MCP servers, connect as clients, and invoke MCP tools directly within Node-RED flows. It supports multiple connection types (HTTP, Server-Sent Events, and WebSocket) and includes health checks, real-time output streaming, and Omnispindle tool presets. Use the MCP Server Node to start, stop, and monitor MCP server processes; use the MCP Client Node to connect to running MCP servers and issue requests or subscribe to events; and use the MCP Tool Node to invoke predefined MCP tools with parameter mapping and optional overrides. The quick-start flows demonstrate connecting to an external Omnispindle MCP server, hosting a server entirely inside Node-RED, and discovering or invoking tools on the target server. The package also exposes example flows for common scenarios like tool invocation, dynamic tool discovery, and health-based restart handling.

Prerequisites:

• Node.js 16+ and Node-RED 1.0+ installed on your system
• Access to the Node-RED user directory (commonly ~/.node-red)

Installation steps:

1. From npm (recommended when published):

cd ~/.node-red
npm install node-red-contrib-mcp-server

2. Manual installation (clone and install):

cd ~/.node-red
git clone <repository-url> node_modules/node-red-contrib-mcp-server
cd node_modules/node-red-contrib-mcp-server
npm install

3. Local development workflow:

cd /path/to/node-red-contrib-mcp-server
npm link
cd ~/.node-red
npm link node-red-contrib-mcp-server

After installation, restart Node-RED to load the new nodes.

Notes and tips:

• The MCP Server Node manages lifecycle, health checks, and real-time output for MCP server processes (Python, Node.js, or custom commands).
• Ensure your server path and environment are correctly configured, especially for Python servers requiring dependencies.
• The Omnispindle presets simplify configuring a local Omnispindle MCP server and its tools.
• Refer to the examples folder for ready-made flows to connect to external MCP servers or to run a flow-based MCP server entirely within Node-RED.
• Common issues include port conflicts, missing executable permissions, and mismatched Node.js versions. Check the server logs and enable verbose/log level settings for troubleshooting.