SearchSymbolsLABSCO SUMMARY
Grep knows the string; this knows the symbol.
Finding every caller of a method by text search means guessing spellings and missing the calls that go through an interface. Roslyn resolves the symbol first, so references, dependencies and complexity are answered from the compiler's view of the solution.
What it is
A C# MCP server built on Microsoft's Roslyn compiler platform, giving a client real symbol analysis over a solution rather than text search. Multi-level caching and incremental analysis keep it workable on large codebases.
What you get
- Symbols searched by wildcard pattern — *Service, Get*User — across classes, methods and properties
- Every usage of a symbol located across the whole solution
- Detailed information about a type, method or property
- Project dependencies and namespace usage analysed
- High-complexity methods identified by cyclomatic complexity
- Input validation and path sanitisation on the paths it is given
Requirements
.NET 8.0 SDK or later, and the absolute path to the solution you want analysed. The client config runs it with dotnet run pointed at the RoslynMcpServer project, and sets an environment name and a log level alongside it; setup.ps1 does the Windows wiring for you.
Setup effort
Build from source — git clone https://github.com/carquiza/RoslynMCP.git
USE CASES
01
Finding a class when you only remember the suffix
Search by pattern — everything ending in Service, everything shaped like Get*User — instead of scrolling the solution explorer.
02
Checking what breaks if you change a method
List every usage across the solution and read the symbol's detail before touching the signature.
03
Understanding an unfamiliar solution's shape
Analyse project dependencies and namespace usage to see which parts lean on which.
04
Deciding where refactoring effort would pay
Rank methods by cyclomatic complexity so the argument is about a measure rather than a hunch.
5 tools
Listed in project docs. Your client may show a different list.
FindReferencesGetSymbolInfoAnalyzeDependenciesAnalyzeCodeComplexityBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
.NET 8.0 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/carquiza/RoslynMCP.git
cd RoslynMCP/RoslynMcpServer
dotnet restore
dotnet buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"roslyn-code-navigator": {
"command": "dotnet",
"args": [
"run",
"--project",
"<YOUR_PATH_TO_ROSLYN_MCP_ROSLYN_MCP>"
],
"env": {
"DOTNET_ENVIRONMENT": "Production",
"LOG_LEVEL": "Information"
}
}
}
}
