atlassian-mcp-server
Atlassian's official MCP server bridges AI tools (Claude, ChatGPT, Cursor, VS Code) with Jira, Confluence, Bitbucket, Compass, and JSM via OAuth 2.1 or API tokens. It runs as a cloud-hosted service and respects existing Atlassian access controls, letting teams query and create content without context-switching.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | atlassian/atlassian-mcp-server |
| Owner | atlassian |
| Primary language | JavaScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 836 |
| Forks | 105 |
| Open issues | 65 |
| Latest release | Unknown |
| Last updated | 2026-07-08 |
| Source | https://github.com/atlassian/atlassian-mcp-server |
What atlassian-mcp-server is
A JavaScript-based MCP server implementing the Model Context Protocol, hosted on Atlassian Cloud. Exposes granular tools for read/write/search operations across Jira, Confluence, JSM, Bitbucket, and Compass, with role-based permission groups and dual authentication (OAuth 2.1 or scoped API tokens).
Get the atlassian-mcp-server source
Clone the repository and explore it locally.
git clone https://github.com/atlassian/atlassian-mcp-server.gitcd atlassian-mcp-server# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- OAuth 2.1 flow requires a modern browser for authorization handshake; headless/CI environments should use API tokens instead.
- Permission groups (read, write, search) are managed at the Atlassian org level; admins must grant access per product to control what tools see.
- API tokens are scoped differently by product (JSM and Bitbucket Cloud have restricted scopes); review support docs for token requirements per use case.
- MCP Registry entry (com.atlassian) enables one-click setup in supported clients; verify your target client supports MCP and has compatible MCP version.
- Data flows through Atlassian Cloud-hosted service; audit your compliance requirements if handling sensitive Jira/Confluence data.
When to avoid it — and what to weigh
- Self-hosted or on-premise Atlassian deployments — Server is cloud-hosted only; no on-premise or self-hosted option mentioned. Requires Atlassian Cloud site.
- Need for Jira Service Management + OAuth 2.1 — JSM tools are API-token-only; OAuth 2.1 is not supported for that product. Bitbucket Cloud also requires API tokens with scoped permissions.
- Compass without OAuth 2.1 — Compass tools require OAuth 2.1 exclusively; no API token option available.
- Organizations without Atlassian Cloud infrastructure — Requires modern Atlassian Cloud site with Jira, Confluence, JSM, Bitbucket, or Compass. No integration with legacy Server/Data Center editions.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI license allowing commercial use, modification, and distribution with attribution and liability disclaimer.
Apache 2.0 permits commercial use, modification, and distribution. However, this is the server code license; actual usage and support depend on Atlassian Cloud service terms. Review Atlassian's Cloud terms of service and MCP server SLA for production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
Service is cloud-hosted and respects user's existing Atlassian Cloud access controls; no separate auth layer. OAuth 2.1 is industry-standard. API tokens are product-scoped. No details on encryption in transit/at rest, audit logging, or vulnerability response process; review Atlassian Cloud security docs and MCP server admin guide. Admin-level permission controls available at org level.
Alternatives to consider
Direct Atlassian API + custom integrations
More control but requires building and maintaining custom MCP adapter; no official support or pre-built client integrations.
Zapier / Make.com Atlassian connectors
Lower-code workflow automation for Jira/Confluence but less suited for AI agent / LLM use cases; no direct Claude/ChatGPT integration.
Open-source or third-party MCP servers (e.g., community-built)
May offer flexibility but lack official support, security review, and guaranteed compatibility with Atlassian products.
Build on atlassian-mcp-server with DEV.co software developers
Start with the official Atlassian Rovo MCP Server. Choose your client, configure OAuth or API tokens, and enable your team to query and create Jira, Confluence, and Bitbucket content from Claude, ChatGPT, or Cursor.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
atlassian-mcp-server FAQ
Does this work with Atlassian Server or Data Center?
Can I use both OAuth 2.1 and API tokens simultaneously?
What happens to permissions if I revoke a token or change Atlassian user roles?
Is there a rate limit or usage quota?
Software developers & web developers for hire
DEV.co helps companies turn open-source tools like atlassian-mcp-server into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your mcp servers stack.
Ready to integrate Atlassian with your AI tools?
Start with the official Atlassian Rovo MCP Server. Choose your client, configure OAuth or API tokens, and enable your team to query and create Jira, Confluence, and Bitbucket content from Claude, ChatGPT, or Cursor.