A
licenseNot graded
qualityA
maintenanceMCP server for accessing Wiki.js through its GraphQL API, enabling page management, search, tags, and system info operations.
MIT
wikijs-mcp
by sondt2709
Related Servers
Alternatives to wikijs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with Wiki.js via GraphQL API, enabling page management (CRUD, search, publish), user and group management, and blogging workflow with drafts.7 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server for Wiki.js integration, enabling page CRUD operations (create, update, get, list, search, delete, move) via the Wiki.js GraphQL API.-
- AlicenseAqualityDmaintenanceAn MCP server for Wiki.js that enables AI agents to create, read, update, search, list, and move wiki pages via the GraphQL API. It supports surgical section updates and structured content management through named sections.6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides a unified interface to manage Wiki.js pages, users, and groups via GraphQL API, enabling AI agents to create, read, update, and delete content and perform administrative tasks.7 npm14MIT
- AlicenseAqualityDmaintenanceMCP server for Wiki.js that exposes 29 tools for managing pages, comments, tags, assets, users, navigation, and more via HTTP/SSE with built-in mutation safety.2923 npmCreative Commons Zero v1.0 Universal
TDQS
A3.9/5.0
Scored across 13 tools
Disambiguation5/5
Each tool targets a distinct resource and action: pages vs tags vs assets, and within pages there are clear separations between listing, searching, fetching, creating, updating, moving, deleting, and history operations. Potential confusions (list_pages vs search_pages, get_page vs get_page_version) are resolved by clear descriptions.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with lowercase snake_case. The verbs (list, search, get, create, update, move, delete, restore) are uniformly used, and nouns clearly indicate the target resource (pages, tags, assets, page_tree, page_history).
Tool Count5/5
13 tools is a well-scoped number for a Wiki.js content management server. The count covers core page lifecycle, search/navigation, history/restore, and auxiliary tag/asset listing without being excessive or too sparse.
Completeness4/5
The page lifecycle is fully covered (create, read, update, delete, move, list, search, tree, history, restore). The only notable gap is asset management, where only listing is provided (no upload/download/delete), but this is likely outside the tool's primary content-focused purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues