Skip to main content
Glama
MarcelRoozekrans

roslyn-codelens-mcp

by MarcelRoozekrans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to roslyn-codelens-mcp

No user-submitted related servers found.

    Related Servers

    • sharplens-mcp

      pzalutski-pixel
      A
      license
      A
      quality
      A
      maintenance
      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.
      62
      32
      MIT

    • Fuse

      Litenova-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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.
      34
      Apache 2.0

    • solograph

      fortunto2
      A
      license
      A
      quality
      B
      maintenance
      Code intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.
      15
      3
      MIT

    • LSP-MCP

      morrow-addref
      F
      license
      A
      quality
      D
      maintenance
      Minimal MCP server bridging a Roslyn C# language server to AI agents, exposing tools for diagnostics, call hierarchy, and type hierarchy.
      1
      -

    • mcp-deepcontext

      jmerelnyc
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling symbol-aware semantic search in Claude Code, allowing precise location of functions, types, and implementations via a symbol graph and embeddings.
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 67 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources