Honest comparison · Doco and Outline

Doco vs Outline

Choose Outline for a polished, mature team wiki with strong administration and integrations. Choose Doco when MIT licensing and an agent-facing block contract with stable IDs, If-Match, atomic batches, and Markdown round-trip are decisive.

Direct answer

Choose for the job,
not the feature count

The products overlap, but their centers of gravity are different. Start with the source of truth and the people or agents who must maintain it.

Choose Doco when

  • MIT licensing is required for the complete application.
  • Agents need stable block addresses and explicit stale-write failures.
  • The same live document must be accessible through UI, MCP, CLI, and REST.

Choose Outline when

  • You need a polished team wiki with mature administration and integrations.
  • Outline's collections, search, permissions, and hosted experience already match the team.
  • Business Source License terms are acceptable for the intended deployment.
At a glance

The operating differences

DimensionDocoOutline
Primary jobHuman-agent collaborative documentsFast collaborative team knowledge base
Data ownershipMIT licensed and self-hostableSelf-hostable under current BSL 1.1 terms
Human collaborationYjs collaboration, offline browser state, block commentsMature realtime wiki, collections and permissions
Agent access29-tool MCP, CLI and versioned REST block writesBuilt-in MCP server (Streamable HTTP, OAuth or API key) plus REST API
Content modelStable-addressed rich-text blocksMarkdown-compatible collaborative documents
Best fitTeams building agent-maintained operational knowledgeGrowing teams that want a polished conventional wiki

Outline is stronger when

Outline is stronger as a mature conventional team wiki: polished navigation, administration, collections, integrations, and a long-developed hosted experience. It also provides a built-in MCP server at the workspace URL plus /mcp, with OAuth sign-in by default and a workspace-level switch for admins.

Doco is stronger when

Doco uses the permissive MIT license and makes agent safety part of the core data contract: stable block IDs, canonical versions, If-Match writes, atomic batches, idempotency, and rollback.

Migration

Moving from Outline

Migration is medium effort. Markdown content is portable, but collections, permissions, comments, integrations, and administration settings need an explicit mapping rather than a blind bulk import.

  1. 01

    Export representative collections and documents to Markdown with attachments.

  2. 02

    Map Outline collections into Doco knowledge bases and nested folders.

  3. 03

    Import content, then verify tables, images, links, comments, and heading structure.

  4. 04

    Recreate members and permissions; validate an agent read and protected write before cutover.

Run a representative trial first. Keep the original export until links, attachments, permissions, tables, and a restore have all been verified.

Bottom line

Use the smaller truth

Outline is the safer default for teams seeking a mature wiki. Doco is the more open and agent-specialized choice when block-safe machine maintenance is a primary requirement.

01Is Outline open source?

Its current repository uses Business Source License 1.1, whose own text says it is not an open-source license before the change date. It is source-available and self-hostable within those terms.

02Does Outline support MCP?

Yes. Outline has a built-in MCP server at https://<subdomain>.getoutline.com/mcp (self-hosted: your own domain plus /mcp). It supports Streamable HTTP only, signs in with OAuth by default or accepts an API key as an Authorization: Bearer header, and admins can turn it off under Settings → Workspace → AI. Stdio-only clients connect through the mcp-remote proxy.

03How do Outline MCP edits differ from Doco MCP edits?

Outline's update_document tool changes a whole document in replace, append, prepend or patch mode; patch finds an exact Markdown substring and replaces its first occurrence. Doco's MCP tools address individual blocks by stable ID and pass the version the agent read (base_version), so a write against a document that changed in the meantime returns 409 instead of applying.

04Which is easier for a normal team wiki?

Outline is generally more mature and polished for a conventional team wiki. Doco is narrower and optimized for human-agent document operations.