PlugWiki
Atlassian Rovo MCP Server logo

Add Atlassian (Jira and Confluence) to Claude Code

Connect Claude Code to your Jira and Confluence with one command, then sign in with your Atlassian account from /mcp.

Add Atlassian's hosted server to Claude Code with the command above, then type /mcp inside Claude Code and sign in with your Atlassian account. After that, Claude Code can look up, create and edit your Jira issues and Confluence pages from the terminal. It works with Atlassian Cloud only. If Jira calls start failing while /mcp still says connected, the sign-in has likely gone stale, so reconnect first.

Good for

  • Developers who pick up Jira tickets and update them without leaving the terminal
  • Engineers who turn code changes into Confluence docs or release notes
  • Teams that want one shared server setup in a project .mcp.json file
  • Scripts and CI jobs that need a token login, once an admin allows it

Add Atlassian Rovo to Claude Code

Claude Code

  1. 1

    Copy this prompt.

    Add the Atlassian Rovo MCP server to Claude Code. Run this command:

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

Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Atlassian Cloud account.

Read-only mode: Claude Code asks before each Atlassian tool runs unless you add an allow rule, so leave the create and edit tools off your allow list. A full read-only switch exists only for your whole organization: an org admin turns off Write in Atlassian Administration.

Run the command in your terminal, start claude, then type /mcp, pick atlassian and choose Authenticate to sign in in your browser. Add --scope user to use it in every project; without it the server only loads in the folder where you added it. The plugin adds the same server plus Atlassian's Jira and Confluence skills. The API token option combines Atlassian's documented header with Claude Code's --header flag: send a personal token as Basic (base64 of email:token) and a service account key as Bearer <key>. A token written in the command is saved in plain text in ~/.claude.json.

From the vendor's docs. Source.

