# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/atlassian-rovo-mcp-vs-linear-mcp
- Markdown: https://www.anchorterminal.com/compare/atlassian-rovo-mcp-vs-linear-mcp.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/compare/atlassian-rovo-mcp-vs-linear-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/atlassian-rovo-mcp-vs-linear-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

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 Server: grade C, 58.1/100, rank #284 of 452. Markdown https://www.anchorterminal.com/tools/atlassian-rovo-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/atlassian-rovo-mcp.json
- Linear MCP: grade C, 54/100, rank #328 of 452. Markdown https://www.anchorterminal.com/tools/linear-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/linear-mcp.json

## 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 | Atlassian Rovo MCP Server | Linear MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 60 | Linear MCP +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 58 | 51 | Atlassian Rovo MCP Server +7 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 38 | Atlassian Rovo MCP Server +25 |
| Security & auth | 14% (17.5 this run) | 85 | 71 | Atlassian Rovo MCP Server +14 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | Linear MCP +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 57 | Atlassian Rovo MCP Server +23 |
| Transparency & trust | 7% (8.8 this run) | 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

1. Connect to `https://mcp.atlassian.com/v2/mcp`, not `/v1/sse`, which stopped being supported after 30 June 2026
2. Call `discover` before execute, since flat tool names have changed under v2
3. Pass `maxResults: 10` on JQL and CQL searches, as Atlassian's own skills require
4. Expect a permission error rather than a tool for deletes until an admin enables delete_jira
5. For headless runs send a service-account key as `Authorization: Bearer`, and note that JSM tools need this route

### Linear MCP

1. Use `https://mcp.linear.app/mcp/readonly` for triage and reporting, it only exposes read tools
2. Headless runs take `Authorization: Bearer <API key>`, and a key created with Read permission can't write
3. Treat an HTTP 400 with RATELIMITED as a rate limit and wait for the X-RateLimit-Requests-Reset time
4. Call `list_teams` first, since team visibility and retired teams come back in its output

## Other comparisons with Atlassian Rovo MCP Server or Linear MCP

- [Atlassian Rovo MCP Server vs Notion MCP](https://www.anchorterminal.com/compare/atlassian-rovo-mcp-vs-notion-mcp.md)