burrow
Related Servers
Alternatives to burrow
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that lets compatible clients discover, read, organize, revise, favorite, create, edit, and delete content in a LeafWiki instance.292MIT
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4325MIT
- AlicenseAqualityDmaintenanceAn MCP server for the un.manned wiki that lets AI agents read and write wiki content securely without exposing API keys, with built-in guardrails for quotas, duplicates, and untrusted content.17MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI assistants search, read, and write to a Wiki.js personal wiki, enabling persistent knowledge management through Markdown pages.3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to add to, search, and manage a wiki knowledge base, enabling AI chat tools to contribute and retrieve information from the wiki via natural language prompts.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.1MIT
TDQS
Scored across 39 tools
Tools are mostly distinct by resource and action, and descriptions clarify overlaps. Some boundaries are close, such as update_page/edit_text/append for content changes and read_links/read_refactor_preview for incoming links, but agents can generally choose correctly.
Names consistently use snake_case with clear read_, write_, and delete_ prefixes. The operation naming is predictable throughout, even when some write actions are verb-only rather than verb_noun.
At 39 tools, the surface is far above the typical 3-15 range and beyond the heavy 16-25 band. While the wiki domain is broad, the tool count creates significant context and selection overhead.
The set covers page CRUD, hierarchy, tags/properties, links and refactoring, revisions, assets, favorites, search, and auth/feature status. Standard wiki workflows have no obvious dead ends.