Outline Wiki MCP Server
Related Servers
Alternatives to Outline Wiki MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityNot gradedmaintenanceEnables LLMs to interact with Outline wiki for document management, search, collections, and comments, with optional AI-powered features including RAG-based Q\&A and content summarization.37336 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage documents and collections in Outline wiki through natural language commands.1-
- FlicenseNot gradedqualityDmaintenanceIntegrates Outline Wiki with AI assistants like Claude Desktop, enabling search, create, update documents, list collections, and more.1-
- AlicenseAqualityCmaintenanceEnables interaction with the Outline knowledge base API, allowing search, document and collection management, comments, and more.16Apache 2.0
- FlicenseBqualityDmaintenanceEnables Claude Code to search and retrieve documents from an Outline knowledge base.2-
- AlicenseNot gradedqualityDmaintenanceConnects MCP clients to Outline workspaces, enabling agents to safely read, update, and manage documentation through structured tools.13 npm2MIT
TDQS
Scored across 37 tools
Most tools have distinct purposes, but some overlap exists. For example, 'search_documents' and 'find_related' both involve document discovery, though 'find_related' is semantic. 'archive_document' and 'delete_document' (with permanent=false) both involve removal, but descriptions clarify differences. Overall, descriptions help, but a few tools could be confused without careful reading.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_document', 'list_collections', 'update_document', and 'delete_collection'. All tools use snake_case, and verbs are predictable (e.g., add, archive, ask, batch, create, delete, export, get, list, move, restore, search, sync, unarchive, update). No deviations or mixed conventions are present.
With 37 tools, the count is borderline high for a wiki server, feeling heavy compared to typical well-scoped sets of 3-15 tools. While the tools cover extensive operations, it may overwhelm agents. However, given the domain's complexity, it's not extreme, but leans toward too many for optimal coherence.
The tool set provides complete CRUD/lifecycle coverage for documents and collections, including creation, reading, updating, deletion, archiving, restoration, and export. It also includes advanced features like AI-powered search, summarization, diagram generation, and batch operations. No obvious gaps exist; agents can handle all core wiki workflows without dead ends.