Atlassian's official remote MCP server (Rovo) connects Jira, Confluence, Compass and Bitbucket to an AI client — 60+ tools over OAuth, fully managed. So Claude can triage issues, update tickets and read docs. Here's the setup.
Setup — official remote server
The endpoint is https://mcp.atlassian.com/v1/mcp. Add it as a remote/OAuth connector in clients that support remote MCP:
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v1/mcp"
}
}
}
For stdio-only clients (or older setups), bridge with mcp-remote (Node 18+):
{
"mcpServers": {
"atlassian": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"]
}
}
}
On first use you authorise via Atlassian OAuth and pick your Cloud site. Restart the client; see MCP config file location.
Verify
Ask: "Show my open Jira issues in the WEB project and summarise the linked Confluence spec." Real data back confirms it works.
Common problems
- Wrong site / no data — you authorised a different Atlassian Cloud site; re-run auth and select the right one.
/ssedeprecation — use the/v1/mcpendpoint above (the old/ssepath is being retired).- Server (Data Center) not Cloud — the official remote server targets Atlassian Cloud; self-hosted needs a different/community server.
mcp-remoteerrors — Node 18+ required; see Cursor MCP not working.
Going further
Jira pairs with GitHub and Sentry for engineering workflows. Compare with Linear in Linear MCP vs Jira MCP. Browse the productivity category or curated loadouts.