A
licenseB
qualityD
maintenanceEnables AI assistants to search and retrieve content from WikiJS knowledge bases, allowing integration with your Wiki through simple search and retrieval tools.
4
28 npm
6
MIT
@growi/mcp-server
Officialby growilabs
Related Servers
Alternatives to @growi/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceExposes any project wiki to AI assistants with features like fuzzy search, content search, lazy loading, and auto-reload.6ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, retrieve, and optionally edit pages in a WikiJS knowledge base via the Model Context Protocol.39 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to search, find related content, and retrieve pages from an Obsidian wiki via vector-backed tools, with optional connectors for personal data sources.2 npmMIT
Ambientofficial
AlicenseNot gradedqualityBmaintenanceEnables AI apps like Claude, ChatGPT, Copilot, Claude Code and Codex to read and write a shared company wiki over MCP, where meetings, work sessions and notes become living pages about people, projects and decisions. It also serves search, briefs, transcripts, decisions and action items, and lets teams connect their own git-hosted team wiki.1MIT- AlicenseAqualityCmaintenanceEnables AI assistants to search, browse, and read Wiki.js 2.x pages through the GraphQL API in a read-only way, allowing them to query a company knowledge base.6MIT
TDQS
B3.2/5.0
Scored across 31 tools
Disambiguation5/5
Every tool has a clear and distinct purpose. For example, getPage, getPageInfo, getPageListingChildren, and getPageTag all target different aspects of a page. Similarly, share link operations are separate from comment operations. There is no discernible overlap.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern in camelCase (e.g., createPage, deleteShareLink, getComments). One outlier is 'pageListingInfo' which lacks a verb, deviating from the pattern. Overall, the naming is largely consistent and predictable.
Tool Count2/5
With 31 tools, the count exceeds the 25+ threshold identified as 'too many' in the scale. While the domain (a wiki system) may require many operations, this number feels heavy and could overwhelm an agent, leading to potential miselection.
Completeness4/5
The tool set covers most lifecycle operations for pages, comments, share links, tags, and revisions. A minor gap is the lack of an update comment tool, but agents can work around this by using removeComment and addComment. Otherwise, the surface is well-rounded.
Maintenance
ActivitySlowing
ResponsivenessLimited data