Specific implementation researched
Atlassian MCP
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Atlassian
- Publisher
- Atlassian
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- OAuth 2.1; optional API token.
- Read capabilities
- Search Jira, Confluence and other Atlassian content · Read Loom recordings and project context
- Write capabilities
- Create or update work items and pages
- Permissions
- Connected products are accessible within existing user permissions.
- Required plan
- No confirmed information
- Additional costs
- According to the provider, enriched Teamwork Graph search and context calls consume Rovo credits.
- Maintenance status
- v2 is documented; v1 usage is scheduled to receive v2 tools automatically from March 1, 2027.
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Not verified | — |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
Get started with the Atlassian MCP server | Atlassian AI Gateway | Atlassian Support ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.atlassian.com/v2/mcp