Skip to main content
Glama
magna-nz

ASPNET Core Debugging MCP Server

by magna-nz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to ASPNET Core Debugging MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-netcoredbg

      AerialByte
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI agents to debug .NET applications using netcoredbg. It supports core debugging tasks like setting breakpoints, stepping through code, and inspecting variables or stack traces.
      1
      MIT

    • dotnet-mcp

      jongalloway
      A
      license
      Not graded
      quality
      B
      maintenance
      Give your AI assistant superpowers for .NET development! This MCP server connects GitHub Copilot, Claude, and other AI assistants directly to the .NET SDK, enabling them to create projects, manage packages, run builds, and more—all through natural language.
      35
      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
      -
    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.7/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool has a distinct purpose: breakpoint management, execution control, stack inspection, tracing, and diagnostics are cleanly separated. The breakpoint_* and trace_* families are clearly differentiated by their suffixes (set, remove, list, wait, start, stop, get).

    Naming Consistency4/5

    The tool names are largely predictable, with strong prefixes like debug_, breakpoint_, trace_, and stack*. Minor inconsistencies exist, such as 'threads_list' vs 'debug_state' and 'stack_explore' vs 'stacktrace_get', but the overall pattern remains comprehensible.

    Tool Count3/5

    27 tools is on the upper end of what's reasonable for a debugger domain, covering session control, breakpoints, stepping, inspection, tracing, and diagnostics. Some redundancy exists (e.g., stack_explore bundles stacktrace_get + variables_get; debug_step can also wait like breakpoint_wait), which adds weight without adding much capability.

    Completeness4/5

    The domain coverage is strong: launch/attach, pause/continue/step, multiple breakpoint types, stack/variable inspection, expression evaluation, output reading, and diagnostic helpers. The main gap is a detach-without-terminate operation)Skip? Otherwise, no obvious missing capabilities for a debugger MCP server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources