Head to head · Issue tracking · October 2026 research run
Atlassian Rovo MCP Server vs Linear MCP
Atlassian Rovo MCP Server scores 57.2 (C) on agent readiness against Linear MCP's 54.6 (C), and leads in 4 of 7 scored categories. Linear MCP leads on reliability and payments & pricing. Both do issue tracking.
Best issue tracking, docs and chat tools for AI agents · All 46 work comparisons
Which one, for what
Best for Teams already on Atlassian Cloud who want an agent to read and write Jira, Confluence and Bitbucket under the user's permissions with admin audit.
Ahead on
- Agent ergonomics, 73 against 38
- Security & auth, 85 against 75
- Maintenance & community, 80 against 65
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No numeric rate limits or 429 guidance published for the MCP server
Best for Teams on Linear who want an agent to triage, file and update issues under the user's permissions, with a hard read-only option.
Ahead on
- Reliability, 60 against 50
- Payments & pricing, 45 against 15
Watch for
No published tool list, schemas or MCP error responses
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent ergonomics Atlassian Rovo MCP Server +35
Atlassian Rovo MCP Server 73
About 247 tools are named on the supported-tools page (updated 2 November 2026), but v2 returns about 20 primary tools in tools/list, marked (Primary), with discover and the execute meta-tools loading the rest on demand, and admins enable permission groups per product. 11 to 30 tools gives 15, plus 10 back for dynamic loading and toolsets (25, was 20). Search and list tools take maxResults or limit, list tools such as listJiraIssueComments and searchTeams are paginated, and JQL, CQL and field selection filter results (20, was 15). Error messages are documented for IP allowlisting and auth, including 403s from IP rules or scopes, not per tool, so partly met (10 of 20). Read, write and destructive execution of deferred tools are separate meta-tools, but primary write tools are called by name, no readOnlyHint or destructiveHint is named in the tool docs and there is no idempotency guidance, so partly met (10 of 20). One URL and an OAuth sign-in, no SDK, required parameters per tool not published, so partly met (8 of 15). The three partly met lines keep their earlier values pending a rule on in-between values. 25 + 20 + 10 + 10 + 8 = 73.
Linear MCP 38
Tool count not published and not countable without a workspace sign-in, so context cost is scored as unknown (5), plus a read-only endpoint that exposes only read tools (7). The changelog says list_customer_needs returns results one page at a time, other list tools weren't visible (8). No documented error responses for MCP calls (3). The read-only endpoint is safe by construction, and we couldn't check readOnlyHint or destructiveHint (8). One URL with OAuth or a Bearer key, and an official SDK in TypeScript only (7). 12 + 8 + 3 + 8 + 7 = 38.
Payments & pricing Linear MCP +30
Atlassian Rovo MCP Server 15
No x402, MPP or L402 (0). Usage draws Rovo credits. The usage-limits page says single-product lookups are free and enriched Teamwork Graph calls cost 1 to 10 credits each, and the supported-tools page gives 15 to 30 credits for Confluence infographic and visualisation tools, but no per-credit price sits next to them, so plan-level public pricing (10). Atlassian Cloud has free plans with no card, but no page we read says the MCP server is enabled on them, so 0 (was 10, not a checklist value). A person signs in through a browser OAuth flow or creates an API token (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Linear MCP 45
No x402, MPP or L402 (0). No separate MCP charge, and Linear's plan prices are public, from $0 to $16 per user a month before Enterprise (10). The pricing table lists MCP access as included on the Free plan, which needs no card (20). A person signs in through OAuth or creates an API key in the app (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community Atlassian Rovo MCP Server +15
Atlassian Rovo MCP Server 80
Changelog entry on 3 November 2026 (Claude-issued managed auth) (30). Eleven dated entries from 26 September to 3 November, including 13, 16, 20, 23 and 28 October and 2 November (20). Per the 1 October check, not re-read on 4 November, a closed service with a public changelog and a GitHub repository for feedback, where 76 issues were open and the newest ten mostly carried needs-triage with no visible reply (9). server.json names com.atlassian/atlassian-mcp-server 2.0.0, registered in the official MCP registry per the 1 October check (15). The public repository holds manifests and skills with node test scripts and one pinned dev dependency, but no CI workflow (its .github folder holds only issue forms) and no package to install, so the line is partly met and keeps its earlier 6 of 10 pending a rule on in-between values. 30 + 20 + 9 + 15 + 6 = 80.
Linear MCP 65
Last MCP server change on 22 October 2026 (users assigned by part of their name, customer lookup by domain and external IDs), 13 days before 4 November (30). Four dated MCP entries since 6 August: 13 August (enterprise-managed authorisation through Okta), 14 September (list_teams and get_team report visibility and retiredAt), 8 October (new list_customer_needs tool) and 22 October (20). Closed service with a public changelog and in-app support, no public issue tracker for the MCP server (10). Registry line 15 to 0: the 1 October reading of app.linear/linear came from the registry's JSON API, which this run doesn't use, and no first-hand page names the entry (0). No package to install, and the TypeScript SDK's health wasn't checked (5, carried). 30 + 20 + 10 + 0 + 5 = 65.
Reliability Linear MCP +10
Atlassian Rovo MCP Server 50
Statuspage at rovo.status.atlassian.com with an MCP component, read from the page and history.atom (20). In the 90 days from 6 August the feed has two MCP incidents, degraded performance with timeouts on 21 October (15:30 to 18:25 UTC) and intermittent errors for some users on 22 October (14:42 to 18:16 UTC), both degradation rather than an outage, plus the 18 August Rovo chat streaming incident, which doesn't name MCP. Minor only (20). No numeric rate limits for the MCP server in the docs, README or supported-tools page (0). No 429 or retry guidance found (0). No SLA that names the MCP server found (0). v2 has been GA since 8 September 2026 (10). 20 + 20 + 0 + 0 + 0 + 10 = 50.
Linear MCP 60
incident.io status page at linearstatus.com with US and EU components for the app, API and integrations and an RSS history, but no MCP component (15, the value for a vendor page with no component for the product). Minor incidents only from 6 August: the docs site on 12 August, Codex sessions on 14 August, agent automation delays on 19 August, Android push on 1 September, degraded US performance on 5 September, an EU sync failure on 1 October (EU application only), Slack integrations on 28 October, a 15-minute partial outage loading the apps on 27 October and project pages on 30 October (20). The GraphQL API publishes limits, 2,500 requests an hour per user on an API key and 5,000 on OAuth, but the MCP docs don't say whether these apply (10, carried). The rate-limit page now says a limited GraphQL request returns HTTP 429 with RATELIMITED and a Retry-After header, where on 1 October it said HTTP 400; the MCP docs still say nothing on limits or retries, so the partial 5 is carried (the line's 10 for Retry-After alone if the API page is read as covering MCP). Uptime SLA listed on the Enterprise column of the pricing page with no SLA document found (0). The MCP server carries no preview label; only Claude auto-connect is marked beta (10). 15 + 20 + 10 + 5 + 0 + 10 = 60.
Security & auth Atlassian Rovo MCP Server +10
Atlassian Rovo MCP Server 85
OAuth 2.1 bounded by the user's existing product permissions, with scopes per permission group, or API tokens in the Authorization header (Basic email and token, or a service-account Bearer key), never in the URL. Personal API tokens carry the user's full reach (26). Admins grant permission groups per product, delete_jira and manage_jira are off by default, destructive calls go through their own meta-tool, and admins can block client domains and enforce IP allowlists (16). The README and SECURITY.md describe prompt injection and tool poisoning and ask for human confirmation on destructive actions, guidance only (10). Every tool call lands in the organisation audit log under Rovo MCP User Actions (15). security.txt valid (Expires 4 February 2027, read on 4 November), a private disclosure route with a bug bounty named in SECURITY.md, and SOC 2 and ISO 27001 on the trust page, though the page doesn't say Rovo or MCP is in scope (18).
Linear MCP 75
OAuth 2.1 with dynamic client registration and a read scope that, in Linear's words, means the token can't reach write APIs, or API keys that can be created with Read permission only, sent in the Authorization header (30). A read-only endpoint plus read-only keys and scopes, but no confirmation step for writes on the full endpoint (16). Tools return issue and comment text written by anyone in the workspace, and we found no prompt-injection guidance (3). Workspace audit logs cover the last 3 months, admins can see active MCP connections and explicit OAuth token revocations are logged since 14 September 2026, but we found no per-call MCP log (8). Programme 14 to 18: security.txt valid (Expires 31 December 2027, read on 4 November) pointing to a disclosure policy that pays rewards for valid vulnerabilities and names the MCP server (mcp.linear.app) in scope, with SOC 2 Type II and ISO/IEC 27001:2022 on the security page and no public advisories found (18, as atlassian-rovo-mcp with security.txt, a bounty and SOC 2 and ISO 27001). 30 + 16 + 3 + 8 + 18 = 75.
Score by category
| Category | Weight | Atlassian Rovo MCP Server | Linear MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 60 | Linear MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 48 | 51 | Linear MCP +3 |
| Agent ergonomics | 13% | 73 | 38 | Atlassian Rovo MCP Server +35 |
| Security & auth | 14% | 85 | 75 | Atlassian Rovo MCP Server +10 |
| Payments & pricing | 10% | 15 | 45 | Linear MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 65 | Atlassian Rovo MCP Server +15 |
| Transparency & trust | 7% | 78 | 76 | Atlassian Rovo MCP Server +2 |
| Negative events | ≤15 | -3 | -3 | |
| Total | C 57.2/100 | C 54.6/100 |
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 | 247 | none |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | com.atlassian/atlassian-mcp-server | app.linear/linear |
| Last release | 2026-11-03 | 2026-10-22 |
| Terms last updated | no date given | 2026-06-09 |
| Privacy policy last updated | no date given | 2025-03-17 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1.1k stars | none |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Atlassian Rovo MCP Server higher.
| Reviewer | Atlassian Rovo MCP Server | Linear MCP |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 A gateway over 200 tools with one-line definitions | 2/5 Three tool names, all from the changelog |
| WardenSecurity auditor | 4/5 Deletes start off, and every call reaches the audit log | 4/5 Three ways to make the token read-only |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Atlassian Rovo MCP Server
Atlassian's hosted MCP server returns about 20 primary tools and loads the rest of a catalogue of about 247 on demand, with every call in the organisation audit log. No rate limits, 429 guidance or tool annotations are published, and tool removals in September and October were announced on the day or after they took effect.
Linear MCP
OAuth 2.1 with dynamic client registration, a read scope and a read-only endpoint let an agent connect without a registered app and without write access. Linear publishes no tool list, schemas or MCP error responses, and its rate-limit and retry guidance covers the GraphQL API without saying whether it applies to MCP calls.
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 - On a RATELIMITED error, wait for the Retry-After seconds or the X-RateLimit-Requests-Reset time before retrying
- Call
list_teamsfirst, since team visibility and retired teams come back in its output
Questions
Which is better for AI agents, Atlassian Rovo MCP Server or Linear MCP?
Atlassian Rovo MCP Server scores 57.2 (C) on agent readiness against Linear MCP's 54.6 (C), and leads in 4 of 7 scored categories. Linear MCP leads on reliability and payments & pricing.
Do Atlassian Rovo MCP Server and Linear MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Atlassian Rovo MCP Server and Linear MCP without installing anything?
Yes. Atlassian Rovo MCP Server has a hosted endpoint at https://mcp.atlassian.com/v2/mcp and Linear MCP at https://mcp.linear.app/mcp.
Other comparisons with Atlassian Rovo MCP Server or Linear MCP
- Asana vs Atlassian Rovo MCP Server
- Asana vs Linear MCP
- Atlassian Rovo MCP Server vs Basecamp
- Atlassian Rovo MCP Server vs ClickUp
- Atlassian Rovo MCP Server vs Financial Cents MCP
- Atlassian Rovo MCP Server vs monday.com
- Atlassian Rovo MCP Server vs ONES
- Atlassian Rovo MCP Server vs OpenProject
- Atlassian Rovo MCP Server vs Plane
- Atlassian Rovo MCP Server vs Redmine
- Atlassian Rovo MCP Server vs Roma
- Atlassian Rovo MCP Server vs Shortcut
- Atlassian Rovo MCP Server vs Taiga
- Atlassian Rovo MCP Server vs Taskade
- Atlassian Rovo MCP Server vs Teamwork.com
- Atlassian Rovo MCP Server vs Todoist
- Atlassian Rovo MCP Server vs Trello
- Atlassian Rovo MCP Server vs Wrike
- Atlassian Rovo MCP Server vs YouTrack
- Basecamp vs Linear MCP
- ClickUp vs Linear MCP
- Financial Cents MCP vs Linear MCP
- Linear MCP vs monday.com
- Linear MCP vs ONES
- Linear MCP vs OpenProject
- Linear MCP vs Plane
- Linear MCP vs Redmine
- Linear MCP vs Roma
- Linear MCP vs Shortcut
- Linear MCP vs Taiga
- Linear MCP vs Taskade
- Linear MCP vs Teamwork.com
- Linear MCP vs Todoist
- Linear MCP vs Trello
- Linear MCP vs Wrike
- Linear MCP vs YouTrack
- Atlassian Rovo MCP Server vs Notion MCP
- Atlassian Rovo MCP Server vs Outline
Machine-readable
- This page as Markdown
/compare/atlassian-rovo-mcp-vs-linear-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/atlassian-rovo-mcp.json·/api/v1/tools/linear-mcp.json - From a terminal
anchor compare atlassian-rovo-mcp linear-mcp(the CLI) - Over MCP
compare_tools {"a": "atlassian-rovo-mcp", "b": "linear-mcp"}at/mcp, no key