Which teams the agent may act on, and whether it has editing rights or read access only.
Any MCP client that supports the HTTP transport works, including command-line and editor agents and local models. Sign-in uses OAuth where the client supports it, with a token fallback where it does not.
Your own agent gets the full, growing set of FlowFuse platform automation and flow-building tools to run. That matters most where company policy only permits an approved AI agent, so FlowFuse Expert wasn't an option.
Your grant is enforced on every call: a read-only agent stays read-only, and no agent can delete an instance, application, snapshot or team. Every action is recorded in the audit log, marked via MCP.
When the agent builds a flow, you watch it happen on the canvas: open the instance and turn on the MCP toggle in the page header. Nothing goes live until you deploy.
This is available to all FlowFuse Cloud users and to Enterprise self-hosted installations from v3.0, across FlowFuse Hub, Edge and Fleet. See connecting your own agent for setup, including what to check on an instance before asking for a flow.