atlassian/atlassian-mcp-server

One-click install buttons for Cursor, VS Code, ChatGPT, and Claude (native install links, no JSON editing).
Endpoint: https://mcp.atlassian.com/v1/mcp/authv2 (also https://mcp.atlassian.com/v1/mcp for API-token setups).
Local IDEs/custom clients: run the mcp-remote proxy (Node.js v18+) on localhost to connect to the hosted endpoint.

Usage

• •Connect your client and authenticate via browser OAuth 2.1 flow or API token (headless).
• •Natural-language tasks: search/summarize Jira, Confluence, JSM, and Bitbucket content; create/update issues or pages; bulk-create issues; link tickets to pages; create Compass components.
• •Set defaults (cloudId, Jira project key, Confluence spaceId, maxResults) in AGENTS.md to reduce discovery tool calls and save tokens.
• •Admin-driven: org admins enable API-token auth, control allowed domains, and see every tool use in the audit log.

Key features

• ✓Tools organized by product and intent (read/write/search permission groups) across Jira, Confluence, Jira Service Management, Bitbucket Cloud, and Compass.
• ✓OAuth 2.1 and API-token authentication; data access respects existing Atlassian permissions, IP allowlisting, and is encrypted over HTTPS (TLS 1.2+).
• ✓Just-in-time installation (not a Marketplace app) on first OAuth consent; admin controls for domain allow/block and IP allowlists.
• ✓Supported clients: ChatGPT, Claude (Claude.ai/Desktop/Code), Cursor, VS Code (GitHub Copilot), Copilot CLI, Gemini CLI, Amazon Quick Suite, and any local MCP client via mcp-remote.
• ✓Ships default Rovo MCP skills and AGENTS.md tips; audit logging of every tool call.

Best for

Letting AI coding assistants and IDEs work directly with Atlassian Cloud data — searching/summarizing/creating Jira issues and Confluence pages, and automating repetitive work without switching tools.

Caveats

• ⚠Requires an Atlassian Cloud site with one or more of Jira, Confluence, JSM, Bitbucket, or Compass.
• ⚠Jira Service Management and Bitbucket Cloud tools are available ONLY via API-token authentication; Compass tools are ONLY via OAuth 2.1.
• ⚠API-token auth must first be enabled by an organization admin (Atlassian Administration → Rovo → Rovo MCP server → Authentication).
• ⚠The legacy SSE endpoint (https://mcp.atlassian.com/v1/sse) is still supported but deprecated — clients should point to /mcp or /mcp/authv2 instead.
• ⚠MCP clients can perform actions with your existing permissions — Atlassian warns about prompt-injection/tool-poisoning risk and recommends least-privilege and audit-log monitoring.