Best for
- Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
A
Atlassian Rovo MCP Server
Official
Securely connect Atlassian Cloud to AI tools.
GitHub source repository ↗
66FMRS · C
An official, cloud-hosted Atlassian MCP server for accessing and managing Atlassian Cloud data from compatible AI clients. Capabilities and authentication depend on the product, client, user permissions, and administrator policies; canonical tool identifiers are not listed in the supplied material.
The official cloud-hosted Atlassian MCP server connects Jira, Confluence, Jira Service Management, Bitbucket Cloud, and Compass to compatible AI clients over Streamable HTTP. It supports search, creation, and management workflows using OAuth 2.1 or API tokens, while honoring the user’s existing Atlassian permissions.
Tools
The tool list has not been reviewed yet.
Setup
Add https://mcp.atlassian.com/v1/mcp/authv2 to a supported MCP client. Interactive clients use OAuth 2.1 authorization; headless or service-style setups can use an API token. Local clients require Node.js v18+ and the mcp-remote proxy.
claude_desktop_config.json
{"url":"https://mcp.atlassian.com/v1/mcp/authv2","type":"http"}
Fit and risk
Not for
- Users without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
Required permissions
- Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
Risks and side effects
- AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
Troubleshooting
- If the client reports “Your site admin must authorize this app,” have a site administrator complete the OAuth 2.1/3LO consent flow
- Verify the Atlassian account, site, product permissions, and requested scopes
- For IP access errors, check the organization’s IP allowlist and relevant VPN or network ranges
- Confirm that an organization administrator enabled API-token authentication and that the token has required scopes
- Custom clients should use /mcp or /mcp/authv2 instead of the legacy /sse endpoint
Use cases
Search and summarize Jira, Confluence, Jira Service Management, and Bitbucket content
Create or update Jira issues and Confluence pages with natural-language requests
Generate Jira tickets from meeting notes or specifications
Query Compass service components and dependencies
Link Jira issues, Confluence pages, and Compass components
Supported clients
OpenAI ChatGPTFull support
ClaudeFull support
CursorFull support
Visual Studio Code (GitHub Copilot)Full support
GitHub Copilot CLIFull support
Google Gemini CLIFull support
Amazon Quick SuiteFull support
Local MCP-compatible clients via mcp-remotePartial support