Skip to main content
Glama
mcp-dotnet-diagnostics

mcp-dotnet-diagnostics

by aayushmdesai

CI mcp-dotnet-diagnostics MCP server

mcp-dotnet-diagnostics

Give your AI assistant real-time visibility into your .NET application's runtime health.

Connect this Model Context Protocol server to Claude Desktop and ask plain questions about any running .NET process — memory leaks, GC pressure, thread starvation, allocation hotspots. Claude calls the right tools, reads real runtime data, and tells you what's actually wrong.


What this looks like in practice

Health check demo

You ask:

"Why does my API have high memory usage? PID is 12345."

Claude calls get_process_info to confirm connectivity, then get_memory_stats, then get_gc_events — and responds:

"Every GC event in the last 5 seconds was a Gen2 collection triggered by AllocLarge. Something is continuously allocating objects above the 85KB LOH threshold at ~10.5 MB/s. LOH is never compacted by default — fragmentation is at 55% and growing. The fix is ArrayPool<byte>.Shared. Rent a buffer, use it, return it."

You don't tell Claude which tools to call. It figures that out from your question.


Related MCP server: ASPNET Core Debugging MCP Server

Tools

Tool

What it returns

Reach for it when...

get_process_info

Name, PID, uptime, .NET version, OS

Starting any investigation — confirms the process is reachable

get_memory_stats

GC heap, LOH size, alloc rate, Gen0/1/2 counts, fragmentation

Memory is high or growing

get_gc_events

Per-collection timeline — generation, reason, timestamp

GC pauses are affecting latency

get_thread_stats

ThreadPool count, queue depth, completed items, lock contention

Requests are slow or backing up

get_event_counters

All 27 System.Runtime metrics in one snapshot

You want a broad health overview

get_environment_info

Runtime config, filtered env vars (no secrets)

Debugging configuration issues

list_counters

Raw EventCounter names and current values

Discovering what's available on an unfamiliar process


Installation

1. Install the tool

dotnet tool install -g mcp-dotnet-diagnostics

Requires .NET 8 SDK or later. Get it here if needed.

2. Add to Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json while Claude Desktop is fully quit (Cmd+Q — not just the window closed), then add:

{
  "mcpServers": {
    "dotnet-diagnostics": {
      "command": "mcp-dotnet-diagnostics",
      "env": {
        "TMPDIR": "/var/folders/xx/your-tmpdir/T/"
      }
    }
  }
}

3. Reopen Claude Desktop

The dotnet-diagnostics connector appears in the tools menu. Ask it about any .NET process.


macOS: the TMPDIR step is not optional.

The .NET diagnostics protocol finds processes through a Unix socket. On macOS, that socket lives under $TMPDIR — not /tmp/ where the library looks by default. Without this, every tool call returns "process not found."

Find yours with: echo $TMPDIR


Want to contribute or build from source? See CONTRIBUTING.md for how to clone, build, and add new tools.

Usage

Find the PID of your target process:

dotnet-counters ps

Then ask Claude naturally: "Do a full health check on PID 12345." "Why is memory climbing on PID 12345?" "Any thread starvation in PID 12345?" "What's the GC situation on PID 12345?"


How it works

The server uses Microsoft.Diagnostics.NETCore.Client to attach to any running .NET process by PID — the same library that powers dotnet-counters, dotnet-trace, and dotnet-dump. It streams telemetry directly from the CLR over EventPipe, which means you get the same data as the official .NET CLI tools, available to Claude as structured tool responses.

The tool descriptions are written to guide Claude's investigation sequence. When you report high memory, Claude calls get_process_info first (connectivity), then get_memory_stats (heap overview), then get_gc_events (collection details) — because the descriptions say to. The chaining is implicit, not hardcoded.


Requirements

  • .NET 8 SDK or later to build; .NET 10 recommended

  • Claude Desktop or any MCP-compatible client

  • A running .NET process to inspect (your app, an API, anything)


Tests

dotnet test src/McpDotnetDiagnostics.Tests

34 tests across all 7 tools — unit tests against invalid PIDs, integration tests against the live test runner process (Environment.ProcessId). Runs in ~17 seconds.


Design decisions

Three decisions shaped this project in ways that aren't obvious from the outside:


License

MIT

Available Tools

7 tools
get_environment_infoA

Returns runtime environment information for a target .NET process including .NET runtime version, OS details, processor count, memory, and process configuration. Use this when investigating version mismatches, environment-specific bugs, or unexpected runtime behavior. Call get_process_info first to confirm the process is reachable.

Inputs: pid (required).

get_event_countersA

Returns all available EventCounter metrics from a .NET process including CPU usage, memory, GC, threading, exceptions, and JIT stats in a single call. Use this for a broad health overview when you don't know which specific area to investigate. For deeper analysis, follow up with get_memory_stats or get_thread_stats.

Inputs: pid (required), sampleSeconds.

get_gc_eventsA

Returns recent GC events for a target .NET process including collection generation (Gen0/Gen1/Gen2), duration, pause time, and timestamp. Use this when investigating periodic response time spikes, application pauses, memory that grows without releasing, or when get_memory_stats shows high Gen2 collection counts. Call get_memory_stats first to establish whether GC pressure is the root cause before drilling into individual events.

Inputs: pid (required), sampleSeconds.

get_memory_statsA

Returns current .NET memory usage for a target process including total allocated bytes, GC generation collection counts (Gen0/Gen1/Gen2), Large Object Heap size, and memory pressure level. Use this when investigating memory leaks, unexpectedly high memory usage, frequent GC pauses, or slow application performance caused by garbage collection pressure. Call get_process_info first to confirm the process is reachable.

Inputs: pid (required), sampleSeconds.

get_process_infoA

Returns basic information about a running .NET process by PID. Includes process name, uptime, .NET runtime version, OS platform, and CPU core count. Use this as the first step when investigating any .NET application — it confirms the process is reachable and provides baseline context before diving into memory or thread diagnostics.

Inputs: pid (required).

get_thread_statsA

Returns .NET ThreadPool statistics for a target process including worker thread count, available threads, queue length, and completed work items. Use this when investigating slow response times, request timeouts, or deadlocks — high queue length and low available threads indicates thread starvation, which is a common cause of latency spikes in .NET APIs. Call get_memory_stats first — GC pressure is a frequent cause of thread starvation.

Inputs: pid (required), sampleSeconds.

list_countersA

Lists all available EventCounter names and current values from a .NET process. Use this to discover what metrics are available before calling get_memory_stats.

Inputs: pid (required), sampleSeconds.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct with clear purposes, but there is some overlap between list_counters, get_event_counters, and the specific tools like get_memory_stats. The descriptions provide guidance on when to use each, reducing ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_process_info, list_counters). No mixing of conventions.

    Tool Count5/5

    7 tools is well-scoped for a diagnostics server. Each tool covers a distinct aspect (process info, environment, memory, threads, GC, counters), without being excessive or insufficient.

    Completeness4/5

    The tool set covers key diagnostic areas (environment, memory, threads, GC, event counters). Minor gaps exist: no dedicated CPU or exception analysis tool, but they are included in the broad health overview.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers