codewiki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for NLP repo resolution to avoid GitHub API rate limits | |
| CODEWIKI_BASE_URL | No | Base URL for the codewiki service | https://codewiki.google |
| CODEWIKI_MAX_RETRIES | No | Maximum number of retries for failed requests | 3 |
| CODEWIKI_RETRY_DELAY | No | Base retry delay in milliseconds | 250 |
| CODEWIKI_REQUEST_TIMEOUT | No | Request timeout in milliseconds | 30000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codewiki_search_reposC | Search repositories indexed by codewiki.google |
| codewiki_fetch_repoC | Fetch generated wiki content for a repository from codewiki.google |
| codewiki_ask_repoC | Ask a natural-language question about a repository indexed in codewiki.google |
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 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.