No user-submitted related servers found.
Scored across 62 tools
Each tool pairs a clear resource (page, tag, asset, comment, user, group, site) with a distinct action, and near-overlapping pairs like search_pages/grep_pages or get_page_tree/get_navigation_tree are explicitly differentiated in their descriptions. An agent can reliably tell which tool to call.
Tools consistently use snake_case verb_noun names: list_* for collections, get_* for single entities, create_*/update_*/delete_* for CRUD, and domain-specific verbs like move/restore/assign/rebuild. Even unusual names like grep_pages or convert_page_editor follow the same pattern.
62 tools far exceeds the 50+ threshold and would impose a heavy context and selection burden on an agent. The set is comprehensive, but this is a kitchen-sink Wiki.js admin API rather than a well-scoped MCP server; splitting it into page, user, asset, and system servers would be better.
The surface provides strong lifecycle coverage for pages, comments, users, and groups, including history, versions, search, and maintenance operations. Minor gaps remain: assets have upload/rename/delete but no download/read tool, asset folders cannot be deleted, and navigation can be read but not edited.