Skip to main content

Connect Claude to Jira & Atlassian: Rovo MCP Setup (2026)

Connect Jira and Confluence to Claude using the Atlassian Rovo MCP server. The official remote MCP URL, OAuth, and setup for Claude web/desktop and Claude Code.

ByUpdated

The Atlassian Rovo MCP server connects Jira, Confluence, Jira Service Management, and Bitbucket to Claude so you can search, summarize, and create issues and docs from chat. It is an official remote MCP server, so here is how to attach it to Claude (web/desktop) and Claude Code.

🟢 Model references match the current lineup · model notice · Fable subscription
🟢 Model references match the current lineup · Claude Opus 5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.

Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (

🟢 Model references match the current lineup · Claude Opus 5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
0/M input, $50/M output tokens). The one-time
🟢 Model references match the current lineup · Claude Opus 5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
00 credit applied only to the Fable 5 transition and is not offered for 5.1. Some coding and debugging requests may be answered by an Opus model due to a security classifier (both models). See the Fable 5.1 guide and the Fable 5 availability guide for details.

Connect Atlassian — 4 stepsConnect Atlassian — 4 steps1. MCP URLmcp.atlassian.com2. Add to Claudecustom connector · mcp add3. Sign in (OAuth)Atlassian auth4. WorkJira · Confluence

What you can do

Once connected, it helps you search and summarize Jira, Jira Service Management, Confluence, and Bitbucket without switching tools, and create issues, among other things. What is actually possible depends on the tools Rovo MCP provides.

What you need

An Atlassian cloud account and sign-in. Your access scope can vary with site/project permissions and plan.

How to connect — the official remote MCP

The Rovo MCP server URL is https://mcp.atlassian.com/v1/mcp/authv2.

Claude (web/desktop)

In Settings → Connectors, choose Add custom connector and enter the URL above. The general custom-connector flow is covered in How to connect (4 ways).

Claude Code

Register it from the terminal with:

claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2

For scopes and transports, see Claude Code MCP setup.

Authenticate (OAuth)

After connecting, sign in through the Atlassian login window and you are ready. In short, it is two steps: connect your client, then authenticate.

Connecting Jira · Atlassian① Settings → ConnectorsOpen the Connectorsscreen in Claude② Add Rovo MCPEnter the server atmcp.atlassian.com③ Log in · grantSign in with yourAtlassian account④ Approve & workSearch, summarize,create Jira issues

Try it

Ask things like "show my Jira issues due this week," "create a Jira issue for this bug," or "find the deployment doc in Confluence," and Claude will ask to approve the tool, then act in Atlassian.

Staying safe · troubleshooting

It reaches your work data, so check permissions and the approval scope (MCP connector security). If it will not connect, see the troubleshooting guide together with Atlassian's official docs.

Looking for more connectors? Browse the connector directory to search and filter common connectors by use case.

For another issue tool see Linear integration; for the full set see the connector & MCP catalog, and to build your own see Build your own MCP server. The official source is Getting started with the Atlassian Rovo MCP Server.

Written July 2026; re-checked September 9, 2026. The server URL, connection menus, and access scope can change per Atlassian's policies, so check the official docs as you connect. This is an unofficial guide.

Related: Recommended MCP servers & connectors

Was this helpful?

Keep reading