Connect Cursor to Coder

Cursor reaches Coder through one Flowplane address. You add Coder once in Flowplane, add that address to Cursor, 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. 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.

    Connect Coder →

  2. 2

    Add Flowplane to Cursor

    Your address is shown in the Flowplane console; it looks like

    https://mcp.flowplane.eu/<your-label>

    1. Add the block below to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
    2. Open Cursor’s MCP settings and turn flowplane on.
    3. When Cursor asks, sign in to Flowplane and allow it.
    {
      "mcpServers": {
        "flowplane": { "url": "https://mcp.flowplane.eu/<your-label>" }
      }
    }

    Steps checked against the vendor’s documentation (Anysphere)

  3. 3

    Ask Cursor

    • “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 it can do

What Cursor 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 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
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.
Does Cursor see the password or key for Coder?
No. You sign in to Coder through Flowplane, which keeps that sign-in sealed. Cursor only gets a Flowplane sign-in for you, which you can revoke in the console.
Can Cursor 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.
Your assistant

Other assistants with Coder

Everything about Coder and Flowplane →

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.