The official Atlassian MCP Server is a cloud-based bridge between your Atlassian Cloud site and compatible external tools. Once configured, it enables those tools to interact with Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and Atlassian platform data (Projects, Goals, Teams, Focus, Talent, and the Teamwork Graph) in real time. Authentication uses OAuth 2.1 or API tokens, so every action respects the user's existing access controls.
With the Atlassian MCP Server, you can:
- Summarize and search Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals, and more without switching tools.
- Retrieve and review recordings of videos and meetings from Loom.
- Create and update work items or pages based on natural language commands.
- Automate repetitive work, like generating work items from meeting notes or specs.
Connect once, then describe what you want — no tab switching and no copy-pasting. Your AI selects and runs the right actions.
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.
[!IMPORTANT] v2 is now the recommended version. New setups should use
https://mcp.atlassian.com/v2/mcp, which exposes more tools and more products. Existing v1 connections automatically start to expose and use v2 tools; incompatible clients may need to clear cached client IDs or.well-knowncredentials to keep authenticating. For setup steps, see Getting started with the Atlassian MCP Server.
One-click setup
Pick your AI client below to install the official Atlassian MCP Server. Each button uses your client's native install link, so you don't need to edit any JSON config by hand.
Let your agent do the setup
Most AI coding agents can install, authenticate, and configure the server themselves. Copy and paste this prompt into your agent:
Set up Atlassian MCP for this agent using the official setup guide at
https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
and the MCP server URL https://mcp.atlassian.com/v2/mcp. Then start the Atlassian MCP
authentication flow so I can sign in.
Or add the server manually with your client's own command:
Contents
- One-click setup
- Supported clients
- Plugin packaging and compatibility
- Supported products and tools
- How the server exposes tools
- MCP gateways
- Before you start
- Data and security
- How it works
- Example workflows
- Tips and tricks
- Admin notes: managing access
- Security
- Support and feedback
- Disclaimer
Supported clients
The Atlassian MCP Server works with a growing list of MCP-compatible clients:
The Atlassian MCP Server also supports any local MCP-compatible client that can run on localhost and connect to the server via the mcp-remote proxy. This enables custom or third-party integrations that follow the MCP specification.
[!TIP] For the current, canonical list of supported clients and step-by-step setup, see Getting started with the Atlassian MCP Server. You can also refer to your client's own MCP documentation or built-in assistant.
Plugin packaging and compatibility
This repository publishes the same MCP server and skills in several package formats so clients can use their native discovery and installation flows:
The skills in skills/ target the /v2/mcp endpoint and are what every packaged plugin
installs. The previous generation is archived in skills/v1/ for anyone still on a v1
endpoint; it is not installed by any plugin and is set up manually. See
skills/README.md for the differences.
Both mcp.json and .mcp.json are intentional. Agent Plugins requires the root mcp.json filename and its portable transport vocabulary; existing clients continue to use .mcp.json and their native configuration vocabulary. Keep their endpoint settings aligned when changing either file.
The root package can be imported by clients that implement Agent Plugins, including Kiro Powers. Client-specific manifests remain available and are not replaced by the portable package.
Supported products and tools
Tools are organized by product and intent (read, write, search, delete, or manage). Organization admins grant or revoke access at the permission-group level, and each tool inherits the access of its parent group.
Product-specific conditions:
delete_jiraandmanage_jiraare disabled by default and must be enabled by an admin before they can be used.- Bitbucket Cloud tools are only available if your Bitbucket workspace is linked to an organization. Workspaces that aren't linked to an organization can't be selected when authenticating.
- Jira Service Management tools only support authentication via API token, and are only available if an organization admin has enabled API token authentication.
- Loom tools are only available for Loom workspaces linked to an Atlassian site.
- Teamwork Graph tools can retrieve data from third-party services connected to Jira, such as linked pull requests, builds, and deployments. For GitHub for Atlassian, full access means tools retrieve GitHub data based on the user's GitHub permissions, while limited access means they retrieve data based on the user's Jira permissions. Azure DevOps, GitLab, Jenkins, and Spinnaker connectors follow the limited access model.
[!NOTE] For the complete, current tool reference, including the required scope for each permission group, see Supported tools.
How the server exposes tools
Rather than sending every tool definition to the AI client at connection time, the Atlassian MCP Server exposes a small set of the most-used tools and lets the client discover the rest on demand. Tools marked Primary are visible directly to agents.
This has two benefits:
- Your client's context stays free for the task at hand instead of being filled with tool definitions.
- New tools become available without the client needing to reconnect.
MCP gateways
If you're using an MCP gateway, or otherwise need every tool available up front rather than using the discovery and execute methods, use the tools=all override to expose all tools as a paginated flat tool list:
https://mcp.atlassian.com/v2/mcp?tools=all
Before you start
Check that your environment meets these requirements before you set up the server.
Prerequisites
The requirements depend on how you connect:
For supported clients
- An Atlassian Cloud site with one or more of Jira, Confluence, Jira Service Management, Bitbucket, or Compass
- Access to the client of choice
- A modern browser to complete the OAuth 2.1 authorization flow, or API token credentials for headless authentication
If your organization admin has disabled authentication via API token, MCP clients can't connect with a token and need to use OAuth 2.1 instead.
For IDEs or local clients (desktop setup)
- An Atlassian Cloud site with one or more supported products
- A supported IDE (for example, Claude Desktop, VS Code, or Cursor) or a custom MCP-compatible client
- Node.js v18+ installed to run the local MCP proxy (
mcp-remote) - A modern browser for completing OAuth login, or API token credentials for headless authentication
Data and security
The server enforces several security controls:
- All traffic is encrypted in transit over HTTPS (TLS 1.2 or later), per Atlassian's security practices.
- OAuth 2.1 and API token authentication provide secure access control.
- Data access respects user permissions across every connected Atlassian product, including Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom.
- If your organization uses IP allowlisting for Atlassian Cloud products, tool calls made through the Atlassian MCP Server also honor those IP rules.
For a deeper overview of the security model and admin controls, see:
How it works
Architecture and communication
-
A supported client connects to the server endpoint. The recommended endpoint for all clients is:
https://mcp.atlassian.com/v2/mcpThe v1 endpoints (
https://mcp.atlassian.com/v1/mcp/authv2andhttps://mcp.atlassian.com/v1/mcp) remain supported, and existing v1 connections automatically start to expose and use v2 tools. -
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.
[!WARNING] After 30 June 2026, the legacy Server-Sent Events endpoint (
https://mcp.atlassian.com/v1/sse) will no longer be supported. Update any custom clients configured to use/sseso they point to/mcp— preferablyhttps://mcp.atlassian.com/v2/mcp.
[!NOTE] Clients that can't complete authentication after the move to v2 tools may need to clear cached client IDs or
.well-knowncredentials.
Permission management
Access is granted only to data that the user already has permission to view in Atlassian Cloud. All actions respect existing project or space-level roles. OAuth and API token authentication both honor configured scopes and Atlassian permissions.
API token authentication (headless)
API token authentication is available for headless, service-style, or non-interactive client setups (for example, backend systems or automations). It is also required for Jira Service Management tools.
Two mechanisms are supported:
- Admin enablement required: An organization admin must enable API token authentication for the Atlassian MCP Server (Atlassian Administration → Rovo → Rovo MCP server → Authentication).
- Scoped token required: Create a personal API token, or ask your admin for a service account API key, with the scopes required for the tools and data you need to access.
- Configuration guide: Configure authentication via API token
- Admin setting reference: Control Atlassian MCP Server settings: Configure authentication
Example workflows
Once connected, you can run tasks like these from your client.
Jira workflows
- 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."
Confluence workflows
- Summarize: "Summarize the Q2 planning page."
- Create: "Create a page titled 'Team Goals Q3'."
- Navigate: "What spaces do I have access to?"
Compass workflows
- 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 the
api-gatewayservice?"
Loom workflows
- Retrieve: "Find the Loom recording of last week's design review."
- Summarize: "Summarize this Loom walkthrough and list the action items."
Projects and Goals workflows
- Status: "What's the current status of the Checkout Revamp project?"
- Roll up: "Which goals are at risk this quarter, and why?"
Combined tasks
- Link content: "Link these three Jira work items to the 'Release Plan' page."
- Find documentation: "Fetch the Confluence documentation page linked to this Compass component."
- Move work forward: "Move PROJ-456 to 'In Review' and add a comment that the PR is up."
[!NOTE] Actual capabilities vary depending on your permission level and client platform.
Tips and tricks
Set default CloudId, Jira project, and Confluence space
Update your AGENTS.md with the Markdown below to reduce discovery tool calls, save time and tokens, and set maximum search results.
## Atlassian 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.
Use skills
If you're using a desktop client like Claude, you can create or reuse skills for repeated tasks. See the default Atlassian MCP skills.
For Cursor, skills are part of the marketplace plugin.
Admin notes: managing access
If you're an admin preparing your organization to use the Atlassian MCP Server, review the points below. For more detailed admin guidance, see:
- Understand Atlassian MCP Server
- Control Atlassian MCP Server settings
- Manage Atlassian MCP Server
- Monitor Atlassian MCP Server activity
Manage, monitor, and revoke access
- Admin controls: Site and organization admins can manage, review, or revoke the MCP app's access from Manage your organization's Marketplace and third-party apps.
- Domain controls: Use the Rovo MCP server settings page in Atlassian Administration to control which external AI tools and domains are allowed to connect. By default, Atlassian-supported domains are allowed; you can add trusted domains or block supported ones. Domain controls apply to OAuth 2.1 connections. For details, see Available Atlassian MCP server domains.
- IP controls: If your organization uses IP allowlisting for Atlassian Cloud apps, requests made through the Atlassian MCP Server must originate from an IP address allowed by your organization's IP allowlist for the relevant app. For configuration details, see Specify IP addresses for product access. Bitbucket Cloud IP restrictions are configured separately by workspace administrators under Workspace settings → Access controls. See Control access to private content in a workspace.
- End-user controls: Individual users can revoke their own app authorizations from their profile settings.
- Audit logging: Every time a tool is used through the Atlassian MCP Server, an event is recorded in your organization's audit log. Admins can review these in Atlassian Administration under Insights → Audit log (filter for Rovo MCP User Actions or search MCP). For more information, see Monitor Atlassian MCP server activity.
Troubleshooting common issues
-
"You don't have permission to connect from this IP address. Please ask your admin for access." This usually indicates that IP allowlisting is enabled and the request's source IP address isn't allowed to access the relevant app via the Atlassian MCP Server. Ask your site, organization, or Bitbucket workspace administrator to review the applicable IP allowlist.
Hosted AI clients can send requests from the AI provider's outbound IP addresses rather than the user's corporate network or VPN. Being on an allowed VPN may therefore be insufficient. Ask your administrator to review the provider's published outbound IP ranges and approve the required access. For OpenAI-hosted connectors, see OpenAI's IP egress guidance. Local MCP connections can use the local network's outbound IP address. See how IP allowlisting works with Atlassian MCP.
-
OAuth sign-in succeeds, but tool calls return 403. Successful sign-in does not guarantee that tool calls will pass IP restrictions. A 403 can also indicate insufficient scopes, app permissions, or another access policy. Confirm the denial reason before changing an IP allowlist.
Security
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.
Large language models (LLMs) are vulnerable to prompt injection and related attacks (such as indirect prompt injection and tool poisoning). These attacks can instruct the agent to exfiltrate data or make unintended changes without explicit requests.
To reduce risk, only use trusted MCP clients and servers, carefully review which tools and data each agent can access, and apply least privilege (scoped tokens, minimal project/workspace access). For any high-impact or destructive action, require human confirmation and monitor audit logs for unusual activity. We strongly recommend reviewing Atlassian's guidance on MCP risks at MCP Clients: Understanding the potential security risks.
Support and feedback
We use your feedback to improve the Atlassian MCP Server. If you hit a bug or limitation, or have a suggestion:
- Visit the Atlassian Support Portal to report issues and feature requests.
- Share your experiences and questions on the Atlassian Community, and developer-related asks on the Atlassian Developer Community.
- Go to our Ecosystem Developer Portal if you are building an app and found a bug or issue, or have suggestions.
Disclaimer
MCP clients can perform actions across Atlassian products with your existing permissions. Use least privilege, review high-impact changes before confirming, and monitor audit logs for unusual activity.
Learn more: MCP Clients: Understanding the potential security risks.