What problem does it solve?
Troubleshooting C# Model Context Protocol (MCP) servers is hard when tools fail to register, the IDE cannot attach, or the MCP protocol breaks due to incorrect stdio logging.
Core Features & Use Cases
- Local run and transport setup: Run C# MCP servers via
stdio or http, with transport detection guidance based on the MCP ASP.NET Core package reference.
- IDE debugging workflows: Configure VS Code and Visual Studio for debugging, including breakpoints, launch profiles, and attach-to-process options.
- Protocol-level validation: Test tools with MCP Inspector to confirm schemas, tool registration, and request/response behavior, then validate integration with GitHub Copilot Agent Mode.
- Logging and troubleshooting guardrails: Prevent MCP JSON-RPC corruption by ensuring stdio servers never write logs to stdout, and diagnose common failure modes like garbled output, missing tool registration, and HTTP endpoint issues.
Quick Start
Run your C# MCP server locally and test its registered tools with MCP Inspector to confirm transport, schemas, and protocol messages are working end-to-end.