Head to head · Issue tracking · October 2026 research run
Atlassian Rovo MCP Server vs Linear MCP
Atlassian Rovo MCP Server has a score of 58.1 (C) against Linear MCP's 54 (C). Both do issue tracking. The largest gap is agent ergonomics, 25 points.
Atlassian Rovo MCP ServerAtlassian · MCP server
C58.1/100#284 of 452
Linear MCPLinear · MCP server
C54/100#328 of 452
Which one, for what
Pick Atlassian Rovo MCP Server for
- schema & documentation (+7)
- agent ergonomics (+25)
- security & auth (+14)
- maintenance & community (+23)
- transparency & trust (+8)
Pick Linear MCP for
- reliability (+10)
- payments & pricing (+10)
Score by category
| Category | Weight this run | Atlassian Rovo MCP Server | Linear MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 60 | Linear MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 58 | 51 | Atlassian Rovo MCP Server +7 |
| Agent ergonomics | 13%16.2 | 63 | 38 | Atlassian Rovo MCP Server +25 |
| Security & auth | 14%17.5 | 85 | 71 | Atlassian Rovo MCP Server +14 |
| Payments & pricing | 10%12.5 | 20 | 30 | Linear MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 57 | Atlassian Rovo MCP Server +23 |
| Transparency & trust | 7%8.8 | 81 | 73 | Atlassian Rovo MCP Server +8 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 58.1 · C | 54 · C |
Facts side by side
| Fact | Atlassian Rovo MCP Server | Linear MCP |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Atlassian | Linear |
| Hosted endpoint | https://mcp.atlassian.com/v2/mcp | https://mcp.linear.app/mcp |
| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | OAuth or key |
| Pricing | Your plan | Your plan |
| x402 | no | no |
| Licence | proprietary | proprietary |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | com.atlassian/atlassian-mcp-server | app.linear/linear |
| Last release | 2026-09-30 | 2026-08-13 |
| Popularity | 1.1k stars | none |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
Verdicts
Atlassian Rovo MCP Server
v2 gateway exposes primary tools plus discover and three execute meta-tools, and the rest load on demand. No numeric rate limits or 429 guidance published for the MCP server.
Linear MCP
OAuth 2.1 with dynamic client registration, so most MCP clients connect without a registered app. No published tool list, schemas or MCP error responses.
Before you call either
Atlassian Rovo MCP Server
- Connect to
https://mcp.atlassian.com/v2/mcp, not/v1/sse, which stopped being supported after 30 June 2026 - Call
discoverbefore execute, since flat tool names have changed under v2 - Pass
maxResults: 10on JQL and CQL searches, as Atlassian's own skills require - Expect a permission error rather than a tool for deletes until an admin enables delete_jira
- For headless runs send a service-account key as
Authorization: Bearer, and note that JSM tools need this route
Linear MCP
- Use
https://mcp.linear.app/mcp/readonlyfor triage and reporting, it only exposes read tools - Headless runs take
Authorization: Bearer <API key>, and a key created with Read permission can't write - Treat an HTTP 400 with RATELIMITED as a rate limit and wait for the X-RateLimit-Requests-Reset time
- Call
list_teamsfirst, since team visibility and retired teams come back in its output