Skip to main content

Atlassian

Search and update Jira issues, Confluence pages and Compass components through Atlassian's Rovo MCP server.

Connect it with: MCP. Atlassian's own documentation: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/.

What agents can do​

Connect Atlassian so the agents working your tasks can reach it. With it connected, they can:

  • Search Jira with JQL, read an issue with its comments, and create or transition issues.
  • Find and read Confluence pages, and create or update a page with a summary of the work.
  • Look up Compass components and their owners.

Before you start​

  • An Atlassian Cloud site with Jira, Confluence or Compass (the server serves Atlassian Cloud).
  • If your site restricts which apps may connect, an organization admin must allow it in Atlassian Administration > your organization > Connectors > Atlassian MCP server, by allowing Atlassian-supported domains or adding this Jaah's domain.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Atlassian​

Atlassian's MCP server signs you in itself, so connecting needs no key and no app of your own.

  1. In Jaah, open Secrets and select New.
  2. Search for Atlassian and select its card.
  3. Name the secret and choose who can use it (see Who can use it).
  4. Select Connect Atlassian, sign in to Atlassian in the window that opens, and approve the access it lists.
  5. You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).

Connect with an API key​

Atlassian has no API key option in Jaah: connect with the sign-in above.

Use your own OAuth app​

Not needed: Atlassian's MCP server registers Jaah itself when you connect, so there is no app of your own to create.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Atlassian with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

Tell the agent in your task description which secret to use, for example “use the Atlassian secret org/atlassian”.

Atlassian also runs an MCP server, which gives agents ready-made Atlassian tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Atlassian secret, and confirm.
  3. New tasks on the project start with the Atlassian tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Reconnect: when Atlassian ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Atlassian's side too, revoke Jaah in Atlassian's settings.

Limitations​

  • Agents act as the person who signed in, with that person's Jira and Confluence permissions.
  • One connection reaches the sites the signed-in account chooses at consent; connect again for another account.
  • Atlassian rate-limits the server per user; long bulk jobs may be slowed.
  • Agents can do only what the connected Atlassian account and its granted scopes allow.

Troubleshooting​

Test says Atlassian rejected the token (401)

The grant expired or the app was removed under your Atlassian account's Connected apps. Select Reconnect and sign in again.

The sign-in window says your organization does not allow this app

An organization admin opens Atlassian Administration > your organization > Connectors > Atlassian MCP server and adds this Jaah's domain to the allowed domains.

The secret shows Needs reconnect

Atlassian ended the grant (a password change, a revoked connection or a long idle period). Select Reconnect on the secret and sign in to Atlassian again.

New tasks on the project have no Atlassian tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.

Still stuck? Select Test and read the result: it names the value Atlassian refused and the status it answered.

FAQ​

Does Jaah need an app registered at Atlassian?

No. Jaah registers itself with Atlassian's sign-in server the first time anyone connects, and every later connection reuses that registration.

Should I use this or the Jira card?

Use this card for ready-made Jira and Confluence tools through MCP. Use the Jira card when a script needs the REST API with an API token.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Atlassian account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.