Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
nuget AspNetCoreDebuggerMcpClaude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add magna-nz-aspnetcore-debugger-mcp -- nuget AspNetCoreDebuggerMcpÀ exécuter dans un terminal.
{ "mcpServers": { "magna-nz-aspnetcore-debugger-mcp": { "command": "nuget", "args": [ "AspNetCoreDebuggerMcp" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerAn MIT-licensed MCP server that lets an AI agent (Claude, etc.) debug your .NET / ASP.NET Core app — netcoredbg bundled for every platform, nothing extra to install.
Instead of "I think the bug is around line 42, try this", the agent runs your code, pauses it, reads the actual runtime values, mutates state to test a fix, and answers grounded in what it actually saw.
You
GET /users/activereturns[], but I know there are active users in the DB. What's the query actually doing?
Claude
I'll pause inside
UserRepository.GetActiveAsyncand read what EF Core actually sent.SELECT u.* FROM Users AS u WHERE u.IsActive = 1 AND u.TenantId = @__tenantId_0 @__tenantId_0 = 0The SQL is correct; the parameter is wrong.
TenantId = 0, but your tenants start at 1.ICurrentUser.TenantIdis being read in the repository constructor — before the request scope resolves it. Fix: read the tenant inside the query (or apply it viaHasQueryFilterwithIHttpContextAccessor) instead of capturing it at construction.
You
/admin/usersis 401-ing for Anna, but her token looks valid to me. What does the auth handler actually see?
Claude
I'll break inside
JwtBearerHandler.HandleAuthenticateAsyncafter her request lands.Token signature: ✓ valid Claims built: name : anna role : User iss : https://auth.staging.example aud : app-api exp : 2026-05-26T14:12:00Z (not expired)The token validates fine — but the claim is
role=User. Your endpoint is[Authorize(Roles="Admin")]. So the 401 is correct: Anna isn't actually an admin yet upstream. Either her IdP record needs updating, or this policy is wrong.
You
I think capping
discountat 100 fixes the bug. Test that hypothesis without me touching the code.
Claude
I'll pause inside
ApplyDiscounton the next checkout and mutatediscountin place.Paused at PricingService.cs:47 discount = 250 ← bug: two promos stacked Set discount = 100, resumed. Result: subtotal = $400 final = $300 refund-service complaints: 0Capping at 100 unblocks the flow downstream. Hypothesis confirmed — time to make the edit for real and decide where the cap belongs (
ApplyDiscountitself, or upstream inPromoEngine).
You
/reportshangs forever in staging. Attach and tell me why.
Claude
Attached. Ran
hang_analyze.Thread 12 (HTTP request) → blockedOnTask at ReportService.cs:38 Task.Wait() on T#14 Thread 14 (worker) → blockedOnMonitor at SqlConnectionPool.cs:91 waiting for SqlConnection (pool max=5, in-use=5)Classic sync-over-async deadlock. Thread 12 calls
.Wait()on a task that itself needs to open anotherSqlConnectionfrom a fully-held pool. The connection it's holding can't be released until the task completes; the task can't proceed until a connection frees up. Fix:awaitall the way down inReportService, or don't hold a connection across the awaited call.
You
GET /order/42takes 800ms. I don't want to set breakpoints all over — just show me where the time is going.
Claude
I'll auto-instrument your order pipeline and fire the request. Each entry logs the timestamp + arguments, then resumes — the code runs near-normal speed.
[+ 4ms] → OrderController.GetOrder() id=42 [+ 6ms] --→ OrderService.LookupOrder() id=42 [+ 9ms] ----→ OrderRepository.FetchById() id=42 [+ 14ms] ------→ SqlClient.ExecuteQuery() sql="SELECT * FROM orders WHERE id=42" [+ 287ms] ----→ EnrichmentService.Enrich() raw="rows(...)" [+ 781ms] ------→ HttpClient.PostAsync() url="https://crm.internal/enrich"Time is in the CRM enrichment HTTP call — 500ms inside
HttpClient.PostAsync. DB itself was 5ms. Worth cachingEnrichmentService.Enrichor moving it off the request path.
Claude (MCP client)
│ MCP (stdio / JSON-RPC)
▼
aspnetcore-debugger-mcp ← this server
│ DAP (Debug Adapter Protocol)
▼
netcoredbg ← Samsung's MIT-licensed .NET debugger, child process
│ ICorDebug
▼
target .NET process
A protocol bridge with agent-friendly composites on top — exception_autopsy, stack_explore,
hang_analyze, and the trace tools — that bundle multiple DAP requests into a single tool call.
dotnet tool install -g AspNetCoreDebuggerMcp --prerelease
The package bundles prebuilt netcoredbg for linux-x64, linux-arm64, win-x64, osx-x64, and osx-arm64 — no separate install needed.claude mcp add aspnetcore-debugger -- aspnetcore-debugger-mcp
…or edit .mcp.json (project-scoped) / ~/.claude.json (global) / claude_desktop_config.json (Claude Desktop) directly:
{
"mcpServers": {
"aspnetcore-debugger": {
"command": "aspnetcore-debugger-mcp"
}
}
}
/mcp confirms it's connected. From there, describe what you want — "why does this endpoint return null" — and the agent picks the right tools.Bundled netcoredbg binary is selected at runtime — no per-platform install dance.
Requires the .NET 10 SDK on the host. The MCP server itself is a cross-platform .NET global tool — same install command everywhere.
Different sweet spots: this project is the MIT, cross-platform option, with ASP.NET-flavoured composites on top of a DAP. debug-mcp goes deeper into runtime internals via ICorDebug but is Linux-only and AGPL today.
MIT — see LICENSE. Built on netcoredbg (MIT) and the ModelContextProtocol SDK (MIT).
MCP server that lets AI agents (Claude, Cursor) debug your .NET / ASP.NET Core app
{ "mcpServers": { "magna-nz-aspnetcore-debugger-mcp": { "command": "nuget", "args": [ "AspNetCoreDebuggerMcp" ] } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Aspnetcore Debugger s'exécute en local via stdio.
Dernière vérification : 2026-10-28. MCP server that lets AI agents (Claude, Cursor) debug your .NET / ASP.NET Core app