Publish and deploy C# MCP servers. Covers NuGet packaging for stdio servers, Docker containerization for HTTP servers, Azure Container Apps and App Service deployment, and publishing to the official MCP Registry. USE FOR: packaging stdio MCP servers as NuGet tools, creating Dockerfiles for HTTP MCP servers, deploying to Azure Container Apps or App Service, publishing to the MCP Registry at registry.modelcontextprotocol.io, configuring server.json for MCP package metadata, setting up CI/CD for MC
SkillScore96Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 22 of 23 test cases with the skill, and 12 of 23 without it.
Without skill52%
With skill96%
Checks it passed that the model alone missed
The response specifies placing the manifest at .mcp/server.json.
The response includes registryType set to nuget inside the package entry.
The response specifies stdio as the transport type in the client configuration.
and 13 more in the full report
10 fixed12 passed either way1 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+81%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/19/2026v122 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Where should the MCP Registry manifest file be placed in the repository, what exact schema URL must it declare, and what file format does it use?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies placing the manifest at .mcp/server.json.
Missed
Passed
The response specifies using the official 2025-12-11 static schema URL in the $schema property.
Missed
Passed
case-13 · 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.md260 lines4 files
C# MCP Server Publishing
Publish and deploy MCP servers to their target platforms. stdio servers are distributed as NuGet tool packages. HTTP servers are containerized and deployed to Azure or other container hosts. Both can optionally be listed in the official MCP Registry.
When to Use
Packaging a stdio MCP server for NuGet distribution
Creating a Docker container for an HTTP MCP server
Deploying to Azure Container Apps or App Service
Publishing to the official MCP Registry for discoverability
Setting up server.json metadata for the MCP Registry
Stop Signals
Server not tested yet? → Use mcp-csharp-test first
Server not working locally? → Use mcp-csharp-debug
No server project yet? → Use mcp-csharp-create
Publishing a non-MCP NuGet package? → Use nuget-trusted-publishing instead
Use the open-source free `Meziantou.Analyzer` package for design, usage, security, performance, and style rules in .NET. Use when a repo wants broader analyzer coverage with a single NuGet package. USE FOR: the repo uses or wants Meziantou.Analyzer; the team wants one analyzer pack that covers design, usage, security, performance, and style. DO NOT USE FOR: repos that already enforce an overlapping analyzer baseline and do not want extra diagnostics; formatting-only work. INVOKES: inspect the re