SharpLensMcp

A Model Context Protocol (MCP) server providing 62 AI-optimized tools for .NET/C# semantic code analysis, navigation, refactoring, and code generation using Microsoft Roslyn.

Built for AI coding agents - provides compiler-accurate code understanding that AI cannot infer from reading source files alone.

Installation

Via NuGet (Recommended)

dotnet tool install -g SharpLensMcp

Then run with:

sharplens

Via npm

npx -y sharplens-mcp

Build from Source

dotnet build -c Release
dotnet publish -c Release -o ./publish

Claude Code Setup

1. Install the tool (pick one):

dotnet tool install -g SharpLensMcp
# or
npx -y sharplens-mcp

2. Create .mcp.json in your project root:

{
  "mcpServers": {
    "sharplens": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "sharplens-mcp"],
      "env": {
        "DOTNET_SOLUTION_PATH": "/path/to/your/Solution.sln (or .slnx)"
      }
    }
  }
}

3. Restart Claude Code to load the MCP server

4. Verify by asking Claude to run a health check on the Roslyn server

Why Use This with Claude Code?

Claude Code has native LSP support for basic navigation (go-to-definition, find references). SharpLensMcp adds deep semantic analysis:

Capability	Native LSP	SharpLensMcp
Go to definition	✅	✅
Find references	✅	✅
Find async methods missing CancellationToken	❌	✅
Impact analysis (what breaks?)	❌	✅
Dead code detection	❌	✅
Complexity metrics	❌	✅
Safe refactoring with preview	❌	✅
Batch operations	❌	✅

Configuration

Environment Variable	Description	Default
DOTNET_SOLUTION_PATH	Path to .sln or .slnx file to auto-load on startup	None (must call load_solution)
SHARPLENS_ABSOLUTE_PATHS	Use absolute paths instead of relative	false (relative paths save tokens)
ROSLYN_LOG_LEVEL	Logging verbosity: Trace, Debug, Information, Warning, Error	Information
ROSLYN_TIMEOUT_SECONDS	Timeout for long-running operations	30
ROSLYN_MAX_DIAGNOSTICS	Maximum diagnostics to return	100
ROSLYN_ENABLE_SEMANTIC_CACHE	Enable semantic model caching	true (set to false to disable)

If DOTNET_SOLUTION_PATH is not set, you must call the load_solution tool before using other tools.

AI Agent Configuration Tips

AI models may have trained bias toward using their native tools (Grep, Read, LSP) instead of MCP server tools, even when SharpLensMcp provides better capabilities.

To ensure optimal tool usage:

1. Claude Code: Add to your project's CLAUDE.md:

   For C# code analysis, prefer SharpLensMcp tools over native tools:
   - Use `roslyn:search_symbols` instead of Grep for finding symbols
   - Use `roslyn:get_method_source` instead of Read for viewing methods
   - Use `roslyn:find_references` for semantic (not text) references
   

2. Other MCP clients: Configure tool priority in your agent's system prompt

The semantic analysis from Roslyn is more accurate than text-based search, especially for overloaded methods, partial classes, and inheritance hierarchies.

Agent Responsibility: Document Synchronization

Important: SharpLensMcp maintains an in-memory representation of your solution for fast queries. When files are modified externally (via Edit/Write tools), the agent is responsible for synchronizing changes.

When to call sync_documents:

Action	Call sync_documents?
Used Edit tool to modify .cs files	✅ Yes
Used Write tool to create new .cs files	✅ Yes
Deleted .cs files	✅ Yes
Used SharpLensMcp refactoring tools (rename, extract, etc.)	❌ No (auto-updated)
Modified .csproj files	❌ No (use load_solution instead)

Usage:

# After editing specific files
sync_documents(filePaths: ["src/MyClass.cs", "src/MyService.cs"])

# After bulk changes - sync all documents
sync_documents()

Why this design?

This mirrors how LSP (Language Server Protocol) works - the client (editor) notifies the server of changes. This approach:

• Eliminates race conditions (agent controls timing)
• Avoids file watcher complexity and platform quirks
• Is faster than full solution reload
• Gives agents explicit control over workspace state

If you don't sync: Queries may return stale data (old method signatures, missing new files, etc.)

Features

• 62 Semantic Analysis Tools - Navigation, refactoring, code generation, diagnostics, discovery
• AI-Optimized Descriptions - Clear USAGE/OUTPUT/WORKFLOW patterns
• Structured Responses - Consistent success/error/data format with suggestedNextTools
• Zero-Based Coordinates - Clear warnings to prevent off-by-one errors
• Preview Mode - Safe refactoring with preview before apply
• Batch Operations - Multiple lookups in one call to reduce context usage

Tool Categories

Navigation & Discovery (17 tools)

