Plane MCP workflow for teams that use AI coding agents

Updated

CRUX connects a Plane (plane.so) project to the coding agents your team already uses, and self-hosted Plane Community Edition works too when it has a public address. Over MCP the agent reads the task with its sub-tasks, comments and cycle, and every Plane state gets an owner role. It is for teams that keep work in Plane and write code with Claude Code, Codex or Cursor.

The problem with pasting a Plane task into an agent

Ryan opens a work item in Plane, copies its text into Claude Code and types the same instructions as yesterday. The agent sees only the pasted text. It does not know why the earlier code looks the way it does, so it changes that code and breaks behaviour that worked.

What CRUX adds on top of Plane

Your tasks stay in Plane. CRUX adds a workflow. For every state it names an owner role, the agents that help there and the artifact each step leaves. The agent receives the step's instructions with the task filled in, so nobody retypes prompts.

How to connect Plane

  1. Create a project. Sign up, create an organization and a project, and choose Plane as the tracker. An admin of your CRUX organization connects Plane once, with your Plane address and workspace. Each CRUX project links to one Plane project.
  2. Add your Plane token. Create a personal access token in Plane at <your Plane web address>/settings/profile/api-tokens/. Paste it into the CRUX connect dialog on the Connected accounts page, not into your agent's config. CRUX checks the token with Plane before it saves it, and stores it encrypted.
  3. Each teammate adds their own. Every teammate repeats step 2 with their own token. CRUX calls Plane with your token, so your agent's comments appear in Plane under your name. There is no bot account.
  4. Connect your coding agent. Open "Connect your coding agent" in CRUX. The dialog creates a personal CRUX token and the setup for Claude Code, Codex, Cursor and other MCP clients. Your agent connects to https://crux.team/mcp/p/<projectId> and reads that token from CRUX_MCP_TOKEN.
  5. Set up the workflow. A project admin runs /crux:crux-config in Claude Code, which needs the connection from step 4. The agent reads the project's states and cycles, asks who owns each state and proposes the workflow. With a connected code repository the proposal is a pull request. Without a repository CRUX imports the workflow directly. Without Claude Code, choose "Start from the template" or "Build from my board" in the dashboard.
  6. Start a step. Pick a task and start its first step.

To replace your Plane token, relink it on the Connected accounts page. To remove it, disconnect it there and delete the token in Plane too. When Plane refuses a token, CRUX asks you to reconnect.

How Plane states map to workflow steps

CRUX works with the states your Plane project already has, so you rename nothing, and it does not change your Plane settings. The template a new project starts from looks like this. While you set it up, you match its statuses to your Plane states and change the roles and agents.

StatusOwner roleAgentStep artifact
To DoPMrefineracceptance criteria
In ProgressDeveloperplannerimplementation plan
In ReviewDeveloperreviewerreview report
DonePMnonenone

A person in the owner role starts every step and moves the task to the next state. People approve at checkpoints, which usually are the agent's understanding of the task, its plan and its result.

What the agent reads and what it may change

The agent reads the task, its parent and sub-tasks, comments, attachments and links. It lists the project's states and searches tasks by title and by label. When the project has Cycles switched on, the agent reads them as sprints.

The agent can create and update tasks, add comments and relations, and upload attachments. It is told to change a task's state or estimate only when you ask. Deleting a task takes a preview and then a second call that confirms it.

Each step posts its artifact, such as a plan or a review report, as a comment on the Plane task. Text an agent wrote starts with a robot emoji, 🤖.

An agent on your machine does not get the project wiki over MCP. It reads the wiki from the repository checkout.

Limits

  • CRUX is in beta and one founder builds it. We have no customer stories yet.
  • CRUX is a hosted service only.
  • Self-hosted Plane Community Edition works when it has a public address. CRUX blocks private addresses.
  • /crux:crux-config runs in Claude Code only. With Codex or Cursor, start from the template or from your board.

Next step

Start free. One person uses CRUX free. A team of 2 to 10 pays $49 per active project per month, a team of 11 or more pays $120, and the first month of every project is free. During the beta billing is not switched on, so nothing is charged. See the pricing page.

For the agent setup, read Connect your coding agent.

FAQ

Is CRUX a Plane MCP server?

No. Plane has its own MCP server, and to connect Plane to Claude Code for yourself, start there. CRUX gives each project its own MCP address. Through it the agent works with Plane tasks and gets the instructions for each workflow step. Jira MCP and your own skills compares a plain tracker MCP server with CRUX.

Does everyone on the team need a Plane token?

Everyone who starts agent steps needs their own token. People who work only in Plane need neither a token nor a CRUX account.

Does CRUX work with self-hosted Plane?

Yes, with Plane Community Edition, when the instance has a public address.

How is CRUX different from assigning tasks to agents in Jira or Linear?

In Jira and Linear a person can assign a task to an agent, which works in the vendor's cloud and returns a pull request. In CRUX a person starts each step in their own coding agent, and people approve the agent's understanding, its plan and its result. Task-to-PR agents compares these products.

Other trackers

CRUX also works with Jira Cloud, Linear and GitHub Issues.