Atlassian MCP Server Client

Theofficial Atlassian Rovo MCP Serveris a cloud-based bridge between your Atlassian Cloud site and compatible external tools. Once configured, it enables those tools to interact withJira, Confluence, Jira Service Management, Bitbucket, and Compassdata in real time. Authentication usesOAuth 2.1orAPI tokens, so every action respects the user's existing access controls.

With the Atlassian Rovo MCP Server, you can:

- Summarize and searchJira, Confluence, Jira Service Management, and Bitbucket content without switching tools.
- Create and updateissues or pages based on natural language commands.
- Automate repetitive work, like generating tickets from meeting notes or specs.

It's built for developers, content creators, and project teams who work in IDEs or AI tools and want to use Atlassian data without constantly switching context.

Pick your AI client below to install the official Atlassian Rovo MCP Server. Each button uses your client's native install link, so you don't need to edit any JSON config by hand.

The Atlassian Rovo MCP Server works with a growing list of MCP-compatible clients:

Tools are organized by product and intent (read, write, or search). Organization admins grant or revoke access at the permission-group level, and each tool inherits the access of its parent group.

Check that your environment meets these requirements before you set up the server.

The requirements depend on how you connect:

- AnAtlassian Cloud sitewith one or more of Jira, Confluence, Jira Service Management, Bitbucket, or Compass
- Access tothe client of choice
- A modern browser to complete the OAuth 2.1 authorization flow, or API token credentials for headless authentication

For IDEs or local clients (desktop setup)

The server enforces several security controls:

For a deeper overview of the security model and admin controls, see:

A supported client connects to the server endpoint. The recommended endpoint for most clients is:

Thehttps://mcp.atlassian.com/v1/mcpendpoint is also supported (for example, for API token configurations).

Depending on your setup, a secure browser-based OAuth 2.1 flow is triggered, or API token authentication is used.

Once authorized, the client streams contextual data and receives real-time responses from your connected Atlassian products.

Once connected, you can run tasks like these from your client.

- Search: "Find all open bugs in Project Alpha."
- Create/update: "Create a story titled 'Redesign onboarding'."
- Bulk create: "Make five Jira issues from these notes."

- Summarize: "Summarize the Q2 planning page."
- Create: "Create a page titled 'Team Goals Q3'."
- Navigate: "What spaces do I have access to?"

- Create: "Create a service component based on the current repository."
- Bulk create: "Import components and custom fields from this CSV/JSON."
- Query: "What depends on theapi-gatewayservice?"

- Link content: "Link these three Jira tickets to the 'Release Plan' page."
- Find documentation: "Fetch the Confluence documentation page linked to this Compass component."

## Atlassian Rovo MCP When connected to atlassian-rovo-mcp: - MUST use Jira project key = YOURPROJ - MUST use Confluence spaceId = "123456" - MUST use cloudId = "https://yoursite.atlassian.net" (do NOT call getAccessibleAtlassianResources) - MUST use maxResults: 10 or limit: 10 for ALL Jira JQL and Confluence CQL search operations.

If you're an admin preparing your organization to use the Atlassian Rovo MCP Server, review the points below. For more detailed admin guidance, see:

- Not a Marketplace app:The Atlassian Rovo MCP Server isnotinstalled via the Atlassian Marketplace or theManage appsscreen. Instead, it is installed automatically the first time a user completes the OAuth 2.1 (3LO) consent flow (just-in-time, or "lazy loading," installation).
- First-time installation requirements:The first user to complete the 3LO consent flow for your site must have access to the Atlassian apps requested by the MCP scopes (for example, Jira and/or Confluence). This ensures the MCP app is registered with the correct permissions for your site.
- Subsequent user access:After the initial install, users with access to only one Atlassian app (for example, just Jira or just Confluence) can also complete the 3LO flow to access that app through MCP.

Model Context Protocol (MCP) lets AI agents connect to tools and Atlassian data using your account's permissions, which creates powerful workflows but also structural risks. Any MCP client or server you enable (for example, IDE plugins, desktop apps, hosted MCP servers, or "one-click" integrations) can cause an AI agent to perform actions on your behalf.

We use your feedback to improve the Atlassian Rovo MCP Server. If you hit a bug or limitation, or have a suggestion:

MCP clients can perform actions in Jira, Confluence, Jira Service Management, Bitbucket, and Compass with your existing permissions. Use least privilege, review high-impact changes before confirming, and monitor audit logs for unusual activity.

Atlassian runs an official remote MCP server — connect over a hosted URL instead of installing this one locally.

Interact with Atlassian tools like Confluence and Jira.

Integrate with Atlassian Cloud to access Jira tickets, issues, projects, and Confluence pages.

An MCP client for integrating with Atlassian tools like Jira and Confluence using OAuth authentication.

MCP servers for interacting with Jira and Confluence APIs.

Interact with Atlassian products like Confluence and Jira, supporting both Cloud and Server/Data Center deployments.

Integrate Atlassian products like Confluence and Jira with the Model Context Protocol.

Single-binary MCP server and CLI for Jira and Confluence. CI/CD-friendly, context-efficient, supports both Cloud and Server/DC.

Atlassian Rovo MCP Server (Streamin HTTP)