Connect Jira and Confluence

Agents search and update Jira issues and read or create Confluence pages through Atlassian's hosted server; you sign in with your Atlassian account.

Once Jira and Confluence are connected, an agent can search issues with JQL, create issues and move them through transitions, read boards, and search, read and create Confluence pages with CQL.

Before you start

An Atlassian Cloud account with access to the site you want to use. Server and Data Center installs are not supported by Atlassian's hosted server.
Your existing Jira and Confluence permissions apply; the agent can only see and change what you can.
Your organisation admin may need to allow it. In Atlassian Administration, Rovo, Rovo MCP server, admins control which domains may connect and whether it is enabled.
You must be an owner or admin of the woble workspace.

Nothing to copy: Atlassian uses a sign-in flow.

Connect it

Open Marketplace, go to the Integrations tab, find Jira and Confluence and press Connect.
Press Continue with Jira and Confluence. A new tab opens at atlassian.com. Sign in with your Atlassian account.
On the consent screen, choose the site (for example acme.atlassian.net) if you have more than one, review the permissions listed and press Accept.
The tab closes. The card shows Connected and the agent panel lists the new Jira and Confluence tools.

The agent first fetches your accessible sites to get the cloud id, so it may ask which site you mean if you have several.

Or ask an agent

Type @ruby connect Jira and Confluence in any chat. The same card appears in the conversation. Only owners and admins can complete it.

Try it

"@atlas list the open bugs in project PAY updated this week, then find the Confluence page about the on-call rota and tell me who is on this weekend."

If it does not connect

Consent screen blocked or an error about the redirect domain: your Atlassian admin must add the woble host under Rovo MCP server, Domain settings. The first consent on a site may also need an admin to complete it.
Wrong site chosen: the agent finds none of your projects. Press Remove in Marketplace, Connected, and connect again picking the right site.
Session expired, or "You don't have permission to connect from this IP address": press Test connection; if it fails, Remove and reconnect. The IP message means your organisation enforces an allowlist; ask your admin.

Disconnect

Open Marketplace, Connected, and press Remove on Jira and Confluence. The tokens are deleted and agents lose the tools immediately.