Roslyn CodeLens
Give your agent Roslyn-powered semantic navigation and code intelligence over .NET solutions instead of brittle text search.
Overview
Roslyn CodeLens is an MCP server for the Build phase that provides Roslyn-based semantic code intelligence for .NET codebases to coding agents.
What is this MCP server?
- Roslyn CodeLens MCP v2.0.0 as NuGet package RoslynCodeLens.Mcp
- Stdio transport for Claude Code, Cursor, and other MCP clients
- Semantic code intelligence across .NET codebases—not plain ripgrep
- Backed by github.com/MarcelRoozekrans/roslyn-codelens-mcp
- Title Roslyn CodeLens in registry metadata for discoverability
- Server version 2.0.0
- NuGet identifier RoslynCodeLens.Mcp
- Stdio transport only in published metadata
Community signal: 15 GitHub stars.
What problem does it solve?
Agents hallucinate C# structure because text search misses symbols, references, and project boundaries.
Who is it for?
Solo .NET developers who want MCP-driven navigation and analysis while building APIs or services in large solutions.
Skip if: Non-.NET repositories, no-code builders, or teams that only need documentation generation without compiler semantics.
What do I get? / Deliverables
After registering RoslynCodeLens.Mcp, your agent can query semantic .NET code facts to plan safer backend changes.
- Semantic queries and navigation over .NET symbols and projects via MCP
- Agent context grounded in Roslyn rather than raw file text
- Faster, lower-risk backend edits in multi-project repos
Recommended MCP Servers
Journey fit
Semantic understanding of C# and VB projects is core backend construction work while you implement features and refactors. Backend is where Roslyn symbols, references, and project graphs matter most for safe edits and API changes.
How it compares
Roslyn semantic intelligence MCP for .NET, not a cloud IDE or generic filesystem search server.
Common Questions / FAQ
Who is Roslyn CodeLens for?
Builders using Claude Code, Cursor, Codex, or generic MCP clients on C#, F#, or VB .NET solutions who need compiler-accurate context.
When should I use Roslyn CodeLens?
Use it during Build backend work when you refactor, trace usages, or let an agent propose changes that must match real symbols and projects.
How do I add Roslyn CodeLens to my agent?
Add RoslynCodeLens.Mcp from NuGet as a stdio MCP server in your client config, ensure .NET can run the package, open the solution root, and restart the agent.