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 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.
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.
| Dimension | Doco | Outline |
|---|---|---|
| Primary job | Human-agent collaborative documents | Fast collaborative team knowledge base |
| Data ownership | MIT licensed and self-hostable | Self-hostable under current BSL 1.1 terms |
| Human collaboration | Yjs collaboration, offline browser state, block comments | Mature realtime wiki, collections and permissions |
| Agent access | 29-tool MCP, CLI and versioned REST block writes | Built-in MCP server (Streamable HTTP, OAuth or API key) plus REST API |
| Content model | Stable-addressed rich-text blocks | Markdown-compatible collaborative documents |
| Best fit | Teams building agent-maintained operational knowledge | Growing teams that want a polished conventional wiki |
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 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 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.
Export representative collections and documents to Markdown with attachments.
Map Outline collections into Doco knowledge bases and nested folders.
Import content, then verify tables, images, links, comments, and heading structure.
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.
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.
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.
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.
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.
Outline is generally more mature and polished for a conventional team wiki. Doco is narrower and optimized for human-agent document operations.