← Explore all mcp servers

TEAM COLLABORATION / Atlassian

Atlassian Rovo MCP

Searches connected Atlassian work and lets an authorized client create or update work items and pages through the current Rovo MCP endpoint.

“Atlassian Rovo MCP Server”

01 / THE REASONING

Why this made the selection.

  • Connects Jira and Confluence work with related Atlassian context in a single documented service.
  • The current v2 setup distinguishes user permissions and Rovo credit consumption.
  • Atlassian’s setup page points clients at the v2 remote URL and says OAuth 2.1 keeps actions inside the user’s existing product permissions.
  • The same page says MCP calls that retrieve data or generate insights consume Rovo credits from the shared organization pool.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/ (setup, access and capability sections)
  • Official MCP Registry publisher entry: endpoint matched against official setup documentation
  • https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/
  • https://registry.modelcontextprotocol.io/v0.1/servers?search=atlassian&version=latest&limit=100
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • The current documented endpoint is /v2/mcp, with client-specific setup and an optional flat-tool-list mode.
  • OAuth is the primary setup; API-token authentication is a separate documented path.
  • The documented server URL is https://mcp.atlassian.com/v2/mcp, and the registry entry com.atlassian/atlassian-mcp-server describes search and management across Jira, Confluence, Loom, and more.
  • OAuth 2.1 is the documented authorization method, and clients act on connected products only with the user’s existing permissions.
  • The page says those MCP calls consume Rovo credits, and it tells readers to review high-impact changes and monitor audit logs. It does not grant access beyond the user’s existing controls.
  • The setup guide provides tools=all as a client compatibility option and distinguishes MCP calls that consume Rovo credits.

Not established by this review

  • Authentication, service availability and tool execution were not tested.
  • The hosted implementation source and licence were not established.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

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

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Add https://mcp.atlassian.com/v2/mcp using the official guide for your client.
  2. Complete OAuth and confirm the intended site/product access before authorizing changes.
  3. The command above is the guide’s Claude Code setup; run /mcp in a Claude Code session to authenticate. It was not run.

Before you start

  • An Atlassian account with access to the relevant connected products and an eligible MCP client.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

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

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/

    Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample

  2. https://registry.modelcontextprotocol.io/v0.1/servers?search=atlassian&version=latest&limit=100

    Supports: transports

Evidence & Ask