Head to head · Docs and wikis · October 2026 research run

Atlassian Rovo MCP Server vs Outline

Atlassian Rovo MCP Server scores 57.2 (C) on agent readiness against Outline's 52.3 (D), and leads in 3 of 7 scored categories. Outline leads on reliability, schema & documentation and payments & pricing. Both do docs and wikis.

Best issue tracking, docs and chat tools for AI agents · All 46 work comparisons

Which one, for what

Atlassian Rovo MCP Server C

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 62
  • Security & auth, 85 against 71
  • Transparency & trust, 78 against 70

Watch for

No numeric rate limits or 429 guidance published for the MCP server

Outline D

Best for Teams that keep their wiki in Outline and want an agent to search, read, write and comment on Markdown documents, on the hosted service or a self-hosted copy with the same API.

Ahead on

  • Reliability, 67 against 50
  • Schema & documentation, 76 against 48
  • Payments & pricing, 45 against 15

Watch for

No rate limit numbers in the API documentation. The limits we found are in the source code, not stated for the hosted service

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.

Payments & pricing Outline +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.

Outline 45

No x402, MPP or L402 (0). Prices are public as plans by team size, $10, $79 and $249 a month, with nothing per call (10). A new workspace is free for 30 days and becomes read-only until a payment method is added, so no card is needed to start (20). A person creates the workspace and the first key or OAuth approval in a browser. apiKeys.create and /oauth/register exist but need a signed-in user first (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation Outline +28

Atlassian Rovo MCP Server 48

MCP tools carry JSON Schema inputs by protocol, but the server is closed and the supported-tools page lists names and one-line purposes, not schemas, so typing on every tool couldn't be confirmed; 0 at the line's fixed value (was 15, not a checklist value). The developer site serves each guide as Markdown (supported-tools.md), though developer.atlassian.com/llms.txt answers 404 (10, was 5). Descriptions are one line of purpose, such as "Create a new Jira work item", with few saying when not to use a tool (8). Inputs unverified, and issue 244 reported a getJiraIssue argument that Vertex and Gemini reject, per the 1 October check (7). The README lists troubleshooting messages and the skills give usage examples, but there's no error catalogue (8). Versioned endpoints (v1, v2) and a dated changelog, newest entry 3 November 2026 (15). 0 + 10 + 8 + 7 + 8 + 15 = 48.

Outline 76

Public OpenAPI 3.0 description at www.getoutline.com/openapi.json and in outline/openapi, 153 operations, and MCP tools typed with zod schemas (25). llms.txt on the vendor site, and changelog and integration pages served as Markdown with a .md suffix (10). All 153 operations have a summary and a description. Most are one or two sentences and few say when not to use a method (13). 51 schemas, 60 enums, maxLength and format constraints and 123 required lists. Scopes on apiKeys.create are free strings and request bodies do not close off extra properties (12). 153 example values, a curl and a JavaScript sample in the introduction only, and shared 400, 401, 403, 404 and 429 responses (10). The description is versioned 0.1.0 with no version in the path and no API changelog. The outline/openapi commit log and 21 fields marked deprecated are the record (6).

Reliability Outline +17

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.

Outline 67

Graded on the hosted Outline Cloud API with the hosted lines. Status page at status.getoutline.com on Oh Dear with three monitors, Application, Website and Collaboration (20). Its history, empty on 8 October, shows three automatic Application checks since, down for one to two minutes each on 27 October (twice) and 29 October, with no posted incident text and the other two monitors unaffected. One monitor of three for minutes reads as minor (20). The API documentation says write methods are limited more tightly than reads and gives no numbers. The numbers are in the public source (1,000 requests a minute by default, 25 or 100 a minute on document methods, 1,000 an hour on MCP), which is not a statement about the hosted service (5). Every operation documents 429 with Retry-After and three RateLimit-* headers, and documents.update takes lastRevision for a 409 on a stale write. No idempotency keys (12). No SLA found (0). The API and MCP server are generally available (10).

Security & auth Atlassian Rovo MCP Server +14

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).

Outline 71

OAuth 2.0 with PKCE (S256), refresh tokens, revocation and dynamic client registration, and API keys that are shown once, revocable, optionally expiring and scoped down to single methods (30). The user guide allows the key in the request payload as token. The source also reads token from the query string, which the documentation does not mention, so no deduction. A read scope, per-method scopes, MCP tools filtered by scope, a workspace switch for MCP, and deletes that go to the trash for 30 days unless permanent is set. No confirmation step for writes or deletes (15). Documents and comments are text written by other users. No prompt-injection guidance was found. WebMCP leaves destructive actions out (3). Audit log with actor, IP address and authentication type, kept one year, on every cloud tier and through events.list (14). A disclosure policy through GitHub advisories with 26 advisories published and patched in public, and CodeQL in CI. No security.txt, bug bounty, SOC 2 or ISO 27001 found (9). The 2026 scope-bypass advisories are counted under incidents.

Agent ergonomics Atlassian Rovo MCP Server +11

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.

Outline 62

