From cc0e656d7bf256f367e00fed8883fba1ce7f13c0 Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Mon, 14 Sep 2026 16:06:28 +0200 Subject: [PATCH 1/3] Add Claude Code and Codex to the AI connector modal and the docs A coding agent installs the connector into itself, so its tab is one prompt and nothing else: Add the FlowFuse MCP tool at /mcp. Then ask me to complete the sign-in in the browser that opens. The prompt is built from the platform's own origin, the same source the address step already used, so it is correct on Cloud and self-hosted with nothing for the reader to edit. Nothing here goes stale when a client changes how remote servers are added, which they do at different times and in different ways: one documents an mcp add subcommand, Codex documents only its config file and its UI. Modal changes: - Step one is overridable per client, so a tab can show a prompt instead of the bare address. Both go through the same copy path and the same event. - The tab glyph is chosen per client through rather than one hardcoded icon. ServerIcon and CommandLineIcon are values now, not registered components. Docs: 'Command-line and editor agents' splits into a coding-agent section leading with the prompt, and a section for the rest. The hand-written mcp add command stays for anyone who wants it. --- docs/user/expert/third-party-agents.md | 16 +++++- .../components/dialogs/AiConnectorModal.vue | 57 +++++++++++++++---- 2 files changed, 60 insertions(+), 13 deletions(-) diff --git a/docs/user/expert/third-party-agents.md b/docs/user/expert/third-party-agents.md index c214ac141a..dc9a4706aa 100644 --- a/docs/user/expert/third-party-agents.md +++ b/docs/user/expert/third-party-agents.md @@ -89,16 +89,26 @@ Where custom connectors are available on your plan, add one and enter the FlowFu On Team and Enterprise plans an owner adds the connector for the organisation first, and then each person connects and signs in individually. -### Command-line and editor agents +### Coding agents -Claude Code, Cursor, Visual Studio Code and Gemini CLI all connect to the same address. Where a client supports OAuth, sign in; otherwise use a token, see [clients without a sign-in flow](#clients-without-a-sign-in-flow). +A coding agent can add the connector to itself. Ask it, rather than editing its configuration by hand: -For Claude Code: +``` +Add the FlowFuse MCP tool at https://app.flowfuse.com/mcp. Then ask me to complete the sign-in in the browser that opens. +``` + +This works in Claude Code and Codex, and in any other agent that can change its own MCP configuration. It also survives those clients changing how a remote server is added, which they do at different times and in different ways. + +If you would rather add it yourself, Claude Code takes: ```bash claude mcp add --transport http flowfuse https://app.flowfuse.com/mcp ``` +### Other command-line and editor agents + +Cursor, Visual Studio Code and Gemini CLI all connect to the same address. Where a client supports OAuth, sign in; otherwise use a token, see [clients without a sign-in flow](#clients-without-a-sign-in-flow). + ### Local and self-hosted models Use any HTTP-capable MCP client, such as LM Studio, LibreChat or Open WebUI, pointed at your own model, and add the FlowFuse address as a server in that client's configuration. Note that Ollama is a model runtime rather than an agent, so it needs an MCP client in front of it. diff --git a/frontend/src/components/dialogs/AiConnectorModal.vue b/frontend/src/components/dialogs/AiConnectorModal.vue index 31a4dc4063..01c584b3dd 100644 --- a/frontend/src/components/dialogs/AiConnectorModal.vue +++ b/frontend/src/components/dialogs/AiConnectorModal.vue @@ -15,7 +15,7 @@ @click="selectClient(client.id)" > {{ client.name }} @@ -33,12 +33,12 @@ >

01

-

Copy the FlowFuse connector URL

-

Paste it into your agent in the next step.

+

{{ client.step1Title || 'Copy the FlowFuse connector URL' }}

+

{{ client.step1Body || 'Paste it into your agent in the next step.' }}

- {{ endpoint }} - + {{ stepOneText(client) }} + Copy @@ -96,7 +96,7 @@