Skip to main content

Atlassian

Connecting Atlassian's MCP server lets your agents work across your Atlassian Cloud products: Jira (including boards, sprints, versions and attachments), Confluence, Jira Service Management operations, Bitbucket, Loom and Assets, plus Rovo search. With every tool listed, the server offers about 239 tools.

Read How MCP Servers Work in Outermind first if you have not connected an MCP server before.

Before you start​

  • Any paid Atlassian Cloud plan.
  • An Atlassian account with access to the sites and projects agents should work in. The connection acts as the Atlassian user who signs in, so agents reach what that user can reach.
  • Your Atlassian organisation admin, if your organisation restricts which MCP clients may connect; see Prepare Atlassian.
  • A tenant admin in Outermind to run the wizard and grant the tools.

Prepare Atlassian​

Usually there is nothing to prepare: Outermind registers itself with Atlassian automatically when you connect.

An Atlassian organisation admin can restrict which redirect domains MCP clients may use. If your organisation does, the admin must allow Outermind's redirect domain before anyone can connect: the host name in the redirect URI for the region your Outermind organisation is hosted in, for example us-api.outermind.ai for the US region. These are Outermind's redirect URIs:

https://us-api.outermind.ai/api/mcp-oauth/callback
https://uk-api.outermind.ai/api/mcp-oauth/callback
https://eu-api.outermind.ai/api/mcp-oauth/callback
https://au-api.outermind.ai/api/mcp-oauth/callback
https://qa-api.outermind.ai/api/mcp-oauth/callback
http://localhost:4071/api/mcp-oauth/callback

Outermind signs in through the URI for your region, so that domain is required. Allowing the domains of the four production URIs (US, UK, EU and AU) covers every region. The QA and local development URIs, the last two above, serve only Outermind's own test environments, so allow their domains only if Outermind support asks you to.

Connect in Outermind​

  1. Open the Capabilities hub, click MCP Servers under Tool Management, and click Add MCP server.
  2. Under Known server, pick Atlassian (mcp.atlassian.com). The endpoint https://mcp.atlassian.com/v2/mcp?tools=all is filled in, the wizard shows "Sign in and approve. An org admin may need to allow the Outermind redirect domain." and the expected sign-in is OAuth sign-in. Optionally edit Purpose, the one-line description agents see beside this server. Click Next.
  3. On Credential, the wizard says "Outermind registers itself with this server automatically when you connect." Click Connect, sign in to Atlassian and approve.
  4. On Summary, Outermind discovers Atlassian's tools and makes them active. Under Grant tools to agents, pick an agent to choose an access level for each one; to leave a product or action out, use the connection page afterwards.
info

Keep ?tools=all at the end of the endpoint. Without it, Atlassian lists only about 12 primary tools plus a few general discover and execute meta-tools, and you cannot tier or exclude each action separately. If you type the endpoint yourself under Other endpoint, include ?tools=all.

What your agents can do​

Agents can:

  • search, read, create and update Jira work, including boards, sprints, versions and attachments;
  • create, read, update and delete Confluence content;
  • work with Jira Service Management operations alerts;
  • work with Bitbucket, Loom and Assets;
  • search across products with Rovo search.

Read actions start at tier low, and every other action starts at high; see Risk tiers.

What is not available​

  • Adding another user as a watcher on a Jira issue. Outermind's earlier built-in Atlassian integration could do this; the MCP server cannot.
  • Compass. Atlassian removed Compass from this version of its MCP server.

Billing notes​

Outermind knows of no separate Atlassian charge for using the MCP server. A paid Atlassian Cloud plan is required.