node-red-ai-access MCP server

Q: How do I add node-red-ai-access MCP to Claude Code?

Run `claude mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access` in your terminal. Add `--scope user` to make it available in every project.

Q: How do I add node-red-ai-access MCP to Cursor?

Open `~/.cursor/mcp.json` and add the server under `mcpServers`, using the Cursor config shown in the install section above.

✓ VerifiedCommit Nov 11, 2026

com55/node-red-ai-access · typescript · MIT

Provides AI agents with temporary, owner-approved access to Node-RED flows via MCP, REST, or GET links.

Also known as com55/node-red-ai-access, @com55/node-red-ai-access

stdio Developer Tools No API key

Install GitHub ↗

Stars: 1
Tools: —
Downloads, 30 days: 2,297
Latest version: —
Last commit: Nov 11, 2026
License: MIT

What is node-red-ai-access MCP?

node-red-ai-access provides AI agents with temporary, owner-approved access to Node-RED flows via MCP, REST, or GET links.

Summary generated from the project's README

About node-red-ai-access MCP server

Granting AI agents controlled, temporary access to Node-RED flows is the primary function of this Node-RED 4.x+ plugin. It allows developers to provide AI clients with specific interaction channels through an MCP JSON-RPC endpoint, a versioned REST API, or simple HTTP GET links. This setup ensures that any changes suggested by an AI are treated as proposals rather than immediate mutations, requiring human approval through an admin dashboard located at the /ai-access path.

Users manage these interactions via a Git-inspired mental model where AI suggestions act like pull requests. Administrators can review readable node and property diffs, approve them to deploy changes, or reject them to keep the live flow untouched. The system supports different token types for various client capabilities, including specialized links for chat AIs that only support GET requests. Security is maintained through configurable time-to-live settings, with GET links capped at 24 hours and MCP or REST links lasting up to 30 days.

What you can do with it

1Reviewing AI flow changesA developer can inspect a readable diff of node properties before deciding whether to merge an AI's suggestion into the live environment.
2Connecting chat-based AI clientsYou can provide a simple link to a chat AI that only supports HTTP GET requests to allow it to interact with your flows.
3Managing automated agent accessDevelopers can issue specific tokens for MCP or REST clients to enable structured JSON-RPC communication.
4Auditing agent activityAdministrators can track all interactions and changes made by AI agents through a dedicated log.

Written from the project's README. Every use case is checked against a quote from it.

How to install node-red-ai-access MCP

Formats verified 10 Nov 2026Add to Cursor Add to Goose

Claude CodeCursorVS CodeVS Code CLIClaude DesktopCodexCodex config.tomlGemini CLIGemini settings.json

$ claude mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access

~/.cursor/mcp.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "node-red-ai-access": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

$ code --add-mcp '{"name":"node-red-ai-access","type":"stdio","command":"npx","args":["-y","@com55/node-red-ai-access"]}'

claude_desktop_config.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

$ codex mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access

~/.codex/config.toml

[mcp_servers.node-red-ai-access]
command = "npx"
args = ["-y", "@com55/node-red-ai-access"]

$ gemini mcp add -s user node-red-ai-access npx -- -y @com55/node-red-ai-access

~/.gemini/settings.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

No environment variables or API keys required.Setup guides:Claude Code Cursor VS Code Claude Desktop

Automated checks

Ran Nov 13, 2026Full report →

100/100

Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work

Show this score in your README

Source repository linked and reachablePass
Open source license (OSI)Pass
Commit or release in the last yearPass
Package name not close to a popular packagePass
Remote endpoint uses HTTPSNot checked
Destructive tools are labelledNot checked
No hidden instructions to the modelPass
No critical advisory in the package or its dependenciesNot checked

README

View on GitHub

Node-RED AI Access

Temporary, owner-approved Node-RED access for AI clients. Ships as a Node-RED 4.x+ plugin with:

an admin dashboard at /ai-access (browser GET /mcp redirects there)
a versioned REST API under /mcp/api/v1
an MCP JSON-RPC endpoint at /mcp/rpc (Streamable HTTP) over the same services

Git mental model: a proposal is like a pull request. Human approve = merge; reject = close; withdraw = the author closes their own PR. Revision changes auto-rebase open proposals. A conflict blocks approval until resolved. Open proposals expire after a configurable TTL (default 7 days). Every access link can see all proposals (mine: true|false).

Derived from ziv-daniel/node-red-mcp.

Install (Node-RED plugin)

