A Cursor team workflow that starts from the task in your tracker

Updated

Your tracker already holds what Cursor's agent needs to know: the task, its parent and the decisions already on it. CRUX lets Cursor read them over MCP and gives each status in your workflow its own instructions, so nobody writes a prompt. It is for teams that use Cursor with Jira Cloud, Linear, Plane or GitHub Issues. It is not about the Cursor Teams plan.

What goes wrong with Cursor alone

Ryan pastes the text of a Jira task into Cursor. The agent rewrites a retry function, because the task does not say that the team chose that behaviour on purpose a month ago. The reason is in a comment on another task. Megan has her own rules file and her own prompts, so her agent plans a similar task differently. Emily, the PM, cannot tell from Jira whether anyone has started the task, because the work is in two private Cursor chats.

This page is about connecting Cursor to a team's workflow. Cursor Teams is Cursor's own paid plan for billing and admin, and CRUX works with whichever Cursor plan each person has.

Connect Cursor to CRUX over MCP

You need a CRUX account, a project tied to your tracker project, and your own tracker account linked to CRUX.

  1. In the dashboard, open "Connect your coding agent", pick the project and Cursor.
  2. Press "Create my token". The token is shown once, works for one project and acts as you, so copy it then.
  3. Export the token in your shell. Put it in your shell profile or a secrets manager rather than typing it, and never in a committed file.
  4. Copy the crux entry from the dialog into .cursor/mcp.json.
export CRUX_MCP_TOKEN=YOUR_TOKEN

The dialog writes this entry with your project's id in place of PROJECT_ID:

{
  "mcpServers": {
    "crux": {
      "url": "https://crux.team/mcp/p/PROJECT_ID",
      "headers": {
        "Authorization": "Bearer ${env:CRUX_MCP_TOKEN}"
      }
    }
  }
}

Cursor reads ${env:CRUX_MCP_TOKEN} from your environment, so the file holds no token. The same file serves the Cursor CLI, where this command checks the connection:

agent mcp list

CRUX has no bot account. Your comments appear in the tracker under your name, and text the agent wrote starts with a robot emoji.

Cursor Jira MCP setup

Atlassian's own path is the Atlassian Rovo MCP server, which has a section for Cursor with a one-click install. That gives one developer Jira inside Cursor.

With CRUX, Cursor reaches Jira Cloud through the crux entry above, so it needs no second MCP server. You connect your own Jira account once in CRUX, and Cursor reads and updates tasks as you. On top of the task, it gets the instructions for the task's status and the artifacts earlier steps left on it.

Cursor and Linear

Linear's own path is its MCP server, which Cursor installs from its MCP tools page. CRUX takes the same crux entry as for Jira: the project in CRUX is tied to one Linear team, and you connect your own Linear account through OAuth. Cycles become sprints when the team has cycles switched on.

What Cursor can do once it is connected

  • Read the task with its child tasks, comments, attachments, links and statuses, and search other tasks. Earlier tasks keep their approved artifacts, so the agent finds why the code is the way it is.
  • Get the instructions for a workflow step, with the task filled in.
  • Post the step's artifact to the task, for example a plan, after you say ok.
  • Change a status or an estimate, only with your consent.

To start a step, open it on the task in the dashboard, press "Copy prompt & wait" on the "Run on my machine" card, and paste the prompt into Cursor. A person starts every step.

CRUX does not give Cursor the project wiki over MCP. Cursor reads the wiki from your repository checkout, like any other file.

Approval checkpoints

Every tracker status has an owner role. The agent waits for you at the approval checkpoints your team set: typically its understanding of the task, its plan and its result. A person moves the task to the next status, and CRUX never changes your tracker's settings.

What we have not verified in Cursor

  • The crux plugin installs into Claude Code, Codex, GitHub Copilot and Gemini CLI. We have not tested its skills in Cursor, so start steps with "Copy prompt & wait".
  • We have not yet checked how the board shows a step started from Cursor.
  • The setup command /crux:crux-config runs in Claude Code only, and only a project admin runs it. The rest of the team can stay in Cursor.

Limits

  • CRUX is in beta, and one founder builds it.
  • CRUX is a hosted service only. It does not support Jira Server or Data Center.
  • The agent runs on your machine, on your Cursor subscription. CRUX sells no usage credits.
  • One person uses CRUX free. A team of 2 to 10 people pays $49 per active project a month, a team of 11 or more pays $120, and the first month of every project is free. During the beta nothing is charged. See the pricing page.

Next step

Start free, then follow the article Connect your coding agent. For the setup command, see the Claude Code page. The same project works with Codex.

FAQ

How do I connect Cursor to Jira?

For one developer, install the Atlassian Rovo MCP server in Cursor. For a team, connect your Jira Cloud project to CRUX and add the crux entry above to .cursor/mcp.json.

How do I connect Cursor to Linear?

For one developer, add Linear's own MCP server in Cursor. For a team, connect your Linear team to CRUX and add the crux entry above to .cursor/mcp.json.

Does Cursor need a separate Jira MCP server?

No. Cursor calls CRUX, and CRUX calls Jira through the Jira account you connected. Jira MCP and your own skills compares the two setups.

Can people on one project use different agents?

Yes. Any MCP client connects to the same project address, and each person gets the step instructions from CRUX. The dialog has entries for Claude Code, Codex, Gemini CLI, OpenCode, Cursor and Zed.

Where do I keep the token?

In the CRUX_MCP_TOKEN variable, outside committed files. You revoke it in the dashboard under MCP clients.