Atlassian MCP server

Endpoint: https://mcp.atlassian.com/v1/mcp/authv2 · Authentication: Sign in with OAuth

Remote MCP server for Jira, Confluence, Compass, and engineering project context across Atlassian products.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint in your client, start Connect or Sign in, approve the requested scopes, and return to the client. OAuth discovery finds the authorization server; client registration requirements vary by provider. Follow the provider guidance and client setup below.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.atlassian.com/v1/mcp/authv2
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Not yet verified — Latest validation did not verify a transport
Declared authentication: OAuth 2.1
Detected authentication: OAuth 2.1 detected or retained from publisher evidence
Protocol lifecycle: Not yet negotiated
Authorization server: https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3
Category: Project Management

Product documentation · Official listing documentation

More Project Management MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

No app registration needed

The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.

Publisher evidence reviewed 2026-08-24.

Publisher documentation

Connect it

Live-validated endpoint: https://mcp.atlassian.com/v1/mcp/authv2 · Not yet verified. No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.

Agent prompt for Claude Code or Codex

Add the Atlassian MCP server to my MCP client configuration and verify that it works.

What it is: Remote MCP server for Jira, Confluence, Compass, and engineering project context across Atlassian products.
Server URL: https://mcp.atlassian.com/v1/mcp/authv2
Transport: Not yet verified (remote MCP server, no local install).
Authentication: OAuth 2.1. No app registration needed: The publisher supports automatic registration for compatible public clients. No additional provider app setup is required.
Claude Code setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
Codex CLI setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
VS Code setup unavailable: The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Do not invent a configuration for this client.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/atlassian/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "atlassian" in that client's MCP configuration, user scope unless I ask otherwise.
Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

Claude Code setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Codex CLI setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

Codex CLI setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "atlassian": {
      "url": "https://mcp.atlassian.com/v1/mcp/authv2"
    }
  }
}

VS Code setup

Review the publisher and client documentation before configuring this server.

Setup unavailable

VS Code setup is unavailable for this catalog entry. The endpoint transport is unverified. Confirm a concrete transport with the publisher before configuring this client. Consult the publisher and client documentation before configuring this server.

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

Publisher evidence (reviewed 2026-08-24): https://support.atlassian.com/atlassian-ai-gateway/docs/set-up-ides/

Client compatibility

Client	Status	Why
Claude Code	Partial	The endpoint transport has not been verified.
Codex	Partial	The endpoint transport has not been verified.
Cursor	Partial	The endpoint transport has not been verified.
VS Code	Partial	The endpoint transport has not been verified.
Claude	Partial	The endpoint transport has not been verified.
Claude Desktop	Partial	The endpoint transport has not been verified.
ChatGPT	Partial	The endpoint transport has not been verified.
Windsurf	Partial	The endpoint transport has not been verified. Windsurf's documentation does not state support for OAuth sign-in.
Gemini CLI	Partial	The endpoint transport has not been verified.
MCP SDK	Partial	The endpoint transport has not been verified.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

Linear — Remote MCP server for Linear issues, projects, comments, cycles, and roadmap planning context. OAuth 2.1
Asana — Asana's hosted MCP server connects assistants to tasks, projects, teams, comments, and work-management context. OAuth 2.1
ClickUp — ClickUp's hosted MCP server connects assistants to tasks, docs, projects, time tracking, and team workflows. OAuth 2.1
monday.com — Reads and updates monday.com boards, items, columns, and users. Uses OAuth, with monday.com API tokens also documented; calls count toward monday.com API limits. OAuth 2.1
Wrike — Searches, creates, and updates Wrike tasks, folders, and projects and reads reporting data. A Wrike admin creates the OAuth app; each user then signs in. OAuth 2.1
Smartsheet — Reads and updates Smartsheet sheets, rows, columns, discussions, workspaces, and reports. Uses OAuth in supported clients, otherwise a personal access token. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Atlassian? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/atlassian.svg)](https://mcptest.io/servers/atlassian/)

HTML

<a href="https://mcptest.io/servers/atlassian/"><img src="https://mcptest.io/badge/server/atlassian.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/atlassian.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/atlassian/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 2:08 PM
Validation detail: Authentication challenge at https://mcp.atlassian.com/v1/mcp/authv2 returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication oauth

Tool inventory

Requires authorization; inventory not observed

The catalog validator lists tools only on servers that answer without credentials. Atlassian asks for OAuth 2.1 sign-in first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.