Requirements: Node-RED 4.x or newer, Node.js 20.19+ (tested: Node-RED 4.1 on Node 20/22, Node-RED 5.0 on Node 22/24), and adminAuth enabled (recommended). Without adminAuth, AI features stay off unless you opt in; see Configuration.

In the Node-RED Palette Manager, choose Menu → Manage palette → Install, then search for @com55/node-red-ai-access.
Or install with npm in your Node-RED user directory:
```
cd ~/.node-red
npm install @com55/node-red-ai-access
```
Stable releases use npm. From 0.2.0-beta.12 onward, pre-releases are .tgz files available only as GitHub Release assets, not on npm. Pick a version from GitHub Releases and use its exact install command from the release notes. For example, replace X.Y.Z with the full version, including its pre-release suffix (/data is typical for Docker; otherwise use ~/.node-red):
```
cd /data && npm i https://github.com/com55/node-red-ai-access/releases/download/vX.Y.Z/com55-node-red-ai-access-X.Y.Z.tgz
```
Restart Node-RED.

Quick start

Log in to the editor, then open /ai-access on the admin root (for example http://localhost:1880/ai-access, or {httpAdminRoot}/ai-access when httpAdminRoot is set), or click Open AI Access dashboard in the editor sidebar. Opening /mcp in a browser redirects to the dashboard (MCP clients keep using /mcp).
Create an access token on the dashboard's Access tokens tab (admin * only). Choose the token kind for your client.
Either connect an MCP client or give an AI the full GET link. Changes become pending proposals for human review and approval.

Choose a channel

Prefer MCP or REST when your client can send custom headers and JSON bodies. Use a GET link for chat AIs that can only HTTP GET. Each token works on one surface; choose mcp, rest, or get_link to match the client.

Copy the token when it is created: it is shown only once. Access links are in memory and become invalid after a Node-RED restart. The default TTL is 4 hours; GET links are capped at 24 hours, REST / MCP links at 30 days.

Review changes

The AI reads flows and submits proposals. Open Proposals on the dashboard to review the readable node/property diff against the live flow, then approve or reject. Approval deploys the changes; rejection never mutates flows.

Users with read (including guest, if configured) have a read-only view. Creating or revoking access links and approving or rejecting proposals require * permission. The Audit log tab records activity for review.

See the AI quickstart for GET links and Bearer REST / MCP examples, and the dashboard guide for sign-in, tabs, and permissions.

Docs

Document	Description
Channel index	GET link / REST / MCP overview
Dashboard	Sign-in, tabs, and permissions
Configuration	Settings, proxy URLs, CORS, redaction, and storage
MCP OAuth	Endpoints, consent, token lifetimes, and public exposure
REST API	Routes, MCP JSON-RPC, proposals, and runtime adapters
AI quickstart	GET links, Bearer REST / MCP, and examples
MCP client setup	Claude Desktop, Cursor, VS Code, and CLI
MCP tools reference	Generated from live `tools/list`
Error codes	Code, HTTP status, meaning, hint, and channels
Development	Build, test, quality, and generated references
Releasing	Versioning, release assets, and npm publishing
OpenAPI 3.1	Also served at `GET /mcp/api/v1/openapi.yaml` and `GET /mcp/api/v1/openapi.json`

Development

Build and test with yarn; see Development for commands and generated reference checks.

License

MIT — see LICENSE.

Read full README

node-red-ai-access MCP questions

How do I add node-red-ai-access MCP to Claude Code?

Run claude mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access in your terminal. Add --scope user to make it available in every project.

How do I add node-red-ai-access MCP to Cursor?

Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.

What are the different ways an AI client can connect?

Clients can connect using MCP, a versioned REST API, or a simple GET link for chat AIs that only support HTTP GET.

How are changes made by the AI applied to my flows?

The AI submits proposals that appear on the admin dashboard; a human must review the diff and approve the proposal to deploy the changes.

How long do access links last?

Default TTL is 4 hours, but GET links are capped at 24 hours, while REST and MCP links can last up to 30 days.

Facts

Nov 14, 2026

Stars: 1
Downloads, 30 days: 2,297
Latest version: —
Last commit: Nov 11, 2026
License: MIT
Transport: stdio
Package: @com55/node-red-ai-access

com55 ↗

Community publisher

Published by an independent maintainer.

Alternatives

Works with

Claude Code Cursor VS Code Claude Desktop Codex Gemini CLI Windsurf Devin

Badge for your README

Show your HostedMCP checks score. The badge links readers to install instructions for every client.

[![HostedMCP checks](https://api.hostedmcp.org/v1/badge/server/com55/node-red-ai-access.svg)](https://hostedmcp.org/servers/com55/node-red-ai-access/checks)

Maintainer?

Claim this listing to edit it and add the HostedMCP badge to your README.

Claim listing

Before you install

Servers run with the permissions you give them. Use the narrowest token or database role that does the job.

node-red-ai-access MCP server

✓ VerifiedCommit Nov 11, 2026

com55/node-red-ai-access · typescript · MIT

Provides AI agents with temporary, owner-approved access to Node-RED flows via MCP, REST, or GET links.

Also known as com55/node-red-ai-access, @com55/node-red-ai-access

stdio Developer Tools No API key

Install GitHub ↗

Stars: 1
Tools: —
Downloads, 30 days: 2,297
Latest version: —
Last commit: Nov 11, 2026
License: MIT

What is node-red-ai-access MCP?

node-red-ai-access provides AI agents with temporary, owner-approved access to Node-RED flows via MCP, REST, or GET links.

Summary generated from the project's README

About node-red-ai-access MCP server

What you can do with it

1Reviewing AI flow changesA developer can inspect a readable diff of node properties before deciding whether to merge an AI's suggestion into the live environment.
2Connecting chat-based AI clientsYou can provide a simple link to a chat AI that only supports HTTP GET requests to allow it to interact with your flows.
3Managing automated agent accessDevelopers can issue specific tokens for MCP or REST clients to enable structured JSON-RPC communication.
4Auditing agent activityAdministrators can track all interactions and changes made by AI agents through a dedicated log.

Written from the project's README. Every use case is checked against a quote from it.

How to install node-red-ai-access MCP

Formats verified 10 Nov 2026Add to Cursor Add to Goose

Claude CodeCursorVS CodeVS Code CLIClaude DesktopCodexCodex config.tomlGemini CLIGemini settings.json

$ claude mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access

~/.cursor/mcp.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "node-red-ai-access": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

$ code --add-mcp '{"name":"node-red-ai-access","type":"stdio","command":"npx","args":["-y","@com55/node-red-ai-access"]}'

claude_desktop_config.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

$ codex mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access

~/.codex/config.toml

[mcp_servers.node-red-ai-access]
command = "npx"
args = ["-y", "@com55/node-red-ai-access"]

$ gemini mcp add -s user node-red-ai-access npx -- -y @com55/node-red-ai-access

~/.gemini/settings.json

{
  "mcpServers": {
    "node-red-ai-access": {
      "command": "npx",
      "args": [
        "-y",
        "@com55/node-red-ai-access"
      ]
    }
  }
}

No environment variables or API keys required.Setup guides:Claude Code Cursor VS Code Claude Desktop

Automated checks

Ran Nov 13, 2026Full report →

100/100

Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work

Show this score in your README

Source repository linked and reachablePass
Open source license (OSI)Pass
Commit or release in the last yearPass
Package name not close to a popular packagePass
Remote endpoint uses HTTPSNot checked
Destructive tools are labelledNot checked
No hidden instructions to the modelPass
No critical advisory in the package or its dependenciesNot checked

README

View on GitHub

Node-RED AI Access

Temporary, owner-approved Node-RED access for AI clients. Ships as a Node-RED 4.x+ plugin with:

an admin dashboard at /ai-access (browser GET /mcp redirects there)
a versioned REST API under /mcp/api/v1
an MCP JSON-RPC endpoint at /mcp/rpc (Streamable HTTP) over the same services

Derived from ziv-daniel/node-red-mcp.

Install (Node-RED plugin)

In the Node-RED Palette Manager, choose Menu → Manage palette → Install, then search for @com55/node-red-ai-access.
Or install with npm in your Node-RED user directory:
```
cd ~/.node-red
npm install @com55/node-red-ai-access
```
Stable releases use npm. From 0.2.0-beta.12 onward, pre-releases are .tgz files available only as GitHub Release assets, not on npm. Pick a version from GitHub Releases and use its exact install command from the release notes. For example, replace X.Y.Z with the full version, including its pre-release suffix (/data is typical for Docker; otherwise use ~/.node-red):
```
cd /data && npm i https://github.com/com55/node-red-ai-access/releases/download/vX.Y.Z/com55-node-red-ai-access-X.Y.Z.tgz
```
Restart Node-RED.

Quick start

Log in to the editor, then open /ai-access on the admin root (for example http://localhost:1880/ai-access, or {httpAdminRoot}/ai-access when httpAdminRoot is set), or click Open AI Access dashboard in the editor sidebar. Opening /mcp in a browser redirects to the dashboard (MCP clients keep using /mcp).
Create an access token on the dashboard's Access tokens tab (admin * only). Choose the token kind for your client.
Either connect an MCP client or give an AI the full GET link. Changes become pending proposals for human review and approval.

Choose a channel

Review changes

See the AI quickstart for GET links and Bearer REST / MCP examples, and the dashboard guide for sign-in, tabs, and permissions.

Docs

Document	Description
Channel index	GET link / REST / MCP overview
Dashboard	Sign-in, tabs, and permissions
Configuration	Settings, proxy URLs, CORS, redaction, and storage
MCP OAuth	Endpoints, consent, token lifetimes, and public exposure
REST API	Routes, MCP JSON-RPC, proposals, and runtime adapters
AI quickstart	GET links, Bearer REST / MCP, and examples
MCP client setup	Claude Desktop, Cursor, VS Code, and CLI
MCP tools reference	Generated from live `tools/list`
Error codes	Code, HTTP status, meaning, hint, and channels
Development	Build, test, quality, and generated references
Releasing	Versioning, release assets, and npm publishing
OpenAPI 3.1	Also served at `GET /mcp/api/v1/openapi.yaml` and `GET /mcp/api/v1/openapi.json`

Development

Build and test with yarn; see Development for commands and generated reference checks.

License

MIT — see LICENSE.

Read full README

node-red-ai-access MCP questions

How do I add node-red-ai-access MCP to Claude Code?

Run claude mcp add node-red-ai-access -- npx -y @com55/node-red-ai-access in your terminal. Add --scope user to make it available in every project.

How do I add node-red-ai-access MCP to Cursor?

Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.

What are the different ways an AI client can connect?

Clients can connect using MCP, a versioned REST API, or a simple GET link for chat AIs that only support HTTP GET.

How are changes made by the AI applied to my flows?

The AI submits proposals that appear on the admin dashboard; a human must review the diff and approve the proposal to deploy the changes.

How long do access links last?

Default TTL is 4 hours, but GET links are capped at 24 hours, while REST and MCP links can last up to 30 days.

Facts

Nov 14, 2026

Stars: 1
Downloads, 30 days: 2,297
Latest version: —
Last commit: Nov 11, 2026
License: MIT
Transport: stdio
Package: @com55/node-red-ai-access

com55 ↗

Community publisher

Published by an independent maintainer.

Alternatives

Works with

Claude Code Cursor VS Code Claude Desktop Codex Gemini CLI Windsurf Devin

Badge for your README

Show your HostedMCP checks score. The badge links readers to install instructions for every client.

[![HostedMCP checks](https://api.hostedmcp.org/v1/badge/server/com55/node-red-ai-access.svg)](https://hostedmcp.org/servers/com55/node-red-ai-access/checks)

Maintainer?

Claim this listing to edit it and add the HostedMCP badge to your README.

Claim listing

Before you install

Servers run with the permissions you give them. Use the narrowest token or database role that does the job.

node-red-ai-access MCP server

What is node-red-ai-access MCP?

About node-red-ai-access MCP server

What you can do with it

How to install node-red-ai-access MCP

Install node-red-ai-access MCP in Claude Code

Install node-red-ai-access MCP in Cursor

Install node-red-ai-access MCP in VS Code

Install node-red-ai-access MCP in VS Code CLI

Install node-red-ai-access MCP in Claude Desktop

Install node-red-ai-access MCP in Codex

Install node-red-ai-access MCP in Codex config.toml

Install node-red-ai-access MCP in Gemini CLI

Install node-red-ai-access MCP in Gemini settings.json

Automated checks

README

Node-RED AI Access

Install (Node-RED plugin)

Quick start

Choose a channel

Review changes

Docs

Development

License

node-red-ai-access MCP questions

node-red-ai-access MCP server

What is node-red-ai-access MCP?

About node-red-ai-access MCP server

What you can do with it

How to install node-red-ai-access MCP

Install node-red-ai-access MCP in Claude Code

Install node-red-ai-access MCP in Cursor

Install node-red-ai-access MCP in VS Code

Install node-red-ai-access MCP in VS Code CLI

Install node-red-ai-access MCP in Claude Desktop

Install node-red-ai-access MCP in Codex

Install node-red-ai-access MCP in Codex config.toml

Install node-red-ai-access MCP in Gemini CLI

Install node-red-ai-access MCP in Gemini settings.json

Automated checks

README

Node-RED AI Access

Install (Node-RED plugin)

Quick start

Choose a channel

Review changes

Docs

Development

License

node-red-ai-access MCP questions