mcp-digger
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_DIR | No | Override cache directory | .digger/cache |
| DIGGER_CONFIG | No | Override config file path | .digger/config.json |
| MANAGED_SOURCE_DIR | No | Override managed clone directory | .digger/source |
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 |
|---|---|
| dig_statusA | Health-check tool — validates mcp-digger configuration and tests git connectivity for all configured repositories. Call this to verify setup is correct, diagnose auth or network issues, or confirm repos are reachable before digging into source. |
| dig_initA | Bootstrap mcp-digger by creating a starter config file. Only available when no config exists. After running, edit the generated template with your repository details, then restart the MCP server to activate all tools. |
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 2 tools
The two tools have clearly distinct purposes: dig_init creates a starter config, while dig_status validates connectivity and configuration. There is no overlap.
Both tools consistently use the 'dig_' prefix and verb_noun pattern (init, status) in snake_case, making the naming predictable.
With only two tools, the server feels thin for a tool named 'digger' that presumably should provide git analysis capabilities. The description hints at more tools after configuration, but currently only init and status are defined.
The server lacks core digging functionality (e.g., analyzing commits, blame, changes). It only covers initialization and health-check, leaving a major gap in the expected tool surface.