Start free
Building software

Coder MCP server

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.

Connect Coder →Set up your assistant
Tools
5 read · 1 change
Sign-in
Your own account
Approval, by default
Set per tool
MCP server
Flowplane’s tools
What it can do

What your assistant can do in Coder

5 tools that read and 1 that change something in Coder. By default none of them waits for approval; your workspace’s rules can make any of them ask first.

Reads5

  • Check the connectionSee which account it uses and whether it workswhoami
  • List my workspacesYour workspaces and whether they runlist_workspaces
  • List templatesThe templates workspaces are made fromlist_templates
  • List a workspace's buildsWhat was built, started and stopped, newest firstlist_workspace_builds
  • Read a build's logThe end of a build's logget_build_logs

Changes1

  • Start or stop a workspaceStart or stop a workspacestart_or_stop_workspace
How it connects

Sign-in

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.

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.

MCP

Coder and MCP

Coder has an MCP server of its own, built into Coder and still in beta: you run it with the Coder CLI or turn it on as an endpoint of your deployment, and its tools also reach files and commands in workspaces. Flowplane does not pass it through: it talks to Coder’s REST API directly, with a small set of tools and no commands.

Try it

Things to ask

  • “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.”
Your assistant

Connect your assistant to Coder

One Flowplane address works in every assistant below, with the same rules and the same log. Step-by-step setup for each:

FAQ

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.
Which AI assistants can use Coder through Flowplane?
Claude, Claude Code, ChatGPT, Cursor, Codex, GitHub Copilot and Mistral Le Chat, and any other client that supports remote MCP servers with sign-in. They all reach Coder through the same Flowplane address.
What does it cost?
Free for one person, with up to three apps and five assistants. Personal Pro is €9 a month including VAT; companies start at €99 a month for ten active users. Prices are indicative; see the pricing page.

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.

Start free →Book a call