Atlassian MCP server
The Atlassian MCP server gives AI agents access to Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom on Atlassian Cloud: search, summarize, and create or update issues and pages.
Connect Atlassian
Claude Code (then run /mcp in a session to sign in)
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpCodex
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcpAny other MCP client: server URL
https://mcp.atlassian.com/v2/mcpClaude Desktop, Codex Desktop, Cursor, VS Code and ChatGPT install it from their plugin or connector directories by searching for Atlassian. In Windsurf, add a custom server with serverUrl set to the v2 URL. Jira Service Management tools only work with API token auth, and only after an admin enables it. The old SSE endpoint stopped being supported after 2026-06-30.
What the Atlassian MCP server does
The Atlassian MCP server, also called the Atlassian Rovo MCP server, is Atlassian's own hosted bridge between AI tools and an Atlassian Cloud site. Through it an agent can search and summarize Jira work items, Confluence pages, Jira Service Management requests and Bitbucket Cloud repos, create and update issues and pages from plain instructions, and read Loom recordings, Goals, Projects and Teams data.
The Atlassian server groups its tools into permission groups per product, such as read_jira, write_jira and search_confluence, and an organization admin can grant or revoke each group. Delete and manage tools for Jira are off until an admin turns them on. To save context, the server shows agents a small set of primary tools and lets them discover the rest; adding ?tools=all to the URL returns the full list for gateways.
Atlassian runs the server only in its cloud, at mcp.atlassian.com, with OAuth 2.1 sign-in or an API token for headless use; there is no self-hosted version, and Data Center sites are not covered. Every call respects the user's existing Jira and Confluence permissions and the site's IP allowlist. The repo, which holds plugin packages and skills rather than server code, had 1,078 GitHub stars on 2026-10-01.
When to use Atlassian
- You want the agent to turn meeting notes or a spec into Jira work items.
- You need a summary of a Confluence space or an epic's open issues without opening Jira.
- You want the coding agent to read the ticket it is working on and update its status.
- You want to search across Jira, Confluence and Bitbucket in one question.
When to pick something else
- Jira or Confluence Data Center and Server: the MCP server only connects to Atlassian Cloud sites.
- Unattended write access: with write groups enabled the agent can create and edit issues and pages as you, so keep delete tools off and review changes.
- Regulated workloads: Atlassian states the server does not currently support FedRAMP or HIPAA requirements.
What Atlassian needs
- An Atlassian Cloud site with Jira, Confluence, Jira Service Management, Bitbucket or Compass
- A browser for OAuth 2.1 sign-in, or an Atlassian API token if your admin allows token auth
- Node.js 18 or newer only for local clients that need the mcp-remote proxy
What the Atlassian MCP server costs
Free to connect on every Atlassian Cloud plan, including Free; calls that pull enriched Teamwork Graph context use Rovo credits.
Current prices: www.atlassian.com . We do not list prices: vendors change them often, so check the publisher's own page.
Questions people ask
Is the Atlassian MCP server free?
Connecting is free on every Atlassian Cloud plan, including Free, with hourly call limits that rise on paid plans. Calls that pull enriched Teamwork Graph context use Rovo credits (Atlassian pages read 2026-10-01).
Does the Atlassian MCP server work with Jira Data Center?
No. It is a cloud-hosted service for Atlassian Cloud sites only. Data Center users need a community server, such as the MrRefactoring atlassian-dc-mcp packages listed in the MCP Registry.
Other MCP servers for notes, docs and team tools
- Linear: The Linear MCP server gives AI agents access to your Linear workspace through Linear's hosted endpoint: find, create and update issues, projects and comments, with a read-only URL when you only need lookups.
- Notion: The Notion MCP server gives AI agents access to your Notion workspace through Notion's hosted server: search pages and databases, read them as Markdown, and create or update pages, databases and views.
- Obsidian: The Obsidian MCP server gives AI agents access to your Obsidian vault through the Local REST API plugin: list and read notes, search across files, append or patch content and delete files.
- Slack: The Slack MCP server gives AI agents access to a Slack workspace through Slack's hosted endpoint: search messages and files, read channels and threads, send messages, and edit canvases and lists.