Atlassian Rovo MCP Server (official remote)
OfficialAtlassian's official hosted MCP server for Jira and Confluence Cloud — search, create, update.
Add to your client
Copy the config for your MCP client and paste it into its config file.
Add remote MCP URL https://mcp.atlassian.com/v1/mcp and complete OAuthPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"atlassian-rovo-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.atlassian.com/v1/mcp"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Before you start
- An Atlassian Cloud site with Jira, Confluence, and/or Compass (Server/Data Center is not supported by this remote server)
- A modern browser to complete the OAuth 2.1 authorization flow
- For headless/token auth: an admin-enabled, scoped Atlassian API token
- Node.js 18+ if your client needs the `npx -y mcp-remote https://mcp.atlassian.com/v1/mcp` proxy to reach the remote server
About Atlassian Rovo MCP Server (official remote)
Atlassian's official remote (Rovo) MCP server. It securely connects Jira, Confluence, and Compass Cloud to any MCP-capable LLM, IDE, or agent platform through a single hosted endpoint at https://mcp.atlassian.com/v1/mcp — no local install, with Atlassian handling hosting and updates.
Authentication is OAuth 2.1 via a browser flow for interactive clients, or scoped API tokens for headless/long-running setups (which an org admin must enable). All traffic is HTTPS/TLS 1.2+, and the server acts strictly within the signed-in user's existing Atlassian permissions and any IP allowlisting your org enforces.
It exposes ~30 read and write tools — search issues with JQL, create/edit/transition Jira issues, add comments and worklogs, read and write Confluence pages and comments, search with CQL, and manage Compass components. Supported clients include Claude, ChatGPT, GitHub Copilot CLI, Gemini CLI, Amazon Quick Suite, and VS Code, plus any local MCP client via the mcp-remote proxy.
Tools & capabilities (16)
searchJiraIssuesUsingJqlSearch Jira issues with a JQL query
getJiraIssueFetch a Jira issue by ID or key
createJiraIssueCreate a new Jira issue
editJiraIssueEdit fields on an existing Jira issue
transitionJiraIssueMove an issue through its workflow
addCommentToJiraIssueAdd a comment to a Jira issue
addWorklogToJiraIssueLog work against a Jira issue
getVisibleJiraProjectsList Jira projects the user can see
searchConfluenceUsingCqlSearch Confluence content with CQL
getConfluencePageFetch a Confluence page
createConfluencePageCreate a new Confluence page
updateConfluencePageUpdate an existing Confluence page
createConfluenceFooterCommentAdd a footer comment to a Confluence page
getAccessibleAtlassianResourcesList accessible Cloud sites (cloudIds)
atlassianUserInfoReturn info about the authenticated user
createCompassComponentCreate a Compass component
When to use it
- Use it when you want an agent to search and summarize Jira issues or Confluence pages without context switching
- Use it when generating Jira tickets from meeting notes, bug reports, or support threads
- Use it when bulk-creating or updating Confluence documentation from a conversation
- Use it when transitioning issues through a workflow or logging work by natural language
- Use it when you need an officially supported, permission-respecting integration governed by your org's IP allowlisting and SSO
- Use it when wiring Jira/Confluence into VS Code, Claude, ChatGPT, Copilot CLI, or Gemini CLI
Quick setup
- 1Confirm you are on Atlassian Cloud (Jira/Confluence/Compass) and that your admin permits the Rovo MCP server
- 2Add the remote endpoint `https://mcp.atlassian.com/v1/mcp` to your MCP client (or via `npx -y mcp-remote …` for local-only clients)
- 3Launch the client and complete the OAuth 2.1 browser authorization (or configure an admin-enabled API token for headless use)
- 4Restart/reload the client so it discovers the Jira/Confluence/Compass tools
- 5Verify by asking the assistant to search recent Jira issues or fetch a Confluence page
Security notes
OAuth and API-token auth both honor your configured Atlassian scopes and permissions, so the agent cannot exceed your own access. This is Cloud-only; Server/Data Center users need a community server like sooperset/mcp-atlassian.
Atlassian Rovo MCP Server (official remote) FAQ
Does this work with Jira/Confluence Server or Data Center?
No. The official Rovo remote MCP server supports Atlassian Cloud only. For self-hosted Server/Data Center, use a community server such as sooperset/mcp-atlassian.
How does authentication work?
Interactive clients use OAuth 2.1 in the browser; headless or long-running clients can use a scoped Atlassian API token, which an org admin must enable first. The server only does what the authenticated user is already allowed to do.
My client doesn't support remote MCP servers — what do I do?
Run the `npx -y mcp-remote https://mcp.atlassian.com/v1/mcp` proxy (Node.js 18+) to bridge the hosted server to a local stdio client.
What products and actions are covered?
Roughly 30 tools spanning Jira (search via JQL, create/edit/transition issues, comments, worklogs), Confluence (read/create/update pages and comments, CQL search), and Compass (component management), plus shared tools to list accessible sites and user info.
Will it respect our IP allowlist and SSO?
Yes. Traffic uses HTTPS/TLS 1.2+, honors IP allowlisting, and operates within the signed-in user's existing Atlassian permissions.
Alternatives to Atlassian Rovo MCP Server (official remote)
Self-hosted MCP server for Jira and Confluence Cloud and Server/Data Center.
Official Notion server to read, search, create, and update pages and databases in your workspace.
Read, search, and edit your Obsidian vault through the Local REST API community plugin.
Compare Atlassian Rovo MCP Server (official remote) with: