docmost-mcp
Related Servers
Alternatives to docmost-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to search, read, write, and organize pages, spaces, comments, attachments, labels, and member access in self-hosted Docmost Community Edition wikis via its internal HTTP API, using Markdown for page and comment bodies.411,409 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to self-hosted Docmost documentation through tools for listing spaces, searching content, and retrieving pages in Markdown format. It facilitates seamless documentation lookup and content retrieval within MCP-compatible clients.5MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search, read, write, and organize content in self-hosted Docmost Community Edition wikis through MCP clients like Cursor and Claude.411,409 npm3MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents read/write access to a self-hosted Docmost wiki through its REST API.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides a bridge to self-hosted Docmost Community, enabling access to spaces, pages, and search, as well as creating and updating pages via Markdown. It also offers REST endpoints alongside MCP tools.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients such as Claude Code to a self-hosted La Suite Docs instance, letting them full-text search, browse by recency or favorites, read documents as markdown, and create or edit content (including single-section edits). Favorited documents are also exposed as MCP resources so they can be @-mentioned straight into context.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: browsing spaces, browsing page hierarchy, full-text search, single-page fetch, page creation, and page editing. list_pages (hierarchical browsing) and search_pages (full-text lookup) have clearly separate intents, and get_page vs list_pages vs search_pages are easy to tell apart by their outputs.
All six tools follow a clean verb_noun snake_case pattern (list_spaces, list_pages, search_pages, get_page, create_page, update_page). Verbs are used consistently for their action type and no naming style is mixed.
Six tools is well-scoped for a wiki/docs service, covering the natural read/browse/search/create/edit verbs without redundancy. Each tool clearly earns its place in the set.
Create, read (get/list/search), and update are all covered with Markdown fidelity, which handles the core lifecycle. However, there is no delete or archive operation and no explicit page-move/reparent tool, leaving a minor lifecycle gap agents cannot work around.