pick.tools

Atlassian atlassian

Search, create and manage Jira and Confluence content.

Auth
OAuth
Health
up probed
Vendor
atlassian.com
Categories
productivity, dev-tools
Docs
https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/

Endpoint

https://mcp.atlassian.com/v2/mcp (streamable-http)

Authentication

OAuth. pick.tools does not relay OAuth servers in v1; connect your client to Atlassian directly and sign in there.

From an agent (picker mode): connect your MCP client directly to https://mcp.atlassian.com/v2/mcp (OAuth); pick.tools does not relay OAuth servers in v1

Tools (0)

No tools cached. pick.tools does not relay this server.

Calls, last 30 days

2026-10-07 to 2026-11-05 · 0 calls

No relayed calls in the last 30 days.

Probes

Last 7, newest at the top. Probes carry no credential.
Probed at Outcome HTTP Latency ms
oauth 401 101
oauth 401 103
oauth 401 89
oauth 401 101
oauth 401 96
oauth 401 105
oauth 401 104

Connect directly

Your client signs in to Atlassian itself; pick.tools is not in the path.

Claude Code

claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp

JSON config (mcpServers)

{
  "mcpServers": {
    "atlassian": {
      "type": "http",
      "url": "https://mcp.atlassian.com/v2/mcp"
    }
  }
}

For Atlassian

pick.tools probes this server hourly, without a credential, as pick.tools-probe/1 (+https://pick.tools/docs/for-vendors). For vendors lists the egress IPs and how to opt out.