Connect your own agent
Your own MCP client, such as Claude Code or Codex, can work in Flux as you. It runs on your computer
with your own model account, which Flux never sees. Signing in is one click, and nothing is set up
first. On the ./flux demo data:
-
Add Flux to your client with the commands the Connect page shows. Sign in as Ada, the company’s owner (
./flux demoprints her password), and open it: your name at the bottom left → All settings → AI → Connect another (Connect AI while nothing is connected) → Claude Code or Codex on your computer (then Show the command), or go straight to http://127.0.0.1:8081/connect-agent. 8081 is the default port; use the one./flux upprinted.Terminal window claude mcp add --transport http flux http://127.0.0.1:8081/mcp # Claude Codeclaude mcp login fluxcodex mcp add flux --url http://127.0.0.1:8081/mcp # Codex; adding starts the sign-incodex mcp login fluxclaude mcp login fluxneeds a terminal: outside one it stops with “stdin isn’t a terminal”. If the login times out before you choose Allow, run it again. Claude Code adds the server for the folder where you runclaude mcp addand nowhere else: startclaudefrom that folder, or add--scope userto use it from any folder. -
Allow it, once. The login opens Flux in your browser. Check that access goes to an address on your own computer and choose Allow. That is the whole setup: Flux makes the client’s agent and its connection, and the client says it is authenticated (
claude mcp listshows Connected). -
It acts as you. The client sees and changes what you can, in the spaces where AI is on, and no more. It starts at Do it and tell me (its tag on its row in Settings → AI); turn on Ask me first any time and every change waits for your OK. Deleting something and changing other people’s things always wait for your OK in your Inbox, whatever you choose, and only you can approve them.
-
Ask it something, for example: “Using Flux, what is the Community garden sensors space working on, and what is still open?” The client reads the space’s conversation, tasks and Wiki with Flux’s tools, and answers in your client. Claude Code asks before it uses each Flux tool the first time: allow it. From a script,
claude -p "…" --allowedTools mcp__fluxgives the same approval. Disconnect on the same page ends its access at once.
The loopback http:// address works only for a client on the same computer. A client on another
computer needs an HTTPS address: the operator sets FLUX_PUBLIC_ORIGIN behind a TLS reverse proxy
(agent connection,
integrations for operators). Flux accepts clients
only through their public client metadata documents, so the server needs outbound HTTPS when a
client signs in. Both clients were run through these steps against a clean clone
(record).