codewiki-mcp
Related Servers
Alternatives to codewiki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server to query a Git-hosted Wiki, offering tools to list, search, and read Markdown documents via Codex or VS Code.MIT
- FlicenseBqualityCmaintenanceA MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!227-
- AlicenseNot gradedqualityBmaintenanceMCP 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 gradedqualityCmaintenanceMCP server for Wiki.js integration, enabling AI assistants to create, read, update, delete, search, and move wiki pages via natural language.1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.MIT
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4320MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: 'ask_repo' handles natural-language queries, 'fetch_repo' retrieves wiki content, and 'search_repos' finds indexed repositories. The descriptions make it easy to differentiate between querying, fetching, and searching functions.
All tools follow a perfect 'codewiki_verb_noun' pattern with consistent snake_case formatting. The prefix 'codewiki_' is uniformly applied, and verbs ('ask', 'fetch', 'search') are distinct and appropriately paired with nouns ('repo' or 'repos').
With only 3 tools, the set feels thin for a server focused on repository wiki interactions. While the tools cover basic operations, the scope might benefit from additional tools for updates, deletions, or more granular queries to handle common workflows more comprehensively.
The tools provide good coverage for core operations: searching repositories, fetching content, and asking questions. However, there are minor gaps such as lacking update or deletion tools for wiki content, which could limit agent capabilities in full lifecycle management scenarios.