MCP · Project tracking · Atlassian
Atlassian Rovo MCP Server
Connect an AI host to Atlassian Cloud work and documents, with organization controls over read, write and search permissions.
Permissions can grow. Administrator settings can automatically apply permissions to future additions. Review that choice deliberately.
Understand the tool
What it does.
Atlassian's hosted server connects an AI host to supported Cloud products, including Jira and Confluence. Its public repository provides setup and plugin material, not a self-hosted service copy.
Why use it?
Use it to connect requirements with their implementation work. Link each blocker to supporting records. Begin with one project and a read/search task before enabling changes.
A useful fit for
- Jira and Confluence context
- Project handoffs
- Work-item preparation
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Prepare a project handoff
A new project owner needs the current decisions and unresolved work.
- Identify the project and relevant Confluence space.
- Read selected work items and source pages.
- Separate approved decisions, proposals and blockers.
Intended outputA linked handoff brief with open questions.
Use case 02
Draft work from meeting notes
A meeting agreed changes that need tracking.
- Read the selected notes.
- Check for existing work items.
- Propose titles and acceptance criteria before creating anything.
Intended outputReviewable tasks without silently changing the backlog.
A concrete starting point
Illustrative prompt: project handoff
Use v2 with the necessary products and permissions enabled.
Prepare a handoff brief for the Jira project and Confluence space I name. Link decisions and unresolved work. Identify contradictions rather than resolving them by guesswork. Do not create issues, comment or edit pages.What this can change
Retrieved work and documents enter the AI host. Enabled write tools can change shared records.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- An Atlassian Cloud account and access to the selected products.
- An allowed MCP client and organization administrator settings permitting the connection.
- OAuth support for interactive use; API-token access depends on administrator enablement.
- Authentication
- OAuth 2.1 is the recommended interactive method; enabled API-token workflows are also documented.
- Can read
- Authorized Atlassian content and permitted connected context
- Can write or change
- Enabled work-item, page and other product operations
- Network and data flow
- mcp.atlassian.com and Atlassian services
- AI host/model provider
- Approval and control
- Administrators can restrict read, write and search per product. Review host actions separately; organization access is not approval of every change.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Current v2 remote endpoint
- Product availability differs by authentication method and organization configuration
- Do not assume Atlassian Data Center compatibility
Costs and account requirements
Atlassian product subscriptions apply. Rovo MCP calls can consume shared Rovo credits; check current allowances and usage rules.
Current pricing or plan information ↗Apache-2.0 repository; hosted service terms
The repository's license does not replace Atlassian Cloud terms or grant a self-hosted service.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Permissions can grow
Administrator settings can automatically apply permissions to future additions. Review that choice deliberately.
Mixed-source context
Connected context can cross product boundaries. Check the intended audience before passing the resulting brief elsewhere.
Where it may fall short
- No organization connection or tool call was tested.
- A public plugin repository does not establish that the hosted service is fully open source.
Observed behavior · 2026-10-18
Runtime and security findings.
The current /v2/mcp endpoint rejected credential-free initialization. Its public discovery metadata listed read, write and other scopes across multiple Atlassian products.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation
Broad discovery is not an access grant
The current v2 endpoint returned 401 with error invalid_token. Its public resource metadata included read, write, search, delete and manage scope names. This establishes a discoverable authentication boundary, not which scopes a user would receive.
In practice: Review the consent and effective organization permissions. Confirm the intended product and site before allowing a tool operation.
Documented concern
Organization settings can expand with new permissions
Atlassian's MCP Permissions tab controls read, write and search access. Its apply-to-future-additions option can automatically authorize later permissions for an allowed intent.
In practice: Inspect the MCP-specific organization settings and future-addition behavior. Disable write access for an investigation-only workflow and verify denial with a dedicated test account.
Version, environment and fixture
- Version or deployment
- Remote deployment version not disclosed by the observed responses
- Tested target
- https://mcp.atlassian.com/v2/mcp
- Artifact identity
- HTTPS certificate verification enabled. Public resource-metadata body SHA-256: 0beffea740c221e0df9f5797dedb3d5e7591d44c05d40f7894ce0936c1a6917d. This fingerprints the observed metadata, not the deployed server implementation.
- Environment and fixture
- Windows 11 build 26200; Python 3.12.10 urllib; OpenSSL 3.0.16.
- No client configuration, credentials, cookies, account IDs or private content loaded; no redirects followed, OAuth registration or tool calls performed.
- Observed 2026-10-19T00:47:10.910158+00:00 through 2026-10-19T00:47:20.930924+00:00 UTC.
- One request per listed check; 20-second timeout and 64-KiB response cap. Initial sandbox DNS failures were retained separately and resolved with approved network access; they are not endpoint failures.
Checks and results
2 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationMet expectation
- Method
POST https://mcp.atlassian.com/v2/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream. Content-Type: application/json; MCP-Protocol-Version: 2025-03-26; body: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"IonBin-account-free-evaluation","version":"1.0.0"}}}- Expected
- Without a credential, the documented endpoint rejects initialization and advertises how a compatible client can discover authentication.
- Observed
- HTTP 401 at 2026-10-19T00:47:10.910158+00:00. WWW-Authenticate: Bearer; resource_metadata=https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp. Parsed error indicator: invalid_token.
Public authentication discoveryMet expectation
- Method
GET https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream.- Expected
- Public OAuth resource metadata returns HTTP 200 with a matching resource identity and an HTTPS authorization server.
- Observed
- HTTP 200 at 2026-10-19T00:47:20.930924+00:00; Content-Type: application/json. Resource: https://mcp.atlassian.com/v2/mcp. 38 supported scopes: read:me, read:account, offline_access, email, read:jira:agent-interface, write:jira:agent-interface, search:jira:agent-interface, delete:jira:agent-interface, manage:jira:agent-interface, read:confluence:agent-interface, write:confluence:agent-interface, search:confluence:agent-interface, search:rovo:agent-interface, search:code:agent-interface, read:all:twg, write:all:twg, read:goals:agent-interface, write:goals:agent-interface, read:projects:agent-interface, write:projects:agent-interface, read:bitbucket:agent-interface, write:bitbucket:agent-interface, read:loom:agent-interface, write:loom:agent-interface, read:talent:agent-interface, write:talent:agent-interface, read:jira-align:agent-interface, write:jira-align:agent-interface, read:teams:agent-interface, write:teams:agent-interface, read:artifacts:agent-interface, write:artifacts:agent-interface, read:capacity-planning:agent-interface, write:capacity-planning:agent-interface, read:focus:agent-interface, write:focus:agent-interface, read:assets:agent-interface, write:assets:agent-interface. Authorization server: https://auth.atlassian.com (public issuer path omitted). Bearer methods: header.
Practical caveats
- Use the current /v2/mcp guide when configuring a new client; older examples can refer to other transports or endpoint versions.
- Some enriched Teamwork Graph and search calls consume Rovo credits. Authentication success would not establish that a workflow is cost-free.
- A connected client can act with the user's existing permissions; high-impact changes still need explicit review.
What this evaluation does not establish
- OAuth or API-token authentication, organization policies, product/site permissions and tenant isolation.
- Authenticated tool discovery, Jira or Confluence reads/writes, audit records, credit usage and prompt-injection resistance.
- The older endpoint variants and local implementation.
- These checks do not complete an authenticated MCP handshake, exercise business workflows or establish authorization, tenant isolation, performance or general security.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
Useful across established project systems, with documented administrator controls. Product, credit and authentication differences add setup complexity.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Current v2 setup
- Organization permissions
- Credit usage
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Current getting-started guide ↗developer.atlassian.com
- Organization permission controls ↗support.atlassian.com
- Official repository and product differences ↗github.com
- Rovo MCP credit usage ↗support.atlassian.com