# mcp-digger [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/janeksm/mcp-digger  
**GitHub Stars:** 0  
**npm Downloads (last month):** 142  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-digger

## Description
Progressive on-demand access to .NET NuGet package source for AI coding agents.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-digger": {
    "command": "npx",
    "args": ["-y","mcp-digger"]
  }
}
```

## Documentation

## What mcp-digger does

The mcp-digger MCP server makes private .NET library source available to MCP-compatible coding agents. It focuses on NuGet-style repositories containing C# projects and source files, rather than serving as a general source indexer for languages such as Python, TypeScript, Java, or Go.

Repositories can be configured by package name, a package-name wildcard, or automatic discovery of non-test projects below a source directory. The server can follow local sibling `ProjectReference` dependencies and can work with managed Git clones or read-only repositories already present on disk.

## How it works

The mcp-digger MCP server organizes access into progressively deeper levels. An agent can begin with status and repository discovery, inspect package documentation and file lists, search indexed symbols, view public API signatures, and only then request a complete source file. This reduces the need to load entire repositories when a declaration or relationship is enough.

Its ten tools cover health checks, repository and package discovery, symbol lookup, signature extraction, source retrieval, cache rebuilding, and initial configuration. `dig_lookup` supports declaration searches, finding types that implement an interface or extend a base class, and locating files that reference a type. Lookup can operate across packages.

Managed repositories may use HTTPS or SSH Git URLs and can track the default branch or a configured branch. Local repository mode does not fetch or modify the files. The server stores managed clones outside the project tree, while local repositories are treated as read-only.

## Setup and configuration

Install globally with `npm install -g mcp-digger`, or run it with `npx mcp-digger`. Node.js 20 or newer and Git on the system path are required. Create `.digger/config.json` in the workspace root with a `repos` entry containing a repository name and URL. `sourceRoot` defaults to `src`; `packages`, `packageFilter`, or omission of both fields control package selection.

Private repositories can use automatic authentication, PAT-only authentication, or no authentication. A PAT may be placed in configuration or referenced through an environment variable, and a workspace `.env` file is loaded automatically. If no configuration exists, `dig_init` can create a starter file.

After connecting the server, call `dig_status` to check configuration, repository connectivity, and index health.

## Tools and capabilities

- `dig_status`: reports configuration, connectivity, and index health.
- `dig_list`: lists configured repositories and package summaries.
- `dig_repo_overview`: returns filtered repository README content and package count.
- `dig_package_overview`: shows package documentation, key interfaces, abstract classes, and file count.
- `dig_package_files`: lists C# files with a directory summary.
- `dig_lookup`: searches symbols, implementations, base-class relationships, and references.
- `dig_signatures`: returns filtered public C# APIs without method bodies.
- `dig_file`: reads one complete source file, with a 1 MB limit.
- `dig_refresh`: rebuilds caches for selected or all repositories.
- `dig_init`: scaffolds configuration when none is found.

## Limitations and notes

The mcp-digger MCP server is limited to .NET and C# source organized around `.csproj` packages and `.cs` files. It does not index other programming languages. Full-file retrieval is capped at 1 MB, and local repositories remain under the user's branch and filesystem control. Package discovery and transitive project handling depend on the configured repository layout and available solution or package metadata.

_Full upstream README: https://allmcps.com/mcp/mcp-digger/readme_