Atlassian Rovo MCP Server
com.atlassian/atlassian-mcp-serveratlassian.comremotev2.0.0
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
No tools shown: it asks for sign-in first
This server lists its tools only to a signed-in client (OAuth). anlyon.dev never signs in or sends credentials, so it cannot read them, and nothing here is a judgement of the server. Already use it? Copy its tools/list from your client and check it here: the same labels, worked out in your browser.
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.
What the Atlassian Rovo MCP Server can do
The Atlassian Rovo MCP Server is published by atlassian.com, a domain the MCP Registry verified. It asks for sign-in (OAuth) before it lists its tools, and anlyon.dev never signs in, so its tools are not shown.
Scan status: sign-in required
Scopes it asks for: delete:jira:agent-interface, email, manage:jira:agent-interface, offline_access, read:account, read:all:twg, read:artifacts:agent-interface, read:assets:agent-interface, read:bitbucket:agent-interface, read:capacity-planning:agent-interface, read:confluence:agent-interface, read:focus:agent-interfac…
Last attempt Nov 9, 2026, 18:18 UTC.
Have its tools/list output? Check it yourself.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 13, 2026, 11:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp
- RFC 9728 protected resource metadata
- https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp
- Authorization servers
- https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpclaude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpRun in a terminal.
Badge
A badge for your README that links back to this page.
Badge
[](https://anlyon.dev/servers/com.atlassian/atlassian-mcp-server)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:51 UTC.
Atlassian Rovo MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Atlassian Rovo MCP Server safe?
- anlyon.dev has not been able to list its tools, so it has no classes or findings for it yet. It asks for sign-in before listing them. Paste its tools/list output into https://anlyon.dev/scan to check it yourself.
Who publishes the Atlassian Rovo MCP Server?
- atlassian.com (domain verified by the MCP Registry).