How Do You Connect Claude Code to Jira?
Atlassian built and runs an official remote MCP server for Jira, Confluence, Bitbucket, and the rest of its suite, so you're not relying on a third-party integration to keep it working. It follows the same pattern as every other official server Claude Code supports - see [what MCP servers are and why they matter](/blog/what-are-mcp-servers-and-why-they-matter) if you haven't connected one before, or [the general setup guide](/guides/setting-up-mcp-servers) for the mechanics that apply across all of them.
Once it's connected, Claude Code can pull a ticket's full description and comment history before it starts work, search a project by component or label, and update status or leave a comment when a task is done - all without you switching tabs to copy context back and forth.
Step One: Register the Server
- Open a terminal (or the desktop app's built-in terminal panel) and run: claude mcp add atlassian --transport http https://mcp.atlassian.com/v1/mcp/authv2
- Claude Code opens your default browser to Atlassian's login. Sign in and approve the connection - you'll pick which site (and, on some plans, which projects) it can access.
- Back in Claude Code, run claude mcp list to confirm "atlassian" shows as connected, or claude mcp get atlassian for the full connection detail.
Browser OAuth vs an API Token
OAuth is the default path and it's the one most people should use - you approve access once in the browser and Claude Code handles the session from there. It's scoped to whatever you approve, so a personal machine only exposes what you personally have access to.
An API token is the alternative, and it needs to be turned on by an Atlassian admin under Administration settings before it'll work. It's worth the extra setup step on a shared or headless machine where a browser popup isn't practical, or as the fallback described below.
What This Is Actually Good For
- Reading the full ticket - description, comments, linked issues - before you touch a line of code, so Claude Code starts with the same context you'd have if you'd read it yourself.
- Searching a project by component or label before scoping a sprint, instead of scrolling a board by hand.
- Transitioning a ticket's status and leaving a comment when work is done, so the tracker stays current without a separate manual step.
That last one is worth treating carefully - see [reviewing Claude Code's output before you ship](/blog/review-claude-code-output-before-you-ship) for why an agent marking its own ticket done isn't the same as it actually being done.
The One Reliability Quirk to Know About
This isn't a dealbreaker, it's a known rough edge. If you're setting this up for daily use rather than an occasional check-in, it's worth testing the token path from day one instead of discovering the OAuth quirk mid-project.
It's Not Just Jira
The same server also covers Confluence, Bitbucket, Jira Service Management, and Compass. One connection, one OAuth approval, and Claude Code can pull a Confluence page for context while it works a linked Jira ticket - that's the actual point of running it as a single server instead of four separate integrations.
When Not to Bother With It
If you're working solo on a project with no tracker, or Jira is just where tickets go to be forgotten, skip this. It earns its keep once a project has real ticket history worth reading and a status that other people actually check.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How do I connect Claude Code to Jira?
Run claude mcp add atlassian --transport http https://mcp.atlassian.com/v1/mcp/authv2, approve the OAuth prompt in your browser, then confirm with claude mcp list. It's Atlassian's own official server, covering Jira along with Confluence, Bitbucket, and the rest of the suite.
Should I use OAuth or an API token to connect?
OAuth is the default and works for most people - approve it once in the browser. An API token, enabled by an Atlassian admin, is the better choice for a shared or headless machine, or if you hit the OAuth re-authentication quirk covered above.
Can Claude Code see my whole Jira site once it's connected?
Only what you approve during the OAuth flow - the site and projects you grant access to, not every project in your organization. An admin can further restrict access by permission group on their end.
Why does Claude Code keep asking me to log into Jira again?
This is a known reliability quirk with the OAuth connection that Atlassian has acknowledged in its own community forums. If it's happening often, switch to the API token path, which an Atlassian admin can enable under Administration settings.
Does this also work with Confluence and Bitbucket?
Yes. It's a single Atlassian MCP server that covers Jira, Confluence, Bitbucket, Jira Service Management, and Compass - one connection instead of four separate ones.
Last reviewed by David Iya on September 1, 2026
