docs: add FlowFuse MCP server capabilities page - #8516
Conversation
New page docs/user/mcp.md covering the platform automation actions available over MCP by resource and access level, flow building in the Node-RED editor, and the read-only and full-access permission levels. The Expert overview and connect-your-own-agent pages link to it.
Describe the two access levels per client: FlowFuse Expert acts with the user's own team access, while a connected agent chooses read-only or full access, team scope and an expiration at OAuth sign-in. Use read-only and full access consistently, and drop the deletion note.
Rewrite the Expert overview and the connect-your-own-agent pages in the terser reference style, cutting narration and salesy framing. Point the capability and flow building descriptions at the MCP server page instead of repeating them, so the surface has a single source.
| ### Chat Interface | ||
|
|
||
| The Chat Interface is a conversational AI panel built into the FlowFuse Platform and accessible directly within the Node-RED editor. With agentic flow building enabled, you can describe what you want to build and Expert will build it on your canvas for you. It can also answer questions, debug flows, and query live operational data via MCP. | ||
| The Chat Interface is a conversational AI panel in the FlowFuse platform, also available inside the Node-RED editor. Describe what you want to build and Expert builds it on your canvas. It also answers questions, debugs flows, and queries live operational data. |
There was a problem hiding this comment.
This is missleading, the expert is not available in the node-red editor, it's available in the flowfuse immersive mode which embeds the node-red editor
There was a problem hiding this comment.
Fixed. It now reads available in immersive mode, which embeds the Node-RED editor.
| Each FlowFuse tool carries its recommended usage and permissions, so a connected agent knows what it is for before calling it. Most MCP clients then ask you to confirm before running a tool. That prompt is the client's, not FlowFuse's, so its look and whether you can turn it off vary. FlowFuse Expert's own approval cards do not apply here. | ||
|
|
||
| What FlowFuse enforces on every call is what you granted: the teams, and read access or editing rights. That is the granularity. It is a boundary around what an agent can reach rather than a per-tool allow list, and it applies the same way whether the grant came from signing in or from the scope on an access token. | ||
| What FlowFuse enforces on every call is your grant: the teams, and read-only or full access. It is a boundary around what an agent can reach, not a per-tool allow list, and applies the same whether the grant came from signing in or from a token's scope. |
There was a problem hiding this comment.
It kind of is a per tool allow list, we prohibit tool invocation if the tool scope does not match the token's grant (team and read/write)
There was a problem hiding this comment.
Corrected. Dropped the not a per-tool allow list line; it now says FlowFuse rejects a call whose tool reaches past your grant.
|
|
||
| # FlowFuse MCP Server | ||
|
|
||
| FlowFuse is an MCP server. An AI agent connects as a client to operate the platform and build flows. |
There was a problem hiding this comment.
FlowFuse exposes an mcp server
There was a problem hiding this comment.
Reworded to FlowFuse exposes an MCP server.
|
|
||
| | Resource | Read-only | Full access | | ||
| |---|---|---| | ||
| | Teams | Members and roles, invitations, audit log, resource counts, bill of materials | Create a team, update settings, change member roles, invite and re-invite members | |
There was a problem hiding this comment.
we should postpone mergeing this until we have the complete set of tools in
Reword the opener to say FlowFuse exposes an MCP server, place the Chat panel in immersive mode which embeds the Node-RED editor, and describe grant enforcement as per-tool rejection rather than a reach boundary.
| ## Managing AI Features | ||
|
|
||
| **Team owners** can enable or disable all AI features for their team from the team settings page. When disabled, the Expert chat panel with all AI feature will get removed for that team. Running instances need to be restarted for the change to take full effect. | ||
| **Team owners** enable or disable all AI features for their team from the team settings page. Disabling removes the Expert chat panel and all AI features for that team. Running instances need a restart for the change to take full effect. |
There was a problem hiding this comment.
Why can team owners disable this?
|
@cstns I think you forgot to merge, as you did approve already. I'll merge in your stead? |
|
@ZJvandeWeg We were waiting for the remaining write tools PRs to land before merging as now docs mention tools we do not have yet. As mentioned in PR body
|
3 participants
Adds
docs/user/mcp.md, one page for what an AI agent can do through FlowFuse over MCP: platform automations by resource, flow building in the Node-RED editor, and the read-only and full-access levels. FlowFuse Expert and connected third-party agents share the same surface.The Expert overview and connect-your-own-agent pages now link to it instead of repeating the capabilities, and both are tightened to match the reference style.
Full-access columns cover write actions from the open platform tool PRs #8496 to #8504, so merge after those land.