Common errors and fixes

  • Jira calls fail with 'The app is not installed on this instance' while /mcp shows connected

    Cause: The Atlassian sign-in has gone stale (open report; one user describes it in detail).

    Fix: In /mcp, choose Clear authentication on the Atlassian server and sign in again.

    claude-code Source

  • Plugin sign-in link opens 'Invalid context provided. Please try authorizing again.'

    Cause: Open report against the Atlassian plugin; Atlassian says some clients keep stale sign-in data after its version 2 change.

    Fix: Clear authentication in /mcp and sign in again. If it still fails, follow the open report for a fix.

    claude-code Source

  • The claude.ai Atlassian Rovo connector stays unauthorized after browser sign-in

    Cause: Cause unknown. One user's open report, with no replies yet; the plugin server also timed out after 30 seconds for them.

    Fix: No confirmed fix yet; the report is open.

    claude-code Source

  • An API token only gives read-only Teamwork Graph tools, or calls return 401

    Cause: A personal API token was sent as Bearer (one user's forum report). Atlassian's docs say personal tokens use Basic.

    Fix: Send a personal token as Basic with base64 of email:token. Bearer is only for service account keys.

    claude-code Source

  • Large Jira or Confluence results are cut off or saved to a file

    Cause: Claude Code caps MCP output at 25,000 tokens and saves replies over 50,000 characters to disk.

    Fix: Start Claude Code with a higher MAX_MCP_OUTPUT_TOKENS, or ask for fewer fields or results.

    claude-code Source

  • Atlassian is missing from /mcp

    Cause: It was added at local scope in another folder, or Claude Code is signed in with an API key, so claude.ai connectors do not load.

    Fix: Add it again with --scope user, or run /status and /login to use your claude.ai account.

    claude-code Source

  • Calls hang or time out until you reconnect in /mcp

    Cause: Server-side timeouts. The report was closed in March 2026 after the reporter said it had become much better.

    Fix: Reconnect from /mcp. If it keeps happening, ask an admin to enable API token sign-in.

    claude-code Source

Permissions

Medium risk

Claude Code can create and edit Jira issues and Confluence pages with your full Atlassian access, and one user reports it filing tickets without a clear yes. Keep Atlassian's create and edit tools on ask, and never add an allow rule that covers every Atlassian tool.

What it can do

Watch out for

  • Claude may file Jira tickets you did not approve

    A Claude Code user reports the model created Jira tickets after replies that were not a clear yes. Keep create and edit tools on ask, not allow. github.com

  • An allow-all rule skips every prompt

    A rule that covers every Atlassian tool lets Claude Code change Jira and Confluence without asking. Allow only the read tools you trust, by name. code.claude.com

  • A token in the command is saved in plain text

    A header added with --header is written to ~/.claude.json or .mcp.json. Never commit a project .mcp.json that holds your token. code.claude.com

  • Shared project servers ask before they load

    A server saved to .mcp.json with the project scope needs your approval before Claude Code uses it. Reset those choices with claude mcp reset-project-choices. code.claude.com

  • Admins see every call in the audit log

    Atlassian logs each tool call, and org admins choose which AI apps may connect. Ask your admin if Claude Code is blocked. support.atlassian.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyOnly an org admin can turn off Write, for the whole organization, in Atlassian Administration. In Claude Code, keep Atlassian's create and edit tools on ask: do not add an allow rule such as mcp__atlassian__* (or mcp__plugin_atlassian_atlassian__* for the plugin), and add deny rules for write tools you never want used.
Talks tomcp.atlassian.com (HTTPS)
Sign-in and keysClaude Code stores the Atlassian sign-in and refreshes it on its own; Clear authentication in /mcp removes it. An API token passed with --header is saved in plain text in ~/.claude.json or .mcp.json.
Scopes

  • Everything the signed-in user can access in Jira, Confluence, Bitbucket, Compass, Loom and Jira Service Management

Works in

Tap an app to see how to set it up and any known problems.

Questions

Why does Atlassian not show up in Claude Code?

It was probably added in a different folder. By default a server only loads in the project where you added it, so add it again from this folder or with the user scope. A claude.ai Atlassian connector only appears when Claude Code is signed in with your claude.ai account, not an API key.

How do I sign in to Atlassian from Claude Code?

Start Claude Code, type /mcp, pick the Atlassian server and choose Authenticate. Your browser opens the Atlassian sign-in, and Claude Code keeps and refreshes the login after that.

Is there an Atlassian plugin for Claude Code?

Yes. Atlassian's plugin is in Anthropic's official plugin marketplace and is the second option in the install box. It adds the same server plus Atlassian's Jira and Confluence skills, and you still sign in through /mcp.

Why does Jira say 'The app is not installed on this instance'?

Your sign-in has gone stale even though /mcp still shows it connected. Open /mcp, choose Clear authentication on the Atlassian server and sign in again; one user reports Jira calls work right after.

Why does the sign-in page say 'Invalid context provided'?

Users hit this from the Atlassian plugin's sign-in link, and the report is still open. Atlassian says clients that fail to sign in after its move to version 2 may need their saved sign-in data cleared, so clear authentication in /mcp and try again.

Can I use an API token in Claude Code instead of signing in?

Yes, once an org admin turns on API token sign-in. Use the API token option in the install box. A personal token goes in as Basic with your email and token encoded together, and a service account key goes in as Bearer.

Why do I only see read-only tools with my API token?

You probably sent a personal token as Bearer. Atlassian's docs say personal tokens must be sent as Basic, with your email and token encoded together; Bearer is only for service account keys.

Why are big Jira or Confluence results cut off?

Claude Code caps a tool's reply at 25,000 tokens and saves very large replies to a file. Start Claude Code with MAX_MCP_OUTPUT_TOKENS set higher, or ask for fewer fields or results.

How do I stop Claude Code from changing Jira without asking?

Leave Atlassian's create and edit tools out of your allow rules, so Claude Code asks every time. Only an org admin can make the server read-only for everyone.

How do I switch Atlassian accounts in Claude Code?

Open /mcp, select the Atlassian server and choose Clear authentication. Then authenticate again and sign in with the other account.

Information

updated Nov 1, 2026

WebsiteSupported toolsGitHubOfficial MCP RegistryAPI token authenticationIssues

More on this

Sources

Docs, issue trackers and discussions this page is built from.

Show all 12
  1. support.atlassian.com · support.atlassian.com
  2. github.com · github.com
  3. support.atlassian.com · support.atlassian.com
  4. code.claude.com · code.claude.com
  5. github.com · github.com
  6. github.com · github.com
  7. github.com · github.com
  8. github.com · github.com
  9. github.com · github.com
  10. code.claude.com · code.claude.com
  11. support.atlassian.com · support.atlassian.com
  12. github.com · github.com

Updated Nov 1, 2026.