mcp-outline
Related Servers
Alternatives to mcp-outline
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Outline that gives Claude the ability to search and read documents from your Outline instance.MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables reading, writing, and searching documents in Outline via its API. It supports document management, full-text search, and collection organization using Markdown formatting.815 npm17MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that turns a self-hosted Outline wiki into an AI team's knowledge base, providing tools for search, read, write, and organization with per-user permissions via client-supplied API tokens.MIT
- FlicenseBqualityCmaintenanceA Model Context Protocol server that exposes an Outline knowledge base to MCP clients. It enables searching, reading, writing, and commenting on documents through natural language.9-
- FlicenseNot gradedqualityDmaintenanceIntegrates Outline Wiki with AI assistants like Claude Desktop, enabling search, create, update documents, list collections, and more.1-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for interacting with Outline document management, supporting search, read, create, edit, archive documents, collections, comments, and backlinks.30MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct action-resource pairing: list/search/get/list-collections for reads, create/update/move/archive for writes. The only mild overlap is list_documents vs search_documents, but descriptions make the boundary explicit (metadata listing vs full-text search with snippets) and search_documents points to get_document for bodies.
All nine tools follow a strict snake_case verb_noun pattern (list_collections, get_collection, list_documents, create_document, update_document, move_document, archive_document, search_documents, get_document) with no exceptions or mixed conventions.
Nine tools is well-scoped for an Outline document service, covering both the collection and document resources without redundancy. Every tool earns its place, none feels like filler.
The document lifecycle is largely covered (list, search, get, create, update, move, archive), plus collection reads. However, there is no collection creation/update and no explicit unarchive/restore or hard delete, leaving minor gaps agents must work around; archive is documented as reversible but no restore tool is exposed.