Server data from the Official MCP Registry
Progressive on-demand access to .NET NuGet package source for AI coding agents.
Progressive on-demand access to .NET NuGet package source for AI coding agents.
mcp-digger is a well-structured MCP server for indexing .NET/C# source code repositories. Authentication is optional but properly scoped via environment variables and PAT strategies. Code quality is high with comprehensive test coverage. Permissions are appropriate for its purpose (file I/O, git operations, network access). No malicious patterns, hardcoded secrets, or dangerous code execution vulnerabilities detected. Minor code quality observations noted but do not materially impact security posture. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
4 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-janeksm-mcp-digger": {
"args": [
"-y",
"mcp-digger"
],
"command": "npx"
}
}
}From the project's GitHub README.
Your internal .NET libraries have source — mcp-digger turns it into the context AI agents need to use your C# APIs correctly, saving time, tokens, and manual intervention.
⚠ Scope: .NET / C# only. mcp-digger indexes NuGet-style repos containing
.csprojpackages and.cssource files. It is not a general-purpose source indexer — other languages (TypeScript, Python, Java, Go, etc.) are out of scope.
Public NuGet packages have documentation ecosystems — API references, tutorials, community Q&A. Tools like context7 serve that well.
Internal .NET packages often have source code as their primary documentation. mcp-digger turns that source into structured, searchable, token-efficient context that any MCP-compatible agent can consume — bridging the documentation gap in private C# library ecosystems.
Without it:
git clone + find + grep + cat chains burn tokens on infrastructure before useful context is retrieved.With it:
Ten purpose-built tools, escalating from broad to deep. The agent picks the cheapest tool that answers its question.
┌─→ 📦 dig_package_overview ─┐
│ (docs, key types) │
🩺 dig_status → 📋 dig_list → 📖 dig_repo_overview ┤ ├─→ 🔎 dig_lookup → 📄 dig_file
(health) (discover) (README + summaries) │ │ (symbol → file) (full source)
├─→ 📁 dig_package_files ────┤
│ (file listing) │
└────────────────────────────┴─→ 📝 dig_signatures
(stripped API)
Operational: 🔄 dig_refresh (force cache invalidation, on demand)
Bootstrap: 🌱 dig_init (only when no config exists)
| Tier | Tool | What it does |
|---|---|---|
| Health | 🩺 dig_status | Config summary, connectivity check per repo, index health stats |
| Discovery | 📋 dig_list | Lists configured repos + their packages with one-line .csproj summaries |
| L1 Overview | 📖 dig_repo_overview | Repo README.md (filtered to architecture sections) + package count |
| L1 Overview | 📦 dig_package_overview | Package docs, key interfaces, abstract classes, file count |
| L1 Overview | 📁 dig_package_files | .cs file listing for a package, with directory summary header |
| L2 Search | 🔎 dig_lookup | Indexed symbol search — symbol, implements, or references mode. Cross-package supported. |
| L2 Search | 📝 dig_signatures | Stripped C# public API surface filtered by keyword (no method bodies) |
| L3 Source | 📄 dig_file | Full source of a single file (capped at 1 MB) |
| Operational | 🔄 dig_refresh | Force-rebuild caches for one or all repos |
| Bootstrap | 🌱 dig_init | Creates starter .digger/config.json (registered only when no config is found) |
Search modes for dig_lookup:
| Mode | Finds |
|---|---|
symbol (default) | Type/method declarations matching a name substring |
implements | Classes/structs implementing an interface or extending a base class |
references | Files referencing a given type name (word-boundary, case-sensitive) |
npm install -g mcp-digger
# or run directly
npx mcp-digger
Requires Node.js 20+, git on PATH, and a .NET / C# source repo (NuGet packages with .csproj + .cs sources).
Create .digger/config.json in your workspace root:
{
"repos": [
{
"name": "my-libraries",
"url": "https://github.com/org/shared-libs.git",
"packageFilter": "MyCompany.*",
"auth": {
"strategy": "pat",
"PAT-EnvVarName": "GIT_PAT"
}
}
]
}
Don't have a config yet? Start the server, then call dig_init to scaffold one.
Add to .claude/settings.json or project settings:
{
"mcpServers": {
"digger": {
"command": "npx",
"args": ["-y", "mcp-digger"]
}
}
}
Add to ~/.codex/config.toml (or .codex/config.toml for project-scoped):
[mcp_servers.mcp-digger]
command = "npx"
args = ["-y", "mcp-digger"]
Once connected, ask your agent to call dig_status — it reports config validation, per-repo connectivity, and index health.
A repos[] entry has three ways to declare packages:
| Option | Behavior |
|---|---|
"packages": ["A", "B"] | Explicit list — only these packages are exposed |
"packageFilter": "MyCompany.*" | Wildcard — narrows to packages matching the prefix, found via .sln/.slnx/Directory.Packages.props workspace scan. Follows transitive ProjectReference links automatically. |
| (omit both) | Auto-discover all non-test .csproj directories under sourceRoot |
sourceRoot defaults to "src" — set it to whichever directory holds your package folders.
By default, managed clones use the repo's default branch. Pin to a specific one:
{
"repos": [
{
"name": "my-libraries",
"url": "https://github.com/org/shared-libs.git",
"branch": "develop"
}
]
}
The branch is used for both initial clone and subsequent fetches. Only applies to managed clones — for local repos, you control the checked-out branch yourself.
Skip managed cloning when the repo is already on disk. The local path is read-only — mcp-digger never fetches or modifies it.
{
"localRepos": {
"my-libraries": "C:/repos/shared-libs"
},
"repos": [
{
"name": "my-libraries",
"sourceRoot": "src"
}
]
}
| Strategy | Behavior |
|---|---|
auto (default) | Try unauthenticated, fall back to PAT if set |
pat | Always use PAT (fatal if not set) |
none | Never authenticate |
PATs can be inline ("PAT": "...") or via environment variable indirection ("PAT-EnvVarName": "MY_TOKEN"). The .env file in your workspace root is loaded automatically — values containing # should be quoted.
| Variable | Default | Purpose |
|---|---|---|
DIGGER_CONFIG | .digger/config.json | Override config file path |
MANAGED_SOURCE_DIR | .digger/source | Override managed clone directory |
CACHE_DIR | .digger/cache | Override cache directory |
Secrets (PAT values) belong in .env or the real environment — never as env vars in this table.
| Symptom | First call | Then |
|---|---|---|
| Connection / auth issues | dig_status | Reports auth attempts, exact error, actionable hints |
| "No matches" but you expect some | dig_refresh <repo> | Force-rebuilds index, picks up new extraction logic |
| Server starts but no tools visible | dig_status | If unconfigured, only dig_status + dig_init are registered |
| Need a config from scratch | dig_init | Scaffolds .digger/config.json (atomic — won't overwrite existing) |
Enable debug logging in your config:
{ "debug": true, "repos": [...] }
Logs go to .digger/debug.log (capped at 5 MB, auto-truncated). Critical errors and crash output land in .digger/error.log.
MIT License — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.