roslyn-codelens-mcp
Related Servers
Alternatives to roslyn-codelens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal-first MCP server for semantic C# analysis, navigation, validation, and refactoring using Roslyn on real .NET workspaces.2MIT
- AlicenseAqualityBmaintenanceA 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.6242MIT
- AlicenseNot gradedqualityBmaintenanceA local .NET MCP server for coding agents, providing persistent semantic indexing, typed-graph DI wiring resolution, reduced context, and compiler-backed verification for .NET projects.37Apache 2.0
- AlicenseAqualityBmaintenanceCode intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.154MIT
- AlicenseAqualityBmaintenanceBring Visual Studio-style C# fixes and refactorings to your AI coding agent. Roslyn Code Actions, semantic navigation and reviewable transactions—all running locally.564MIT
- AlicenseAqualityBmaintenanceLocal MCP server for Windows and macOS: Claude reads your C#, Python, TypeScript and JavaScript through a syntax index, checks NuGet, PyPI and npm APIs at your pinned versions, remembers how each feature flows through your code, and edits, builds, tests and runs git. Approvals happen only on your machine; secrets are hidden.358MIT
TDQS
Scored across 67 tools
Most tools are distinct in purpose, but there is some overlap among query tools (e.g., find_references vs find_callers vs analyze_change_impact) and overview tools (get_type_overview vs get_symbol_context). Descriptions clarify the differences, so confusion is unlikely but not impossible.
All tool names follow a consistent snake_case verb_noun pattern (find_references, get_diagnostics, rename_symbol, change_signature, etc.). The naming is predictable and uniform, making the API easy to navigate.
With 67 tools, the server is extremely heavy. Although it covers a broad domain (analysis, refactoring, testing, dependencies), many tools are highly specific and could be consolidated (e.g., multiple find_* analyzers). This exceeds any reasonable threshold for typical usage.
The tool set provides comprehensive coverage of the code analysis domain: symbol lookup, references, diagnostics, code fixes, refactoring, test generation, architecture checks, dependency graphs, and more. No obvious gaps exist for the stated purpose of deep Roslyn-based analysis.