Atlassian MCP Server – Jira and Confluence Workflows
Atlassian's official Rovo MCP server gives AI agents permission-aware access to supported Jira, Confluence, and Compass data and actions. Use it for issue tracking, knowledge retrieval, page creation, project coordination, service context, and cross-product team workflows.
Overview
Atlassian's official Rovo MCP server connects compatible AI agents to Atlassian
Cloud products through a centrally hosted, permission-aware service. It lets an
agent work with current Jira, Confluence, and Compass context instead of relying
only on content copied manually into a prompt.
What the MCP server enables
Atlassian documents tools for search, retrieval, and supported write actions
across its cloud products. Depending on organization controls, user permissions,
and enabled permission groups, an AI agent can:
- Search and summarize Jira, Confluence, and Compass content.
- Retrieve Jira issues, project metadata, links, and related work context.
- Create and update Jira issues from natural-language instructions.
- Read, create, and update supported Confluence pages and content.
- Use Rovo search and fetch tools to retrieve cross-product context.
- Support repetitive workflows such as generating tickets from meeting notes,
drafting project pages, and linking related work across products.
When to use it
Use Atlassian MCP when an AI workflow needs live team context or must perform
authorized changes in Atlassian Cloud. Practical examples include triaging Jira
issues, creating work items from specifications, summarizing planning pages,
drafting Confluence documentation, reviewing project activity, retrieving
Compass service context, and combining issue and knowledge data in one workflow.
Connection and authentication
The recommended hosted endpoint is
https://mcp.atlassian.com/v1/mcp/authv2 over Streamable HTTP. Atlassian uses
OAuth 2.1 with a browser-based authorization flow, and clients supporting
dynamic client registration do not need a separately created OAuth app.
For IDEs and local clients that cannot connect directly to a remote MCP server,
Atlassian documents the mcp-remote proxy over stdio. Node.js 18 or later is
required for that bridge. Atlassian also supports API-token authentication when
an organization administrator explicitly enables it, but OAuth remains the
standard configuration represented below.
Key considerations
All actions respect the signed-in user's Jira, Confluence, and Compass
permissions. Organization administrators can control allowed client domains,
authentication options, and permission groups, while audit logs record key
activity. IP allowlists are also enforced. Atlassian's legacy SSE endpoint is
unsupported after June 30, 2026, so new configurations should use Streamable
HTTP. Site-level rate limits vary by plan, and the service currently does not
support FedRAMP or HIPAA requirements. Review high-impact write operations,
apply least privilege, and monitor audit logs for unusual activity.
Supported Transports
streamable_http
URL: https://mcp.atlassian.com/v1/mcp/authv2
stdio
Command: npx
Args:
-ymcp-remote@latesthttps://mcp.atlassian.com/v1/mcp/authv2
Frequently Asked Questions
- When should an AI agent use the Atlassian Rovo MCP server?
- Use it when a workflow needs current Jira, Confluence, or Compass context, or when an authorized agent must create or update issues, draft pages, summarize work, retrieve service information, or coordinate cross-product team activity.
- What does the Atlassian Rovo MCP server add to an AI agent's capabilities?
- It gives the agent structured, permission-aware access to live Atlassian Cloud data and supported actions, allowing it to search, retrieve, create, and update work without relying only on static model knowledge or manually pasted content.
- What can an AI agent access or manage through Atlassian MCP?
- Depending on enabled permission groups and user access, the agent can work with Jira issues and project metadata, Confluence pages and spaces, Compass context, and Rovo search and fetch results. All operations remain limited by existing Atlassian permissions.
- How is authentication configured for the Atlassian Rovo MCP server?
- The standard connection uses OAuth 2.1 with browser-based authorization. Clients supporting dynamic client registration do not need a separately registered OAuth app. API-token authentication is optional only when an organization administrator enables it.
- Which transport should be used for the Atlassian Rovo MCP server?
- Use Streamable HTTP with https://mcp.atlassian.com/v1/mcp/authv2 for current MCP clients. Use the documented mcp-remote stdio bridge for local clients that cannot connect directly to remote MCP servers. The legacy SSE endpoint is excluded because Atlassian ends support after June 30, 2026.