Run and debug C# MCP servers locally. Covers IDE configuration, MCP Inspector testing, GitHub Copilot Agent Mode integration, logging setup, and troubleshooting. USE FOR: running MCP servers locally with dotnet run, configuring VS Code or Visual Studio for MCP debugging, testing tools with MCP Inspector, testing with GitHub Copilot Agent Mode, diagnosing tool registration issues, setting up mcp.json configuration, debugging MCP protocol messages, configuring logging for stdio and HTTP servers. D
SkillScore100Maintained
Automatic
◆AI Engineer pack
Last verified 8/19/2026
What it changes
Passed 22 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill100%
Checks it passed that the model alone missed
The server entry specifies "type": "stdio".
The JSON configuration uses the top-level key "servers".
Starts the C# server using dotnet run in one terminal step.
and 6 more in the full report
7 fixed15 passed either way0 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+59%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/19/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I am developing a C# MCP server in Visual Studio 2022 (not VS Code). I want to add an MCP configuration file so local tools can discover my server. Where should this file be created and what is its exact file name?
What was checked, without and with the skill
Checked
Without skill
With skill
Places the config file as .mcp.json at the solution root directory.
Missed
Passed
case-10 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md200 lines3 files
C# MCP Server Debugging
Run, debug, and interactively test C# MCP servers. Covers local execution, IDE debugging with breakpoints, MCP Inspector for protocol-level testing, and GitHub Copilot Agent Mode integration.
When to Use
Running an MCP server locally for the first time
Configuring VS Code or Visual Studio to debug an MCP server
Testing tools interactively with MCP Inspector
Verifying tools appear in GitHub Copilot Agent Mode
Diagnosing issues: tools not discovered, protocol errors, server crashes
Setting up mcp.json or .mcp.json configuration
Stop Signals
No project yet? → Use mcp-csharp-create first
Need automated tests? → Use mcp-csharp-test
Production deployment issue? → Use mcp-csharp-publish
Inputs
Input
Required
Description
Project path
Yes
Path to the .csproj file or project directory
Transport type
Recommended
stdio or http — detect from .csproj if not specified
IDE
Recommended
VS Code or Visual Studio — detect from environment if not specified
Agent behavior: Detect transport type by checking the .csproj for a PackageReference to ModelContextProtocol.AspNetCore. If present → HTTP, otherwise → stdio.
Workflow
Step 1: Run the server locally
stdio transport:
cd <ProjectDir>
dotnet run
The process starts and waits for JSON-RPC messages on stdin. No output on stdout means it's working correctly.
Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. USE FOR: unified frontend lint commands; combined ESLint, Stylelint, HTMLHint, or similar checks; CI orchestration over multiple frontend linters. DO NOT USE FOR: simple repos where Biome already covers the required surface; teams that have not decided which underlying linters own each file type. INVOKES: inspect the repository context, edit targeted files, and run