Tool	Description
get_symbol_info	Semantic info at position
go_to_definition	Jump to symbol definition
find_references	All references across solution
find_implementations	Interface/abstract implementations
find_callers	Impact analysis - who calls this?
get_type_hierarchy	Inheritance chain
search_symbols	Glob pattern search (*Handler, Get*)
semantic_query	Multi-filter search (async, public, etc.)
get_type_members	All members by type name
get_type_members_batch	Multiple types in one call
get_method_signature	Detailed signature by name
get_derived_types	Find all subclasses
get_base_types	Full inheritance chain
get_attributes	List attributes on a symbol
get_containing_member	Enclosing symbol at position
get_method_overloads	All overloads of a method
find_attribute_usages	Find types/members by attribute

Analysis (11 tools)

Tool	Description
get_diagnostics	Compiler errors/warnings
analyze_data_flow	Variable assignments and usage
analyze_control_flow	Branching/reachability
analyze_change_impact	What breaks if changed?
check_type_compatibility	Can A assign to B?
get_outgoing_calls	What does this method call?
find_unused_code	Dead code detection
validate_code	Compile check without writing
get_complexity_metrics	Cyclomatic, nesting, LOC, cognitive
find_circular_dependencies	Project and namespace cycle detection
get_missing_members	Unimplemented interface/abstract members

Refactoring (14 tools)

Tool	Description
rename_symbol	Safe rename across solution
change_signature	Add/remove/reorder parameters
extract_method	Extract with data flow analysis
extract_interface	Generate interface from class
generate_constructor	From fields/properties
organize_usings	Sort and remove unused
organize_usings_batch	Batch organize multiple files
format_document_batch	Batch format files in project
get_code_actions_at_position	All Roslyn refactorings at position
apply_code_action_by_title	Apply any refactoring by title
implement_missing_members	Generate interface stubs
encapsulate_field	Field to property
inline_variable	Inline temp variable
extract_variable	Extract expression to variable

Code Generation (2 tools)

Tool	Description
add_null_checks	Generate ArgumentNullException guards
generate_equality_members	Equals/GetHashCode/operators

Compound Tools (6 tools)

Tool	Description
get_type_overview	Full type info in one call
analyze_method	Signature + callers + outgoing calls + location
get_file_overview	File summary with diagnostics
get_method_source	Source code by name
get_method_source_batch	Multiple method sources in one call
get_instantiation_options	How to create a type

Discovery (2 tools)

Tool	Description
get_di_registrations	Scan DI service registrations
find_reflection_usage	Detect reflection/dynamic usage

Infrastructure (10 tools)

Tool	Description
health_check	Server status
load_solution	Load .sln/.slnx for analysis
sync_documents	Sync file changes into loaded solution
get_project_structure	Solution structure
dependency_graph	Project dependencies
get_code_fixes	Available fixes for a diagnostic
apply_code_fix	Apply a specific code fix
get_nuget_dependencies	NuGet package listing per project
get_source_generators	List active source generators
get_generated_code	View generated source code

Other MCP Clients

For MCP clients other than Claude Code, add to your configuration:

{
  "mcpServers": {
    "sharplens": {
      "command": "sharplens",
      "args": [],
      "env": {
        "DOTNET_SOLUTION_PATH": "/path/to/your/Solution.sln (or .slnx)"
      }
    }
  }
}

Usage

1. Load a solution: Call roslyn:load_solution with path to .sln or .slnx file (or set DOTNET_SOLUTION_PATH)
2. Analyze code: Use any of the 57 tools for navigation, analysis, refactoring
3. Refactor safely: Preview changes before applying with preview: true

Architecture

MCP Client (AI Agent)
        | stdin/stdout (JSON-RPC 2.0)
        v
   SharpLensMcp
   - Protocol handling
   - 57 AI-optimized tools
        |
        v
Microsoft.CodeAnalysis (Roslyn)
  - MSBuildWorkspace
  - SemanticModel
  - SymbolFinder

Requirements

• .NET 8.0 SDK or later — works with .NET 8, 9, 10, and future versions. Analyzes any .NET 8+ project/solution.
• MCP-compatible AI agent

Development

Adding New Tools

1. Add method to src/RoslynService.cs:

public async Task<object> YourToolAsync(string param1, int? param2 = null)
{
    EnsureSolutionLoaded();
    // Your logic...
    return CreateSuccessResponse(
        data: new { /* results */ },
        suggestedNextTools: new[] { "next_tool_hint" }
    );
}

2. Add tool definition to src/McpServer.cs in HandleListToolsAsync

3. Add routing to src/McpServer.cs in HandleToolCallAsync switch

4. Build and publish:

dotnet build -c Release
dotnet publish -c Release -o ./publish

Key Files

File	Purpose
src/RoslynService.cs	Tool implementations (57 methods)
src/McpServer.cs	MCP protocol, tool definitions, routing

License

MIT - See LICENSE for details.