How to
How to connect Claude to Jira
Atlassian ships an official Jira connector for Claude, and it covers a solid standard tool set. The question is whether that standard set matches how your team actually files and moves work.
Connect Claude to Jira either through the official Atlassian connector, which searches, creates, updates, transitions, and comments on issues, or through a custom MCP connector when you need deeper custom field and workflow coverage. A custom connector authenticates as your account with OAuth 2.0 and gates hard-to-undo actions behind your confirmation.
Key takeaways
- Atlassian offers an official Jira connector for Claude with a standard tool set: search, create, update, transition, comment.
- A custom connector goes further: deeper custom field and workflow coverage, tighter scoping, and confirmation tuned to your team.
- Status transitions are meaningful, so they are gated write actions that run only after you approve.
- The connector inherits your Atlassian permissions; if you cannot edit a project, neither can Claude.
Is there an official Jira connector for Claude?
Yes. Atlassian offers an official Jira connector for Claude, and it covers a standard tool set: search and summarize issues, create and update them, transition status, and comment. For many teams that is a strong starting point, and the honest advice is to try it first.
This puts Jira in a different category from tools where the directory connection is read-only. The official connector can already file a ticket and move it.
Where teams outgrow it is specificity. Real Jira instances carry required custom fields, per-project issue types, and workflows with guarded transitions. A generic standard tool set does not know that your bug template requires a severity field and a component, or that only certain transitions are valid from your triage column. A custom connector is built against your instance, so Claude files and moves work the way your team expects.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I connect Claude to Jira with a custom connector?
Ask us to build it. We ship a small MCP server that authenticates to Jira with OAuth 2.0 and the narrowest scopes the work needs. Read tools and write tools are separated, and hard-to-undo actions like workflow transitions require your confirmation before they run.
The setup runs in a few steps:
- 1Tell us how your team uses Jira: the projects, issue types, required fields, and workflow steps that matter.
- 2We build a custom MCP connector with read tools (search, read issue) and write tools (create, transition, assign, comment) kept separate and mapped to your fields.
- 3You authenticate through OAuth 2.0 as your own Atlassian account, so the connector inherits exactly your permissions.
- 4Claude starts filing and updating issues from inside your conversations, with hard-to-undo actions gated behind your approval.
Can Claude create a Jira issue from a conversation?
Yes. Claude turns a discussion into an issue with `create_issue`, setting the summary, description, type, and project, then filling fields like priority, labels, and sprint. The ticket lands in your backlog ready to work, instead of a chat note someone re-enters by hand.
Filing from a conversation is where most of the time savings sit, because the context is already in front of Claude. It has read the discussion, so the description writes itself and decisions get captured while they are fresh.
Beyond creation, the write tools cover the upkeep around an issue:
- Assign or reassign an issue and set priority, labels, or sprint.
- Add a comment with
add_commentto capture context or a decision. - Link related issues, such as marking one as blocked by another.
- Search the backlog and propose batched updates across matching issues.
Can Claude transition Jira issues through our workflow?
Yes, within the transitions your workflow allows. Claude reads the available transitions for an issue and moves it with `transition_issue`, such as from To Do to In Progress or Done. Because a status change is meaningful, the transition runs only after you approve it.
Workflows exist because status changes carry weight: they trigger notifications, move cards on boards, and change what teammates pick up next. The connector treats them that way.
Transitions follow your workflow, not a generic one
Claude reads the transitions actually available for that issue in your instance before proposing a move, so it never tries a status jump your workflow does not allow.
What permissions does a Claude Jira connector need?
Only yours. The connector authenticates as your account through OAuth 2.0 and inherits your existing Atlassian permissions. If you cannot edit a project or transition an issue, neither can Claude through the connector. Scopes are kept as narrow as the work requires.
That also means audit trails stay clean: issues Claude files and comments it adds are attributed to the account that approved them, inside the permissions that account already had.