CWM.RoslynNavigator 0.5.2

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet tool install --global CWM.RoslynNavigator --version 0.5.2
This package contains a .NET tool you can call from the shell/command line. 
dotnet new tool-manifest
                    


                            if you are setting up this repo
                        

                    

                
dotnet tool install --local CWM.RoslynNavigator --version 0.5.2
This package contains a .NET tool you can call from the shell/command line. 
#tool dotnet:?package=CWM.RoslynNavigator&version=0.5.2
                    


                    

                
nuke :add-package CWM.RoslynNavigator --version 0.5.2

CWM.RoslynNavigator — Roslyn MCP Server

Token-efficient .NET codebase navigation via Roslyn semantic analysis.

Overview

CWM.RoslynNavigator is a Model Context Protocol (MCP) server that provides Claude Code with semantic understanding of .NET solutions. Instead of reading entire source files (hundreds of tokens), Claude can query for specific symbols, references, and type hierarchies (tens of tokens).

Prerequisites

  • .NET 10 SDK
  • A .NET solution file (.sln or .slnx)

Tools

Tool Description
find_symbol Find where a type, method, or property is defined
find_references All usages of a symbol across the solution
find_implementations Types that implement an interface or derive from a base class
find_callers All methods that call a specific method
find_overrides Overrides of a virtual or abstract method
find_dead_code Unused types, methods, and properties
get_type_hierarchy Inheritance chain, interfaces, and derived types
get_public_api Public members of a type without reading the full file
get_symbol_detail Full signature, parameters, return type, and XML docs
get_project_graph Solution project dependency tree
get_dependency_graph Call dependency graph for a method
get_diagnostics Compiler and analyzer warnings/errors
get_test_coverage_map Heuristic test coverage by naming convention
detect_antipatterns .NET anti-patterns (async void, sync-over-async, etc.)
detect_circular_dependencies Circular dependency detection at project or type level

Installation

dotnet tool install -g CWM.RoslynNavigator

Then add to your Claude Code global settings (~/.claude/settings.json):

{
  "mcpServers": {
    "cwm-roslyn-navigator": {
      "command": "cwm-roslyn-navigator",
      "args": ["--solution", "${workspaceFolder}"]
    }
  }
}

The --solution argument accepts either a direct path to a .sln/.slnx file or a directory to scan for solution files.

As a Local Tool (per-repo)

dotnet new tool-manifest   # if you don't have one
dotnet tool install CWM.RoslynNavigator

Then add to your project's .mcp.json:

{
  "mcpServers": {
    "cwm-roslyn-navigator": {
      "command": "dotnet",
      "args": ["tool", "run", "cwm-roslyn-navigator", "--", "--solution", "${workspaceFolder}"]
    }
  }
}

From Source (for contributors)

dotnet run --project mcp/CWM.RoslynNavigator/CWM.RoslynNavigator.csproj -- --solution /path/to/your/Solution.sln

Solution Discovery

The server resolves the solution file in this order:

  1. Explicit --solution argument — Pass a .sln/.slnx file path directly, or a directory to scan recursively
  2. Working directory scan — If no argument, scans the current working directory recursively for solution files
  3. Deterministic selection — Shallowest solution wins (BFS); within the same depth, alphabetical (case-insensitive) ordering is used

Discovery searches up to 3 levels deep using breadth-first search, so a solution at src/MyApp.sln or src/backend/Api/Api.sln is found automatically.

The following directories are skipped during scanning: .git, .vs, .idea, node_modules, bin, obj, packages, artifacts, TestResults, .claude.

Architecture

Program.cs              → MSBuildLocator → Host → MCP stdio transport
WorkspaceManager.cs     → MSBuildWorkspace lifecycle, file watching, compilation caching
WorkspaceInitializer.cs → BackgroundService triggers workspace load on startup
SolutionDiscovery.cs    → Auto-detect .sln/.slnx from args or working directory
SymbolResolver.cs       → Cross-project symbol resolution with disambiguation
Tools/                  → MCP tool implementations (15 read-only tools)
Responses/              → Token-optimized JSON response DTOs

Scaling

Solution Size Strategy
Small (1-15 projects) Load entire workspace on startup, keep compilations warm
Large (15-50 projects) Lazy-load compilations on first query per project
Enterprise (50+) Lazy loading + warn if query touches unloaded project

Development

# Build
dotnet build mcp/CWM.RoslynNavigator/CWM.RoslynNavigator.csproj

# Run tests
dotnet test mcp/CWM.RoslynNavigator/tests/CWM.RoslynNavigator.Tests.csproj

# Run manually against a directory
dotnet run --project mcp/CWM.RoslynNavigator/CWM.RoslynNavigator.csproj -- --solution /path/to/your/project/

# Run manually against a solution file
dotnet run --project mcp/CWM.RoslynNavigator/CWM.RoslynNavigator.csproj -- --solution /path/to/your/Solution.sln
Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
0.7.0 807 3/21/2026
0.6.0 663 2/23/2026
0.5.2 98 2/23/2026
0.5.1 91 2/23/2026
0.5.0 102 2/23/2026