A
licenseA
qualityC
maintenanceAn MCP server for managing Wiki.js 2.x pages through its GraphQL API, enabling search, read, create, update, move, delete, version history, and asset listing.
13
16 npm
MIT
wikijs-mcp-http
Related Servers
Alternatives to wikijs-mcp-http
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for accessing Wiki.js through its GraphQL API, enabling page management, search, tags, and system info operations.MIT
- AlicenseNot gradedqualityCmaintenanceAn 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.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Wiki.js with full GraphQL API coverage, fine-grained permissions, multi-user support, and deployable on Vercel.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables full management of WikiJS instances, supporting operations like page creation, searching, and updating. It also provides tools for knowledge graph exploration, content summarization, and retrieval of wiki statistics.8 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.-
TDQS
A3.7/5.0
Scored across 29 tools
Disambiguation5/5
Each tool has a distinct verb-noun pair that clearly specifies the resource and action. Potential overlaps like get_page_by_id vs get_page_by_path are resolved by different identifiers. No two tools are ambiguous.
Naming Consistency5/5
All tools follow the consistent pattern 'wikijs_verb_noun' with imperative verbs and lowercase nouns separated by underscores. No mixing of styles or irregular naming.
Tool Count4/5
29 tools is somewhat high for an MCP server, but the breadth of Wiki.js functionality (pages, comments, tags, assets, users, system) justifies the count. Still, it leans towards the heavier side.
Completeness3/5
Core page and comment operations are well-covered with CRUD and additional actions. However, tag creation is missing (only delete/update/list/search), asset management lacks upload/delete, and user management is limited to search and current user. Some notable gaps remain.
Maintenance
ActivityInactive
ResponsivenessNo issues