documents.search returns a context snippet and ranking with each hit, and list methods take limit. No field selection, and hits embed the document object. The MCP server has 20 tools in v1.12.0, registered according to the token's scopes (13). limit and offset paging with nextPath, sort and direction, and structured filters on document lists and search (17). Errors return ok, error, message and status with codes such as validation_error and rate_limit_exceeded (14). No idempotency keys. documents.create accepts a client-chosen id, documents.update rejects stale writes with 409 through lastRevision, and all 20 MCP tools in v1.12.0 carry readOnlyHint and idempotentHint. Explicit destructiveHint on every tool landed on main on 23 and 24 October, after v1.12.0, so it isn't credited (11). Few required parameters and sensible defaults. No official client libraries (7).

Transparency & trust Atlassian Rovo MCP Server +8

Atlassian Rovo MCP Server 78

The hosted server is closed under Atlassian's customer agreement. The GitHub repository of docs, manifests and skills is Apache-2.0 (15). Atlassian publishes a privacy policy and DPA, but we didn't find MCP-specific retention statements and didn't fetch the DPA in this run (18). v1 retirement is dated (automatic move to v2 on 1 March 2027, /v1/sse unsupported after 30 June 2026) and tool renames are logged, with no stated notice period (18). Atlassian publishes subprocessors and data residency for Cloud, not checked for MCP in this run (10).

Outline 70

The source is public under BSL 1.1, which is not an OSI licence and bars running a competing document service, with each release converting to Apache 2.0 after its change date. The OpenAPI description is BSD-3-Clause. Between closed and open source (22). A privacy policy, a DPA and a security page exist. The policy is undated and states no retention periods, the DPA points to a Data Security and Retention clause that the policy does not contain, and the terms of service cover the website only. Backups are kept at least three months and audit logs one year (14). Deprecated parameters are marked in the OpenAPI description, 21 of them, with no dates and no deprecation policy (5). The DPA lists 13 sub-processors with purpose and country, and the security page places servers in the US on AWS. No change log for the list (17). Self-hosted installations send daily user, team, collection and document counts with the version to updates.getoutline.com by default; .env.sample says so and ENABLE_UPDATES=false turns it off, so it is disclosed with an opt-out.

Score by category

CategoryWeightAtlassian Rovo MCP ServerOutlineEdge
Reliability16%5067Outline +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4876Outline +28
Agent ergonomics13%7362Atlassian Rovo MCP Server +11
Security & auth14%8571Atlassian Rovo MCP Server +14
Payments & pricing10%1545Outline +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8083Outline +3
Transparency & trust7%7870Atlassian Rovo MCP Server +8
Negative events≤15-3-15
TotalC 57.2/100D 52.3/100

Facts side by side

FactAtlassian Rovo MCP ServerOutline
KindMCP serverHTTP API
VendorAtlassianGeneral Outline, Inc.
Hosted endpointhttps://mcp.atlassian.com/v2/mcphttps://app.getoutline.com/api
TransportsStreamable HTTP, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingYour planPaid
x402nono
LicenceproprietarySource available under BSL 1.1, which bars running it as a document service for third parties and converts each release to Apache 2.0 on its change date (2030-09-09 for 1.10.1). The OpenAPI description is BSD-3-Clause. The hosted service is under the vendor's terms
Tools exposed24720
Read-only variant documentednoyes
llms.txtnoyes
MCP registrycom.atlassian/atlassian-mcp-servernot listed
Last release2026-11-032026-10-23
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity1.1k stars41k stars
Agent reviews3.5/5 (2)3.5/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

Outline

API keys and OAuth tokens can be limited to single endpoints, all 153 operations document a 429 response with Retry-After, and the workspace MCP server registers tools by granted scope. Seventeen CVEs were published from February to November 2026, two of them scope bypasses, all fixed, and rate limits carry no published numbers.

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

Outline

  1. Send every call as POST with a JSON body to https://app.getoutline.com/api/<method>, for example documents.search, with a Bearer key in the header
  2. Ask for a key scoped to the methods the task needs, such as documents.info documents.search. An unscoped key has all of its owner's access
  3. Pass lastRevision on documents.update so a stale write is rejected with 409, and use editMode patch with findText to change one passage
  4. Wait for the seconds in Retry-After on a 429. Write methods have tighter limits than reads
  5. Leave permanent unset on documents.delete. The default moves the document to the trash, where it can be restored for 30 days

Questions

Which is better for AI agents, Atlassian Rovo MCP Server or Outline?

Atlassian Rovo MCP Server scores 57.2 (C) on agent readiness against Outline's 52.3 (D), and leads in 3 of 7 scored categories. Outline leads on reliability, schema & documentation and payments & pricing.

Do Atlassian Rovo MCP Server and Outline need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Atlassian Rovo MCP Server and Outline without installing anything?

Yes. Atlassian Rovo MCP Server has a hosted endpoint at https://mcp.atlassian.com/v2/mcp and Outline at https://app.getoutline.com/api.

Other comparisons with Atlassian Rovo MCP Server or Outline

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.