CodeWiki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEWIKI_CACHE_DIR | No | Custom cache directory path | |
| CODEWIKI_CACHE_TTL | No | Cache TTL in milliseconds (default: 86400000) | 86400000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_repositoryC | Search for a GitHub repository on Google CodeWiki |
| get_repository_docsC | Get documentation for a specific GitHub repository |
| search_documentationC | Search within cached documentation for a repository |
| list_cached_repositoriesB | List all repositories currently cached |
| clear_cacheC | Clear the documentation cache |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap. clear_cache manages cache, get_repository_docs retrieves specific docs, list_cached_repositories shows cached items, search_documentation searches within cached content, and search_repository finds repositories externally. The boundaries are well-defined and unambiguous.
The naming follows a consistent verb_noun pattern (e.g., clear_cache, get_repository_docs, list_cached_repositories) with all tools using snake_case. The only minor deviation is that 'search_repository' might be more consistent as 'search_repositories' to match plural forms, but overall the pattern is highly predictable and readable.
With 5 tools, the count is well-scoped for a documentation-focused server. Each tool serves a specific function in the workflow (caching, retrieving, listing, searching), and there are no redundant or missing tools that would make the set feel too thin or bloated for its purpose.
The toolset covers core documentation workflows effectively: caching management, repository retrieval, listing, and searching both internally and externally. A minor gap is the lack of update or delete operations for cached documentation, but agents can work around this by clearing and re-fetching, and the surface is otherwise complete for the stated purpose.