Manage Linear issues, projects, and cycles from AI context.
- Home
- Top MCPs for Project Management
- Atlassian
Atlassian
Manage Jira, Confluence, and Compass via the official Atlassian Rovo MCP.
Quick answer
What it does
Surfaces Atlassian Cloud operations as MCP tools: Jira issue CRUD and search, Confluence page reads and edits, Compass service catalog queries.
Best for
- Jira issue CRUD and search
- Confluence page reads and edits
- Compass service catalog queries
- OAuth-based team installs
Not for
- Bitbucket PR workflows (not in MCP surface)
- Atlassian Server / Data Center deployments
Source: top-mcps.com/mcp/atlassian — verified Aug 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "atlassian": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp" ] } } }Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.atlassian.com/v1/mcp. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLI or .mcp.jsonshellclaude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcpThen run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.cursor/mcp.jsonjson{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v1/mcp" } } }Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.vscode/mcp.jsonjsonc{ "servers": { "atlassian": { "type": "http", "url": "https://mcp.atlassian.com/v1/mcp" } } }VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "atlassian": { "serverUrl": "https://mcp.atlassian.com/v1/mcp" } } }Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
cline_mcp_settings.jsonjson{ "mcpServers": { "atlassian": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp" ] } } }Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "streamable-http", "url": "https://mcp.atlassian.com/v1/mcp" } } ] } }Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLIshellcodex mcp add atlassian --url https://mcp.atlassian.com/v1/mcpCodex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "atlassian": { "command": { "path": "npx", "args": [ "-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp" ] } } } }Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Atlassian", "transport": "http", "url": "https://mcp.atlassian.com/v1/mcp" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. project management work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-project-management
Compare Atlassian MCP vs [Linear MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/atlassian - top-mcps.com listing for Linear
Install the Atlassian MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/atlassian (fetch https://top-mcps.com/mcp/atlassian.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Project Management MCPs
Other tools in the same category worth evaluating.
Compared with Atlassian
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Project Management? See all Project Management MCPs →