Dotnet Sherlock MCP Server

Most knowledge and memory work still happens through a UI a human drives. Dotnet Sherlock MCP MCP server moves it into the conversation instead. This tool is essential for developers who want to harness LLM capabilities for:.

The short version

• Comprehensive MCP Server — Provides 36 specialized tools for .NET assembly analysis
• Advanced Assembly Introspection — Deep reflection-based analysis of types, members, and metadata
• Rich Member Analysis — Detailed inspection of methods, properties, fields, events, and constructors
• Smart Filtering & Pagination — Advanced filtering by name/attributes with efficient pagination for large datasets
• XML Documentation Integration — Automatic extraction of summary, parameters, returns, and remarks
• Performance Optimized — Caching, streaming, and memory-efficient processing

The tools it exposes

The server publishes 1 tool. What each one is for:

• Guidelines — The Guidelines tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dotnet Sherlock MCP's toolset — Guidelines — is a fair guide to whether it matches your workflow. It is maintained by jcucci; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.