MCP serverPartly tested (needs an account)
Jira and Confluence in your assistant
Atlassian MCP Server
Atlassian's official connector lets your assistant search, sum up, create and update Jira work items and Confluence pages using your own account access.
- Works with
- Claude Code, Codex CLI
- Good for
- Daily work and research, Build an app
What it does
Jira is where many teams track tasks, and Confluence is where they keep pages and notes. This is Atlassian's own connector (an MCP server, a bridge that lets your assistant use another service). Atlassian runs it in its cloud at mcp.atlassian.com/v2/mcp. The only setup is one line in your assistant and a sign-in in your browser.
After you sign in, your assistant can search and sum up Jira work items and Confluence pages. It can create a story, move a work item to another status, add a comment or write a new page. If your company uses them, it also reaches Jira Service Management, Loom, Bitbucket, Goals, Projects, Compass, Teams, Focus and Talent.
Some limits keep it in check:
- It only sees what your own account can see.
- Every tool call goes into your organisation's Atlassian audit log.
- The Jira delete and manage tools stay off until an admin turns them on.
- Admins can limit it by domain or IP address.
- Jira Service Management tools need an API token that an admin allows.
The server first shows a small set of main tools. The assistant finds the other tools when it needs them, so you may not see every tool in the list at sign-in.
Some use costs Rovo credits. Searches and requests that pull context from several products use Rovo credits from your organisation's shared pool, mostly 1 to 10 credits a call. Looking up a single work item or page and write actions such as updating a work item are listed as free (Atlassian's Rovo usage page). Standard, Premium and Enterprise plans include a monthly allowance per user. Extra use is on by default at $0.01 a credit; admins can set a spending limit. The usage page lists no allowance for Free plans.
The content it reads, such as pages, work items and Loom recordings, goes to your AI model like anything else in a chat. Teamwork Graph tools can also return data from services connected to Jira, such as GitHub pull requests, builds and deployments.
If you install it as a Claude Code plugin from Anthropic's directory, you also get six skills (instruction files): capture tasks from meeting notes, generate a status report, a Jira sprint dashboard, company-wide search, spec to backlog and issue triage. The task and backlog skills show their plan and wait for you. The status report skill offers to publish to Confluence.
The old address /v1/sse is no longer supported after 30 June 2026. Use /v2/mcp.
Who it is for
Teams that plan work in Jira and keep notes in Confluence and want their assistant to find, sum up and create work items and pages. It helps project leads who turn meeting notes into tasks or write weekly status reports. You need an Atlassian Cloud site.
Example prompts
- "Summarize the Q2 planning page in Confluence."
- "Find all open bugs in Project Alpha and group them by priority."
- "Make five Jira issues from these meeting notes. Show me the list before you create them."
- "Move PROJ-456 to In Review and add a comment that the fix is ready."
- "What spaces do I have access to?"
How to install
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpcodex mcp add atlassian --url https://mcp.atlassian.com/v2/mcpHow to use it
In Claude Code run /mcp and sign in to Atlassian (in Codex: codex mcp login atlassian), then ask: Summarize the Q2 planning page. Or: Make five Jira issues from these meeting notes.
Other assistants
Codex CLI:
- Add the server:
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp- Sign in through your browser:
codex mcp login atlassianCheck it works
- In Claude Code, run
claude mcp list. Before sign-in, the server shows as "Needs authentication". - Type
/mcp, choose atlassian and finish the sign-in in your browser. - Ask "What spaces do I have access to?" (an example from the README). The answer should list your Confluence spaces.
- In Codex, run
codex mcp login atlassianand finish the sign-in in your browser.
Common problems
- Blocked by your company's network rules — "You don't have permission to connect from this IP address. Please ask your admin for access." — IP allowlisting is on. Ask your admin to review the allowlist. Hosted AI clients may connect from the AI provider's addresses, so a VPN may not be enough (README).
- Sign-in stopped working after the move to v2 tools — no error text — clear the cached client ID or saved
.well-knowncredentials in your assistant and sign in again (README). - An old setup guide uses the /v1/sse address — no error text — that address is no longer supported after 30 June 2026. Use
https://mcp.atlassian.com/v2/mcp. - Jira Service Management tools are missing — no error text — those tools work only with an API token that an admin has allowed (README).
What to watch out for
- Needs an Atlassian Cloud site; every action uses your own Jira and Confluence permissions (README)
- Searches and cross-product requests use Rovo credits from your organisation's shared pool, mostly 1 to 10 a call; single-item lookups and updates are listed as free. Extra use is on by default at $0.01 a credit; admins can set a spending limit (Atlassian support)
- Can create and update Jira work items and Confluence pages; Jira delete and manage tools stay off unless an admin turns them on (README)
- Pages, work items and Loom recordings it reads are sent to your AI model; every tool call is recorded in your organisation's Atlassian audit log (README)
- Admins can block it by domain or IP allowlist, and Jira Service Management tools work only with an API token that an admin allows (README)
- Teamwork Graph tools can return data from third-party services connected to Jira, such as GitHub pull requests, builds and deployments (README), so answers can include more than Atlassian data
- The plugin version also adds six skills that turn meeting notes into Jira tasks and offer to publish status reports to Confluence; they show the plan first, but they write to your sites when you agree
Licence and author
- Licence
- Apache-2.0
- Author
- Atlassian
- Source code
- github.com/atlassian/atlassian-mcp-server
How we tested it
We installed it on an empty test computer on 16 Oct 2026. Partly tested: installed in a clean test system, but its main features need an account or key we did not use.
We did not sign in, because that needs an Atlassian Cloud site. We did not test Codex or the plugin version with the six skills. Not yet used on real work.
Technical details of the test
- Date
- 16 Oct 2026
- Method
- In a clean container with no account we added Atlassian's hosted server with claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp (Claude Code 2.1.296). claude mcp list showed the server as Needs authentication.
Checked again on 17 Oct 2026
Alternatives
- Zapier MCP — can reach Jira and Confluence among many apps, but through Zapier actions, not Atlassian's own server.
- GitHub MCP server — the same idea for GitHub issues and pull requests instead of Jira.
- Slack plugin — for chat messages and channels instead of work items and pages.
FAQ
Do I need a paid Atlassian plan? You need an Atlassian Cloud site with Jira, Confluence or another supported product. Searches and cross-product requests use Rovo credits, mostly 1 to 10 a call. Atlassian lists single-item lookups and updates as free. Standard, Premium and Enterprise plans include a monthly allowance, and the usage page lists none for Free plans.
Can it delete my work items? Not by default. The README says the Jira delete and manage tools stay off until an admin turns them on.
Is there a Claude Code plugin?
Yes. Anthropic's directory lists it as atlassian. The plugin adds the same connector plus six skills. The one-line command adds only the connector.
Does it work in Gemini CLI? The README lists Gemini CLI as supported, but it gives no install command. So we do not list one yet.
Sources
- github.com/atlassian/atlassian-mcp-server
- support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
- support.atlassian.com/rovo/docs/rovo-usage-limits/
- developers.openai.com/codex/mcp/
- raw.githubusercontent.com/anthropics/claude-plugins-official/main/.claude-plugin/marketplace.json