Skip to main content
Connect your agent to Atlassian to work across Jira, Confluence, and other Atlassian Cloud products — search issues, create pages, manage projects, and more.

​
How to enable

The recommended route is the Rovo MCP server: an Atlassian organization admin must first allow Abundly to access your Atlassian instance, after which each user authenticates with their own Atlassian account. If your admin can’t allow the domain, connect with an API token instead.
1

Allow Abundly in your Atlassian admin console

  1. Go to admin.atlassian.com
  2. In the sidebar, navigate to Apps → Platform experiences → AI settings → Rovo MCP Server
  3. Click Add domain and enter your Abundly app domain with /** (for example, https://app.abundly.ai/** or https://your-tenant.app.abundly.ai/**)
Atlassian admin console showing the Rovo MCP Server settings page with the Abundly domain added
This is a one-time setup. Once the domain is added, all users in the organization can connect their accounts.
2

Add Atlassian to your agent

Go to the MCP Servers tab in your agent’s capabilities. You’ll find Atlassian in the “Add a server” section — click it to add.
3

Authenticate your account

Click Connect, then Continue with OAuth and complete the OAuth flow to connect your Atlassian account.
API token authentication is also available under advanced settings, but OAuth is recommended — API tokens only expose a limited subset of tools.

​
Connecting with an API token instead

The Rovo MCP server is the easiest route, but it isn’t the only one. You can also give an agent direct access to the Jira and Confluence REST APIs with an Atlassian API token, defined as an Outgoing API. This is worth considering when:
  • Your Atlassian admin can’t or won’t allow the Abundly domain in the Rovo MCP settings
  • The agent should act as its own dedicated Atlassian account rather than on behalf of a person
  • You need endpoints or fields the MCP server doesn’t expose
The trade-off is that you describe the API to the agent yourself instead of getting a ready-made tool set.
1

Create the API token

Go to id.atlassian.com/manage-profile/security/api-tokens while signed in as the account the agent should act as, and create either a classic token or a token with scopes (see below). Copy the value immediately — it’s only shown once.
2

Store it as a Secret

In Workspace → Secrets, create a secret whose value is the Atlassian account email and the token joined by a colon:
Store it unencoded — the platform Base64-encodes it and adds the Basic prefix when calling the API.
3

Define the Outgoing API

In Workspace → Outgoing APIs, create an outgoing API, add the secret with the Basic auth injection method, and add the endpoint pattern for your token type. Then enable it on the agent’s Capabilities page. The general HTTP Requests capability is not required — an Outgoing API works on its own.

​
Classic vs. scoped tokens

Atlassian offers two kinds of API token, and they are called against different base URLs — this is the detail most setups get wrong. Prefer a scoped token: it limits the damage a leaked credential can do, and it lets you give the agent read-only access where that’s enough. Pick the smallest set of scopes that covers the agent’s job — read-only on issues is enough for reporting and triage suggestions, and you only need write scopes if the agent should change anything. Confluence uses the same pattern with ex/confluence in place of ex/jira. To find your cloudId, open https://your-site.atlassian.net/_edge/tenant_info in a browser — or simply ask the agent to fetch it.
Atlassian API tokens expire — up to 365 days, and one year by default. Put a reminder in your calendar, or have the agent remind you: when the token expires, its calls start failing with authentication errors. Rotating the token means updating the Secret; the Outgoing API and the agent stay untouched.
Once the agent has a working call, ask it to write the details into its instructions — base URL, JQL it used, fields it needs. That turns trial and error into a repeatable routine.

​
Example use cases

  • Issue triage — “Every morning, check Jira for new unassigned issues in the Support project and suggest an assignee based on workload”
  • Sprint reporting — “Summarize the current sprint progress and post an update to Slack every Friday”
  • Documentation sync — “When a Jira epic is marked as done, create a Confluence page documenting what was shipped”
  • Cross-platform updates — “When someone mentions a Jira ticket in Slack, look it up and post a summary with the current status”