Connect Codex to Coder
Codex reaches Coder through one Flowplane address. You add Coder once in Flowplane, add that address to Codex, and sign in. Check your Coder workspaces, templates and builds, read a build’s log, and start or stop a workspace from a chat.
- Tools
- 4 read · 1 change
- Sign-in
- Your own account
- Approval, by default
- Set per tool
- MCP server
- Flowplane’s tools
- 1
Add Coder in Flowplane
In the Flowplane console, add Coder, type the address you open Coder at and paste your session token. A Coder behind a firewall connects through a tunnel.
Each person pastes their own Coder session token, so the assistant sees and starts exactly the workspaces that person may. You make the token with `coder tokens create`, or in Coder under your account, Tokens. Flowplane keeps it sealed; the assistant never sees it.
- 2
Add Flowplane to Codex
Your address is shown in the Flowplane console; it looks like
https://mcp.flowplane.eu/<your-label>- Add the server with the first command below.
- Sign in with the second: your browser opens Flowplane; sign in and allow Codex.
- In the IDE extension: MCP servers › Add server, choose Streamable HTTP, paste
https://mcp.flowplane.eu/<your-label>, then Authenticate.
codex mcp add flowplane --url https://mcp.flowplane.eu/<your-label> codex mcp login flowplane - 3
Ask Codex
- “Which of my workspaces are running right now?”
- “Start my backend and frontend workspaces.”
- “Why did the last build of my dev workspace fail? Show the end of its log.”
- “Which templates can I make a workspace from?”
- “Stop every workspace I have not used today.”
What Codex can do in Coder
For teams that run their development environments on their own Coder deployment. Through Flowplane an AI assistant can list your workspaces and whether they run, the templates they are made from, a workspace’s builds and the end of a build’s log, and start or stop a workspace. It works with several workspaces in one request, for example starting all of them in the morning.
Reads4
- List my workspacesYour workspaces and whether they run
list_workspaces - List templatesThe templates workspaces are made from
list_templates - List a workspace's buildsWhat was built, started and stopped, newest first
list_workspace_builds - Read a build's logThe end of a build's log
get_build_logs
Changes1
- Start or stop a workspaceStart or stop a workspace
start_or_stop_workspace
Questions
- Can the assistant run commands in my workspace?
- No. Running commands, terminals and ports, Coder Tasks, and creating, deleting or updating workspaces are left out on purpose, as is everything about users, templates, organisations and the deployment.
- Does starting or stopping a workspace wait for approval?
- Not by default: it can be undone by starting or stopping again. Stopping ends what runs in the workspace, and unsaved work outside its home volume is lost. It acts on any workspace your Coder user may manage, so an admin can set it to ask first.
- Does Codex see the password or key for Coder?
- No. You sign in to Coder through Flowplane, which keeps that sign-in sealed. Codex only gets a Flowplane sign-in for you, which you can revoke in the console.
- Can Codex change things in Coder without asking?
- Yes, by default: none of its changes in Coder waits for approval. Your workspace’s rules can make any of them ask first, per tool.
- Connect Claude to Coder→
- Connect Claude Code to Coder→
- Connect ChatGPT to Coder→
- Connect Cursor to Coder→
- Connect GitHub Copilot to Coder→
- Connect Mistral Le Chat to Coder→
Flowplane is not affiliated with or endorsed by Coder’s maker; the name and logo only identify the app. Pricing
Let your AI work with your data. Safely, from today.
Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.