Skip to main content
Glama
supcon-international

@supcon-international/node-red-mcp-server

by supcon-international
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @supcon-international/node-red-mcp-server

No user-submitted related servers found.

    Related Servers

    • node-red-mcp

      ziv-daniel
      F
      license
      Not graded
      quality
      A
      maintenance
      A 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
      -

    • nodered-mcp

      indigo323
      F
      license
      Not graded
      quality
      B
      maintenance
      Minimal MCP server wrapping the Node-RED admin API, enabling flow management, node installation, and context retrieval via natural language.
      -

    • n8n MCP Server

      illuminaresolutions
      A
      license
      B
      quality
      D
      maintenance
      An MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).
      33
      50 npm
      118
      MIT

    • nodered-mcp

      ylt
      F
      license
      B
      quality
      D
      maintenance
      A Python MCP server that provides language models full read/write access to a Node-RED instance through its Admin HTTP API, enabling flow management with structured Pydantic responses and incremental patching.
      22
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 27 tools

    Disambiguation3/5

    Some tools overlap in purpose, e.g., 'find-nodes-by-type' and 'search-nodes' both search nodes, and there are multiple 'get-flows' variants (get-flows, get-flows-formatted, get-flows-state) which could confuse an agent. However, most tools target distinct operations.

    Naming Consistency2/5

    Naming is inconsistent: most tools use verb_noun (e.g., create-flow, delete-flow), but some deviate with prepositions (find-nodes-by-type), adjectives (get-flows-formatted), or single verbs (inject). The pattern is not uniform.

    Tool Count3/5

    27 tools is on the high side for a server, but the domain (Node-RED administration) is broad enough to warrant many tools. However, some tools like get-node-detailed-info and get-node-set-detailed-info could be consolidated.

    Completeness4/5

    The tool set covers most common Node-RED admin operations: flow CRUD, backups, node management, diagnostics, and settings. Missing uninstall-node-module and maybe credential management, but these are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources