Mcp Digger
Let agents progressively fetch and explore .NET NuGet package source instead of guessing APIs from names alone.
Overview
mcp-digger is a MCP server for the Build phase that provides progressive on-demand .NET NuGet package source access for AI coding agents.
What is this MCP server?
- mcp-digger v1.1.3 on npm with npx runtime hint and stdio transport
- Progressive on-demand access to .NET NuGet package source for coding agents
- Reduces hallucinated APIs when working in C# / .NET repos
- Maintained at github.com/janeksm/mcp-digger with published README
- npm package mcp-digger version 1.1.3
- stdio transport with npx runtime hint
- Targets .NET NuGet package source per server description
What problem does it solve?
.NET agents often invent method signatures because they cannot see inside the NuGet packages your project actually references.
Who is it for?
Indie and solo developers shipping .NET backends or tools who rely on MCP agents for implementation help.
Skip if: Pure JavaScript or Python stacks with no NuGet dependencies, or teams that forbid agents from fetching external source.
What do I get? / Deliverables
After you register mcp-digger, your agent can pull NuGet source on demand and ground changes in real package implementations.
- MCP tools for on-demand NuGet source exploration
- More accurate agent suggestions against real package APIs
- Less rework from invented .NET dependency signatures
Recommended MCP Servers
Journey fit
NuGet source access is agent-tooling for .NET builds when the model needs ground-truth from packages you depend on. Progressive on-demand digging sits with coding-agent tooling rather than ship-time security review or launch SEO.
How it compares
NuGet source MCP for .NET agents, not a general GitHub code search skill or IDE-only Go to Definition.
Common Questions / FAQ
Who is Mcp Digger for?
Solo .NET builders using Claude Code, Cursor, Codex, or Windsurf who need accurate NuGet package internals during coding sessions.
When should I use Mcp Digger?
Use it in Build while integrating or debugging against NuGet dependencies where API surface must match published source.
How do I add Mcp Digger to my agent?
Add an MCP server entry that runs npx Mcp Digger (v1.1.3), stdio transport, then restart your host so tools expose progressive NuGet source access.