A
licenseA
qualityA
maintenanceRoslyn-based MCP server providing semantic code intelligence for .NET codebases — type hierarchies, call sites, DI registrations, and reflection usage for Claude Code
67
64
MIT
Roslyn Workbench MCP
by lantean-code
Related Servers
Alternatives to Roslyn Workbench MCP
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server for semantic C# analysis, navigation, validation, and refactoring using Roslyn on real .NET workspaces.1MIT
Related Servers
- FlicenseAqualityDmaintenanceMinimal MCP server bridging a Roslyn C# language server to AI agents, exposing tools for diagnostics, call hierarchy, and type hierarchy.1-
- AlicenseAqualityAmaintenanceMCP server that runs JetBrains' ReSharper command-line tools for code inspection and cleanup, exposed to C# coding agents over stdio.31MIT
- AlicenseAqualityCmaintenanceMCP server for .NET assembly analysis. Vendor-neutral wrapper around AsmResolver and ILSpy for parsing and decompiling .NET assemblies.111MIT
- AlicenseAqualityAmaintenanceA 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.6237MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that gives AI assistants Roslyn-powered browsing of any C# solution, letting them list types by folder or namespace, read XML documentation, and retrieve method signatures, locations and bodies. This keeps queries targeted so agents pull only the exact slice of source they need instead of reading whole files into context.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides Roslyn-based code intelligence for AI coding agents via MCP, enabling efficient navigation and surgical edits of C# solutions.6MIT
TDQS
B3.2/5.0
Scored across 48 tools
Disambiguation4/5
Most tools target clearly distinct Roslyn operations (analyze-* group, workspace-* group, symbol hierarchy tools). However, a few clusters could be confused: find-references vs find-callers vs get-symbol-dependents, and get-code-context vs get-document-outline vs get-operation-tree overlap in intent. Descriptions help but an agent may still hesitate between dependency and reference tools.
Naming Consistency5/5
Every tool follows a consistent kebab-case verb_noun pattern (get-*, find-*, analyze-*, workspace-*, prepare/submit-error-report). Prefixes map predictably to intent groups, making the set easy to scan.
Tool Count2/5
48 tools is heavy, well past the 25+ threshold and approaching the extreme 50+ tier. While a semantic analysis domain is broad, this many tools burdens selection and several (find-callers/find-callees, get-symbol-dependencies/dependents) could plausibly be consolidated.
Completeness4/5
Coverage is strong across diagnostics, symbol resolution, hierarchy, dependency/impact analysis, code actions, and workspace lifecycle. The notable gap is mutation: list-code-actions and prepare-fix-all exist but no apply/rename/refactor tool, suggesting a read-only surface despite the 'workbench' framing.
Maintenance
ActivityActive
ResponsivenessWithin a week