Dotnet Sherlock Mcp
Let your agent inspect .NET assemblies with reflection and type analysis while you debug, document, or extend backend services.
Overview
dotnet-sherlock-mcp is a MCP server for the Build phase that provides .NET assembly introspection, reflection, and type analysis tools to your coding agent.
What is this MCP server?
- .NET assembly introspection over MCP stdio
- Advanced reflection and type analysis tooling
- NuGet package Sherlock.MCP.Server (v2.9.1)
- Supports agent-led exploration of unfamiliar binaries and libs
- Developer Tools focus—not a generic file search skill
- Server version 2.9.1
- NuGet identifier Sherlock.MCP.Server
- stdio MCP transport
Community signal: 4 GitHub stars.
What problem does it solve?
Large or opaque .NET assemblies slow you down when the agent cannot see real type layouts, APIs, and reflection detail beyond plain source files.
Who is it for?
Solo builders shipping .NET APIs or services who want agent-native assembly and type analysis during refactors or third-party lib onboarding.
Skip if: JavaScript-only stacks, builders who do not run .NET tooling, or teams wanting cloud deploy or infra MCP instead of binary introspection.
What do I get? / Deliverables
Your agent can query assembly-level structure so backend changes, integrations, and docs target the actual compiled surface.
- Agent-queryable .NET type and assembly analysis
- Faster mapping of public APIs and dependencies
- Reflection-backed answers for backend change planning
Recommended MCP Servers
Journey fit
Build/backend is the natural shelf for deep assembly introspection on running or compiled .NET codebases. Backend subphase covers service internals, type graphs, and integration surfaces agents must understand before changing APIs.
How it compares
.NET reflection MCP server, not a general code-search or unit-test skill.
Common Questions / FAQ
Who is dotnet-sherlock-mcp for?
Developers on C# and .NET backends who use MCP agents and need structured assembly and type analysis beyond text search.
When should I use dotnet-sherlock-mcp?
Use it while building or extending .NET services when you must map types, reflection, or assembly boundaries before editing code.
How do I add dotnet-sherlock-mcp to my agent?
Install Sherlock.MCP.Server from NuGet, configure stdio MCP in your client, and point analysis at the assemblies you need on your machine.