What problem does it solve? Running and debugging C# MCP servers locally involves tricky setup: configuring mcp.json for VS Code or Visual Studio, avoiding stdout contamination that corrupts the JSON-RPC protocol, and diagnosing why tools fail to appear in GitHub Copilot Agent Mode. This Skill provides a structured workflow to get a server running, tested, and debuggable. ## Core Features & Use Cases - Local Execution & IDE Configuration: Run servers via dotnet run for stdio or HTTP transports and generate mcp.json or launch.json for VS Code and Visual Studio. - Interactive Testing: Test tools, prompts, and resources with MCP Inspector and verify tool discovery in GitHub Copilot Agent Mode. - Troubleshooting & Logging: Diagnose tool registration failures, breakpoint issues, and stdout contamination, and configure stderr-safe logging for stdio servers. - Use Case: You built an MCP server but its tools do not appear in Copilot Agent Mode. Follow the workflow to rebuild, verify [McpServerTool] attributes and WithTools registration, then confirm discovery via MCP Inspector. ## Quick Start Ask the agent to run and debug your C# MCP server project, generate the mcp.json configuration, and test its tools with MCP Inspector.