Search cross-product context
Find work and knowledge across supported Atlassian sources using Teamwork Graph tools.
Documentation ↗MCP server / project management / source-linked
Atlassian Rovo MCP
Atlassian MCP is useful when a task crosses Jira work items, Confluence knowledge and other Atlassian context. Compare it on the sources your team actually uses and the tools exposed in your tenant, rather than assuming that every connected product permits the same actions.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Atlassian's remote MCP service now documents the v2 endpoint. Older /v1/sse setup instructions are obsolete.
Implementation source ↗
Atlassian's remote MCP service now documents the v2 endpoint. Older /v1/sse setup instructions are obsolete.
Implementation source ↗
Atlassian MCP is useful when a task crosses Jira work items, Confluence knowledge and other Atlassian context. Compare it on the sources your team actually uses and the tools exposed in your tenant, rather than assuming that every connected product permits the same actions.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Remote HTTP
- Authentication
- OAuth 2.1; optional API-token route documented separately
Connect to https://mcp.atlassian.com/v2/mcp and complete Atlassian authorization. For gateways requiring a flat tool list, the documented ?tools=all variant exposes the tools instead of discovery/execute.
Setup reference ↗What it actually exposes.
Concrete capabilities with maintainer sources.
Create and update work
Tools can act on work items and content, within the connected user's permissions.
Documentation ↗Discover relevant operations
The v2 service uses discovery and execute methods; gateways can request a flat paginated tool list.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
What's your must-have MCP server that you use daily?
A commenter reports using Atlassian MCP to ground Confluence agents with product code context and produce concise documentation.
“Atlassian MCP for Confluence ... understands the code base and documents it concisely; it is a must have.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed workflow: trace a requirement to delivery
Suggested evaluation, not an observed test result.
- Locate the Confluence requirement and related Jira work.
- Compare the requested behavior with issue status and identify unanswered acceptance criteria.
- Draft a linked status brief and proposed issue updates for human review.
What to inspect: A traceable requirement-to-work map, not an automatically validated delivery claim. Not tested here.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Enriched Teamwork Graph and context calls consume Rovo credits from the organization's shared allowance.
Boundary reference ↗Editorial inference: cross-product authorization increases the importance of confirming the site and object before a write.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A traceable requirement-to-work map, not an automatically validated delivery claim. Not tested here.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Linear MCP | Editorial choice: engineering work is already tracked in Linear. | A narrower work-management context. Documentation ↗ |
| Notion MCP | Editorial choice: team knowledge is primarily Notion pages. | Choose the system holding the authoritative content. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Can I keep using the old SSE URL?
The former /v1/sse endpoint is no longer supported; the current setup guide uses /v2/mcp.
Documentation ↗
Does MCP bypass Jira or Confluence permissions?
No. Actions respect the authorizing user's existing access controls.
Documentation ↗
Source trail.
Maintainer documentation used in this record.