mcp-csharp-debug

Debug and test C# MCP servers with IDE integration and protocol inspection.

Updated May 1, 2026
One-click install
npx skills add https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions --skill mcp-csharp-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-csharp-debug
Source: https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions/tree/main/.claude/skills/mcp-csharp-debug
Command: npx skills add https://github.com/BenjaminMichaelis/mcp-server-dotnet-az-functions --skill mcp-csharp-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables developers to run, debug, and test C# MCP servers locally, facilitating smooth setup and troubleshooting for development workflows.

Core Features & Use Cases

  • Local MCP server execution: Run MCP servers on your machine to verify behavior and logs.
  • IDE debugging integration: Configure Visual Studio or VS Code for breakpoints and inspection during runtime.
  • Protocol testing and troubleshooting: Use MCP Inspector to send requests and analyze responses, diagnosing tool registration issues and protocol errors.
  • Tool discovery: Verify that registered tools appear correctly in Copilot Agent Mode and respond as expected.
  • Logging setup: Properly configure logging to stderr for stdio servers and custom log to files for error tracking.
  • Error diagnosis: Step through tool execution, check registration attributes, and examine environment/configuration issues.

Quick Start

Launch your MCP server project in Debug mode through IDE, attach debugger, and set breakpoints in your tool methods to observe execution, then trigger tools via MCP Inspector or Copilot to test behavior.

Frequently Asked Questions about mcp-csharp-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a C# MCP server locally in Visual Studio?

Debug a C# MCP server locally by launching your project in Debug mode through the IDE, attaching the debugger to set breakpoints in tool methods, and observing runtime execution. This enables detailed IDE integration for stepping through tool execution and inspecting variables.

Why are my registered MCP tools not showing up in Copilot Agent Mode?

Registered MCP tools may not appear in Copilot Agent Mode due to protocol errors or incorrect registration attributes. Use the MCP Inspector to send requests, analyze responses, and diagnose tool discovery issues to ensure tools register correctly and respond predictably.

How do I configure logging for a stdio MCP server to track errors?

Configure logging for a stdio MCP server by directing logs to stderr and setting up custom log files for error tracking. Proper logging configuration maintains protocol integrity and helps diagnose environment or configuration issues during local development.

What is the best way to test MCP protocol responses and troubleshoot errors?

The best way to test MCP protocol responses is using the MCP Inspector to send requests and analyze responses. This troubleshooting process diagnoses tool registration issues, verifies protocol integrity, and ensures tools respond predictably in your dev environment.

Can I use VS Code to step through MCP server tool execution and inspect variables?

Yes, you can use VS Code for IDE debugging integration with C# MCP servers. Launch your project in Debug mode, attach the debugger, and set breakpoints in your tool methods to step through execution, inspect variables, and examine environment configuration issues.