[{"data":1,"prerenderedAt":174},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F01\u002Fflowfuse-release-2-26":3},{"id":4,"title":5,"body":6,"description":12,"extension":163,"meta":164,"navigation":169,"path":170,"seo":171,"stem":172,"__hash__":173},"blog\u002Fblog\u002F2026\u002F01\u002Fflowfuse-release-2-26.md","FlowFuse 2.26: Bringing access-controls to your MCP nodes",{"type":7,"value":8,"toc":152},"minimark",[9,13,18,27,30,33,36,39,50,54,57,74,82,91,95,105,113,116,120,125,128,136,140],[10,11,12],"p",{},"With the holiday break sitting in the middle of this release cycle, it's a smaller release than usual this month. But that hasn't stopped us continuing to make the FlowFuse Expert even more useful.",[14,15,17],"h2",{"id":16},"role-based-access-control-for-your-mcp-tools","Role-based access control for your MCP tools",[10,19,20,21,26],{},"Following on the the introduction of ",[22,23,25],"a",{"href":24},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights\u002F","FlowFuse Expert MCP-Powered Insights"," we have added annotations to the FlowFuse MCP nodes and linked them up with the FlowFuse roles.\nThis permits a level of control over who can access what. This is just a first step, we will be working in the area over the next few iterations.",[10,28,29],{},"The MCP nodes now allow you to set some standard annotations to give the platform a hint as to what type of action the node performs. This lets you separate tools that provide read-only information from those that make potentially-destructive changes.",[10,31,32],{},"Within the FlowFuse team, you can then use the granular RBAC feature to configure what users have access to the different types of node.",[10,34,35],{},"For example, Viewer role users can have access to read-only nodes, whilst Owners get to access the full range of tools. These roles can be customised for each Application within the team.",[10,37,38],{},"The annotations we apply are part of the MCP standard, so will be recognised by your own Agents and LLMs.",[10,40,41,47],{},[42,43],"img",{"alt":44,"dataZoomable":45,"src":46},"MCP Server Tool Node with new annotations","","\u002Fblog\u002F2026\u002F01\u002Fimages\u002Fmcp-annotations.png",[48,49,44],"em",{},[14,51,53],{"id":52},"integrating-flowfuse-expert-with-node-red","Integrating FlowFuse Expert with Node-RED",[10,55,56],{},"This release also brings some new abilities for the FlowFuse Expert to help you do things inside Node-RED itself.",[58,59,60,68],"ul",{},[61,62,63,67],"li",{},[64,65,66],"strong",{},"Streamlined Node Installation:"," When the Expert suggests a node module, it can now automatically open the Palette Manager and filter for the correct package, leaving you just one click away from installation.",[61,69,70,73],{},[64,71,72],{},"Direct Flow Imports:"," When the Expert provides demo flows, you no longer need to copy-paste JSON. The Expert can now inject those flows directly into your editor, ready for deployment.",[10,75,76,77,81],{},"Make sure you've updated the ",[78,79,80],"code",{},"@flowfuse\u002Fnr-assistant"," module inside your instance to unlock these new capabilities.",[10,83,84,88],{},[42,85],{"alt":86,"dataZoomable":45,"src":87},"FlowFuse Expert Install Node","\u002Fblog\u002F2026\u002F01\u002Fimages\u002Fff-expert-install-node.gif",[48,89,90],{},"FlowFuse Expert integration with the Palette Manager",[14,92,94],{"id":93},"what-else-is-new","What else is new?",[10,96,97,98,104],{},"For a complete list of everything included in our 2.26 release, check out the ",[22,99,103],{"href":100,"rel":101},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Freleases\u002Ftag\u002Fv2.26.0",[102],"nofollow","release notes",".",[10,106,107,108,104],{},"Your feedback continues to be invaluable in shaping FlowFuse's development. We'd love to hear your thoughts on these new features and any suggestions for future improvements. Please share your experiences or report any ",[22,109,112],{"href":110,"rel":111},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002Fnew\u002Fchoose",[102],"issues on GitHub",[10,114,115],{},"Which of these new features are you most excited to try? Reach out on GitHub or social media!",[14,117,119],{"id":118},"try-flowfuse","Try FlowFuse",[121,122,124],"h3",{"id":123},"flowfuse-cloud","FlowFuse Cloud",[10,126,127],{},"The quickest way to get started is with FlowFuse Cloud.",[10,129,130,135],{},[22,131,134],{"href":132,"rel":133},"https:\u002F\u002Fapp.flowfuse.com\u002Faccount\u002Fcreate",[102],"Get started for free"," and have your Node-RED instances running in the cloud within minutes.",[121,137,139],{"id":138},"self-hosted","Self-Hosted",[10,141,142,143,147,148,104],{},"Get FlowFuse running locally in under 30 minutes using ",[22,144,146],{"href":145},"\u002Fdocs\u002Finstall\u002Fdocker\u002F","Docker"," or ",[22,149,151],{"href":150},"\u002Fdocs\u002Finstall\u002Fkubernetes\u002F","Kubernetes",{"title":45,"searchDepth":153,"depth":153,"links":154},2,[155,156,157,158],{"id":16,"depth":153,"text":17},{"id":52,"depth":153,"text":53},{"id":93,"depth":153,"text":94},{"id":118,"depth":153,"text":119,"children":159},[160,162],{"id":123,"depth":161,"text":124},3,{"id":138,"depth":161,"text":139},"md",{"navTitle":5,"excerpt":165},{"type":7,"value":166},[167],[10,168,12],{},true,"\u002Fblog\u002F2026\u002F01\u002Fflowfuse-release-2-26",{"title":5,"description":12},"blog\u002F2026\u002F01\u002Fflowfuse-release-2-26","xyh0TMJOjFkkHO4SmxRtT5k9t2jXQXqpdgIt9wyQlR8",1780070553995]