Log inSubmit server
MCP Digger logo

MCP Digger

Browse, search, and inspect private C# libraries from NuGet-style repositories through progressive MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Digger

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-digger": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-digger"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The mcp-digger MCP server gives AI coding agents on-demand access to internal .NET and NuGet package source. It clones configured Git repositories or reads local repositories, indexes C# projects, and exposes progressive tools for discovery, symbol search, signatures, and full files. Use it when an agent needs private C# library context without adding those repositories to the active workspace. It requires Node.js 20+, Git, and repositories containing .csproj projects and .cs source files.

Use cases

  • Browse private C# package APIs before writing code
  • Find implementations of an interface across internal packages
  • Inspect public signatures without loading method bodies
  • Read source files from managed or local Git repositories
  • Refresh indexed repository caches on demand

Key features

  • Progressive C# source access
  • Cross-package symbol lookup
  • Public API signature extraction
  • Managed and local repository modes
  • PAT and SSH/HTTPS Git access
  • Configurable package discovery

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · mcp-digger (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads142Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.

How MCP Digger works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Digger

mcp-digger is an MCP server that connects AI coding agents to private .NET and NuGet-style Git repositories containing C# projects. Its main tools list repositories and packages, search symbols and references, inspect public signatures, read source files, check repository health, refresh indexes, and create initial configuration.

Install it with `npm install -g mcp-digger` or run it directly with `npx mcp-digger`. Node.js 20 or newer and Git on the system path are required. Add a `.digger/config.json` file, or call `dig_init` after starting the server to create starter configuration.

Configure repositories in `.digger/config.json` under `repos`. You can specify packages, a package-name filter, or let the server discover non-test projects below `sourceRoot`. Authentication supports automatic selection, PAT-only mode, or no authentication; PATs can be referenced through environment variables.

Yes, mcp-digger works with Cursor through a project-level `.cursor/mcp.json` or a global `~/.cursor/mcp.json` configuration. Use an MCP server entry that runs `npx` with `-y` and `mcp-digger` as its argument.

mcp-digger supports .NET and C# repositories containing `.csproj` packages and `.cs` source files. It is not intended to index TypeScript, Python, Java, Go, or other languages.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Digger AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-digger?style=directory)](https://allmcps.com/mcp/mcp-digger)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-digger"><img src="https://allmcps.com/api/badge/mcp-digger?style=directory" alt="MCP Digger on AllMCPs" /></a>