Atlassian Rovo
Read, search, create and edit Jira issues and Confluence pages from an AI assistant. OAuth 2.1 sign-in, 31 tools in Anthropic's snapshot against 55 in Atlassian's own reference, and org-admin read/write/search permission gates.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Atlassian Rovo via MCP
https://mcp.atlassian.com/v1/mcp/authv2Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect Atlassian Rovo once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioAtlassian Rovo Tools & Capabilities (31)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Yes, on Cloud. Atlassian's product page states all Atlassian Cloud customers have access, with site-level rate limits that vary by Jira and Confluence plan. The same answer adds a hard exclusion worth checking before you start: the MCP server does not currently support FedRAMP or HIPAA requirements, so regulated workloads are out of scope.
They are hourly and set per site by plan. Atlassian publishes 500 calls per hour on Free and 1,000 per hour on Standard. Premium and Enterprise start at 1,000 per hour plus 20 additional calls per user, capped at 10,000 calls per hour. The limits are site-level, so everyone connected shares one budget.
Yes, and this is the main control. Atlassian's admin documentation describes a Permissions tab under Rovo then Rovo MCP server that toggles read, write and search independently, per app. Blocking write stops creation and modification across the org. Atlassian states changes take effect immediately, with no restart or reconnection required.
An admin has almost certainly blocked that permission group. Atlassian documents the exact string users see: access denied because your organization admin has not authorized the named permission, for example write. The fix is for an admin to set that permission to Allowed on the Permissions tab. Two other causes are a blocked IP address and a disallowed authentication method.
No. Atlassian states the server does not store or cache your Jira or Confluence content, and describes it as a secure proxy between your AI client and your Atlassian Cloud site. It operates within the permissions of the signed-in user and only reaches data that person is already allowed to see in the products themselves.
Check your network egress rules for Atlassian domains. Atlassian's admin documentation warns that the server renders interactive Jira and Confluence widgets in iframes, and that strict egress filtering which blocks the Atlassian domain makes the server appear to be down or not functioning because the visual components fail to load rather than erroring.
Only if your organization admin has enabled it. Atlassian documents API token authentication for non-interactive cases such as CI/CD, bots and backend services, using a personal token or a service account key. Atlassian recommends OAuth 2.1 for anything user-driven, and notes token auth exposes fewer tools than OAuth does.
Yes. Atlassian's getting-started guide names OpenAI ChatGPT, Claude, Docker, GitHub Copilot CLI, Google Gemini and Amazon Quick Suite as supported clients, and states the server supports any app with MCP support. Atlassian publishes per-client setup steps for VS Code, Cursor, Claude Code, Claude Desktop, Codex and Windsurf.
Sources
- Atlassian Rovo MCP Server — getting started — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — supported tools — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — authentication and authorization — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/authentication-and-authorization/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — configuring OAuth 2.1 — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-oauth-2-1/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — configuring authentication via API token — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — setting up clients — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/setting-up-clients/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — Rovo search and fetch — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/using-rovo-search-and-fetch-in-the-atlassian-remote-mcp-server/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian Rovo MCP Server — troubleshooting and verifying your setup — https://support.atlassian.com/atlassian-rovo-mcp-server/docs/troubleshooting-and-verifying-your-setup/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian admin — configure Rovo MCP server permission — https://support.atlassian.com/security-and-access-policies/docs/Configure-Atlassian-Rovo-MCP-server-permission/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian admin — control Rovo MCP server settings — https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian admin — monitor Rovo MCP server activity — https://support.atlassian.com/security-and-access-policies/docs/monitor-atlassian-rovo-mcp-server-activity/ (fetched 2026-08-18) · retrieved 2026-08-18
- Atlassian — remote MCP server product page and FAQ (rate limits, FedRAMP/HIPAA, data handling) — https://www.atlassian.com/platform/rovo-mcp (fetched 2026-08-18; the older
/platform/remote-mcp-serverURL 301-redirects here) · retrieved 2026-08-18 - Atlassian Community — *Using the Atlassian Remote MCP Server (beta)*, the documentation URL Anthropic's directory publishes — https://community.atlassian.com/forums/Atlassian-Remote-MCP-Server/Using-the-Atlassian-Remote-MCP-Server-beta/ba-p/3005104 (fetched 2026-08-18). This is a community forum article, not maintained documentation. It now opens by stating it is no longer up to date and links to the support-site documentation above, which is what this page is built from. It still instructs readers to use the
/v1/sseendpoint that Atlassian is retiring after 30 June 2026. · retrieved 2026-08-18 - Live authentication probe of
https://mcp.atlassian.com/v1/mcp/authv2— anonymousinitializereturned HTTP 401 with aWWW-Authenticate: Bearerchallenge (2026-08-18) · retrieved 2026-08-18 - Live OAuth descriptor probes (2026-08-18) — see the note below · retrieved 2026-08-18
- Anthropic connector directory snapshot, dated 2026-08-16 — https://claude.ai/directory/11ba10d9-477b-4988-bd1c-90a7fa680dc1 · retrieved 2026-08-16
Server Info
- Category
- Productivity
- Developer
- Atlassian Rovo
- Tools
- 31
- Domain
- mcp.atlassian.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Productivity
Related Resources
Ready to connect Atlassian Rovo?
Connect Atlassian Rovo once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.