Jira integration for Claude Code and Codex teams
Updated
To work with Claude Code or Codex and Jira as a team, connect your Jira Cloud project to CRUX, and connect each developer's coding agent to CRUX over MCP. Each Jira status then gets an owner role and a step, a person starts each step, and people approve at checkpoints.
Just need to connect Jira to Claude Code for yourself? Atlassian's MCP server is enough, and its getting started guide has the setup.
What goes wrong with task access alone
Ryan connects a Jira MCP server to Claude Code and asks the agent to do a task. The agent does not know that on Monday the team agreed, in a comment on a related task, to keep the old API, so it rewrites that API.
A generic Jira MCP server gives an agent access to tasks, and for one developer on small tasks that is often enough. Jira MCP and your own skills compares that setup with CRUX.
How to connect Jira Cloud
- Create a project. Create an organization and a project in CRUX and choose Jira Cloud as the tracker. An admin of your CRUX organization connects Jira once. One CRUX project is tied to one Jira project.
- Link your Jira account. Each team member links their own Jira account on the Connected accounts page, through CRUX's Atlassian OAuth app. The app asks for
read:jira-work,write:jira-work,read:jira-userandoffline_access, plus granular scopes for issues, projects, boards, sprints and JQL. It asks for no admin write scope. When "Block user apps" is on in Atlassian Administration, an admin has to allow the app first, and CRUX gives you a ready message to send them. - Connect your coding agent. Open the "Connect your coding agent" dialog in the dashboard and create a personal token. Keep it in the
CRUX_MCP_TOKENenvironment variable. The dialog gives the setup for Claude Code, Codex, Cursor and other MCP clients. - Set up the workflow. A project admin runs
/crux:crux-configin Claude Code, which needs the CRUX MCP server from step 3. The agent reads the project's statuses and asks who owns each one and where the checkpoints go. With a code repository it opens a pull request with the workflow; without one, CRUX imports the workflow directly. Without Claude Code, choose "Start from the template" or "Build from my board" in the dashboard. - Start a step. In Claude Code run
/crux:crux-run KEY-12 planner, with the Jira task key and the agent name. In Codex the same command is$crux:crux-run KEY-12 planner.
The Codex command from the dialog:
codex mcp add crux --url https://crux.team/mcp/p/<projectId> --bearer-token-env-var CRUX_MCP_TOKENHow Jira statuses map to workflow steps
The template a new project starts from looks like this. While you set it up, you match its statuses to your Jira board and change the roles and agents.
| Status | Owner role | Agent | Step artifact |
|---|---|---|---|
| To Do | PM | refiner | acceptance criteria |
| In Progress | Developer | planner | implementation plan |
| In Review | Developer | reviewer | review report |
| Done | PM | none | none |
The person in the owner role starts the step. People approve at checkpoints, usually the agent's understanding, its plan and its result. A person moves the task to the next status.
A Claude Code Jira workflow, step by step
Here is one task, KEY-12 "Export invoices as CSV", on the template above.
- To Do. Emma, the PM, runs
/crux:crux-run KEY-12 refinerin Claude Code. The agent reads the task and its comments, asks her what is unclear and drafts acceptance criteria. Emma approves them, the agent posts them as a comment on KEY-12, and she moves the task to In Progress. - In Progress. Ryan, a developer, runs
/crux:crux-run KEY-12 planner. The agent reads the acceptance criteria and drafts an implementation plan. Ryan approves the plan, it lands on KEY-12 as a comment, and he builds the change with his agent. Then he moves the task to In Review. - In Review. Sarah, another developer, runs
/crux:crux-run KEY-12 reviewer. The agent checks the change against the criteria and the plan and writes a review report. Sarah approves it and it goes on KEY-12. - Done. Emma reads the three artifacts on the task and moves it to Done. No agent runs here.
The Atlassian MCP server alone, or with CRUX
| Question | Atlassian MCP server alone | With CRUX |
|---|---|---|
| Who starts a step | Each developer, with their own prompt | The person in the status's owner role, with that step's instructions |
| Where the agent's answer stays | In that developer's chat | In a Jira comment, approved by a person |
| Who moves the status | The developer, or the agent when asked | A person |
| What the PM sees | The task and what someone writes back | The criteria, the plan and the review on the task |
What the agent reads and what it may change
The agent reads the task, its parent and child tasks, all of its comments, its attachments and links. It lists the project's statuses and sprints and searches tasks, also by label. The comments include artifacts from earlier steps, each approved by a person.
An agent on your machine reads the project wiki from the repository checkout, not over MCP.
The agent can create and update tasks, add comments and relations, and upload attachments. It is told to change a status or an estimate only when you ask. It can move a task only through a direct transition that Jira offers you from the current status. Otherwise the call fails with STATUS_TRANSITION_UNAVAILABLE, which lists the statuses the task can reach. Deleting a task takes a preview and then a second call that confirms it, and in Jira it also deletes the task's subtasks.
Each step posts its artifact as a comment on the Jira task. Text an agent wrote starts with a robot emoji, 🤖.
Limits
- CRUX supports Jira Cloud only. Jira Server and Data Center are not supported.
- CRUX is a hosted service only.
- There is no bot account. The agent acts as the person who started it.
- CRUX does not change your Jira settings.
- CRUX is in beta and one founder builds it.
Next step
Start free. One person uses CRUX for free. A team of 2 to 10 people pays $49 per active project per month, and the first month of every project is free. During the beta billing is not switched on, so nothing is charged. The details are on the pricing page.
The article Connect your coding agent has the setup for every client.
Questions
Does CRUX work with Jira Server or Data Center?
No. Jira Server and Data Center are not supported, only Jira Cloud.
How is CRUX different from a Jira MCP server for tickets?
A Jira MCP server gives an agent access to tasks. CRUX adds instructions for the step that matches the task's status, owner roles, checkpoints and artifacts in Jira comments.
How is CRUX different from assigning tickets to Claude Agent for Jira or the Jira Coding Agent?
With Claude Agent for Jira a person assigns the work item to Claude or mentions it in a comment, and Claude opens a draft GitHub pull request. With the Jira Coding Agent a person assigns the work item to it and works with it in a session chat before creating the pull request. Both take a task to 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 in more detail. Checked on 13 November 2026.
Can I trigger Claude Code from Jira tickets?
A person starts each step. In Claude Code they run /crux:crux-run with the Jira task key and the agent name, and the agent reads that task from Jira.
Can Codex or Cursor work on these tickets too?
Yes. Codex runs the same steps with $crux:crux-run, and Cursor connects to the CRUX MCP server like any MCP client. /crux:crux-config runs only in Claude Code; without it, set up the workflow in the dashboard. Connect your coding agent has the setup for each.
Can the agent move tickets to another status on its own?
It is told not to. A person moves the task, or asks the agent to move it. Even then the agent can use only a transition that Jira offers that person.
Other trackers
CRUX also works with Linear, Plane and GitHub Issues.