# \[Announce\] @frtnbach/node-red-contrib-mcp-server

**URL:** <https://discourse.nodered.org/t/announce-frtnbach-node-red-contrib-mcp-server/101439>\
**Category:** Share Your Nodes\
**Tags:** docker, home-assistant, ai\
**Created:** [10 July 2026 07:47 UTC](https://discourse.nodered.org/t/announce-frtnbach-node-red-contrib-mcp-server/101439 "2026-07-10T07:47:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fredrik](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fredrik/32/107652_2.png) [@Fredrik](https://discourse.nodered.org/u/Fredrik)\
**Post date:** [10 July 2026 07:47 UTC](https://discourse.nodered.org/t/announce-frtnbach-node-red-contrib-mcp-server/101439/1 "2026-07-10T07:47:49Z")

</div>

I've been having some fun with Claude and my home automation setup, as mentioned [here](https://discourse.nodered.org/t/ai-home-automation-digital-assistant/101338). I realised that there might be some value to a more generic AI -\> Node-RED connection, not directly related to home automation specifically, so I created [@frtnbach/node-red-contrib-mcp-server](https://github.com/flic/node-red-contrib-mcp-server).

It's a generic building block for turning Node-RED flows into MCP server tools: expose any flow as an MCP tool behind an OAuth-protected endpoint, with optional Node-RED admin (flow read/deploy) tools. No home automation or other domain coupling — this is a bare-bones way to let AI assistants (Claude, etc.) call your flows as tools.

I've included a few examples to show how it's done: Jellyfin, Calibre, Docker (be careful with this one), Music Assistant, Radarr, iRobot/rest980, Overseerr, Sonarr and Spotify. Not all of them are necessarily useful, but the fun part is playing around and seeing what sticks, right? 😉