Deepwiki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPWIKI_MAX_RETRIES | No | Maximum retry attempts for failed requests | 3 |
| DEEPWIKI_RETRY_DELAY | No | Base delay for retry backoff in milliseconds | 250 |
| DEEPWIKI_MAX_CONCURRENCY | No | Maximum concurrent requests | 5 |
| DEEPWIKI_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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deepwiki_fetchC | Fetch a deepwiki.com repo and return Markdown |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly distinct by default.
The single tool name follows a consistent verb_noun pattern (deepwiki_fetch), and with no other tools to compare, there is no inconsistency in naming conventions.
One tool is too few for a server with the apparent purpose of fetching and processing DeepWiki repos, as it lacks operations like search, list, or update, making the scope feel thin and incomplete.
The tool surface is severely incomplete for a DeepWiki server; it only provides a fetch operation without any CRUD lifecycle coverage, search capabilities, or other essential functions for repo management.