Atlassian: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Atlassian at mcp.atlassian.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

Company	Atlassian
Domain	atlassian.com
Category	Productivity (Ora leaderboard category)
MCP server	Sign-in required (OAuth with client registration)
Tranco rank	595 on the list of 4 November 2026
Ora score	69, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for atlassian.com, a vendor-published score)
Company found through	the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Last verified	4 November 2026

MCP server

Endpoint	`https://mcp.atlassian.com/v1/mcp`
How it was found	listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Transport	streamable-http
HTTP status	401
Connected	4 November 2026, 20:01 UTC
Handshake time	771 ms over 1 attempt
Documentation	support.atlassian.com

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

19:55:55Z https://mcp.atlassian.com/v1/mcp sent initialize result auth-required (HTTP 401) 551 ms
20:01:30Z https://mcp.atlassian.com/v1/mcp sent initialize result auth-required (HTTP 401) 771 ms

Authentication

Auth type	OAuth with client registration
What the challenge said	`Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token"`
Authorization server metadata	mcp.atlassian.com
Registration endpoint	`https://mcp.atlassian.com/v1/register`
Auth as listed by a registry	OAuth2.1 (a claim, not checked by connecting)

The sign-in route, step by step

Request https://mcp.atlassian.com/v1/mcp without a token. It answers 401 and a WWW-Authenticate header.
Read the protected resource metadata to find the authorization server.
Register a client at the registration endpoint https://mcp.atlassian.com/v1/register (dynamic client registration), so no human has to create an app first.
Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Atlassian. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
Surface	Result
OpenAPI file	No OpenAPI file at the root paths checked.
WebMCP in the initial HTML	Not detected on the home page by the shared crawl.
MCP discovery file	Not found (the crawl got a non-200 answer).
A2A agent card	Not found (the crawl got a non-200 answer).
A2A agent card (older path)	Not found (the crawl got a non-200 answer).
agents.json	Not found (the crawl got a non-200 answer).
OAuth authorization server metadata	Not found (the crawl got a non-200 answer).
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	Yes: com.atlassian/atlassian-mcp-server
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	Yes
Smithery	Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
Glama	Not checked: Glama's API needs a key and attribution terms.