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 MCP server publishing. DO NOT USE FOR: publishing general NuGet libraries (not MCP-specific), general Docker guidance unrelated to MCP, creating new servers (use mcp-csharp-create), debugging (use mcp-csharp-debug), writing tests (use mcp-csharp-test).
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add dotnet/skills --skill mcp-csharp-publishCompatible with
Supported agents
| name | mcp-csharp-publish |
| description | > 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 MCP server publishing. DO NOT USE FOR: publishing general NuGet libraries (not MCP-specific), general Docker guidance unrelated to MCP, creating new servers (use mcp-csharp-create), debugging (use mcp-csharp-debug), writing tests (use mcp-csharp-test). |
| license | MIT |
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.
server.json metadata for the MCP Registrymcp-csharp-test firstmcp-csharp-debugmcp-csharp-createnuget-trusted-publishing instead| Input | Required | Description |
|---|---|---|
| Transport type | Yes | stdio → NuGet path, http → Docker/Azure path |
| Target destination | Yes | NuGet.org, Docker registry, Azure Container Apps, Azure App Service, MCP Registry |
| Project path | Yes | Path to the .csproj file |
| Package ID / server name | Required for publishing | NuGet PackageId or MCP Registry name |
| Transport | Primary Destination | Users Run With |
|---|---|---|
| stdio | NuGet.org | dnx YourPackage@version |
| HTTP | Docker → Azure | Container URL |
Both paths can optionally publish to the MCP Registry for discoverability.
.csproj with package properties:<PropertyGroup>
<PackAsTool>true</PackAsTool>
<ToolCommandName>mymcpserver</ToolCommandName>
<PackageId>YourUsername.MyMcpServer</PackageId>
<Version>1.0.0</Version>
<Authors>Your Name</Authors>
<Description>MCP server for interacting with MyService</Description>
<PackageLicenseExpression>MIT</PackageLicenseExpression>
<PackageTags>mcp;modelcontextprotocol;ai;llm</PackageTags>
<PackageReadmeFile>README.md</PackageReadmeFile>
</PropertyGroup>
<ItemGroup>
<None Include="README.md" Pack="true" PackagePath="\" />
</ItemGroup>
dotnet build -c Release
dotnet pack -c Release
dotnet tool install --global --add-source bin/Release/ YourUsername.MyMcpServer
mymcpserver --help # verify it runs
dotnet tool uninstall --global YourUsername.MyMcpServer
dotnet nuget push bin/Release/*.nupkg \
--api-key YOUR_NUGET_API_KEY \
--source https://api.nuget.org/v3/index.json
mcp.json:{
"servers": {
"MyMcpServer": {
"type": "stdio",
"command": "dnx",
"args": ["YourUsername.MyMcpServer@1.0.0", "--yes"]
}
}
}
For detailed NuGet packaging and trusted publishing setup, see references/nuget-packaging.md.
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
WORKDIR /src
COPY *.csproj ./
RUN dotnet restore
COPY . ./
RUN dotnet publish -c Release -o /app
FROM mcr.microsoft.com/dotnet/aspnet:10.0
WORKDIR /app
COPY --from=build /app .
# Non-root user for security
RUN adduser --disabled-password --gecos '' appuser
USER appuser
ENV ASPNETCORE_URLS=http://+:8080
EXPOSE 8080
HEALTHCHECK --interval=30s --timeout=3s --start-period=10s --retries=3 \
CMD curl -f http://localhost:8080/health || exit 1
ENTRYPOINT ["dotnet", "MyMcpServer.dll"]
docker build -t mymcpserver:latest .
docker run -d -p 3001:8080 -e API_KEY=test-key --name mymcpserver mymcpserver:latest
curl http://localhost:3001/health
# Docker Hub
docker tag mymcpserver:latest <yourusername>/<mymcpserver>:1.0.0
docker push <yourusername>/<mymcpserver>:1.0.0
# Azure Container Registry
az acr login --name yourregistry
docker tag mymcpserver:latest <yourregistry>.azurecr.io/<mymcpserver>:1.0.0
docker push <yourregistry>.azurecr.io/<mymcpserver>:1.0.0
Azure Container Apps (recommended — serverless with auto-scaling):
az containerapp create \
--name mymcpserver \
--resource-group mygroup \
--environment myenvironment \
--image <yourregistry>.azurecr.io/<mymcpserver>:1.0.0 \
--target-port 8080 \
--ingress external \
--min-replicas 0 \
--max-replicas 10 \
--secrets api-key=my-actual-api-key \
--env-vars API_KEY=secretref:api-key
Azure App Service (traditional web hosting):
az webapp create \
--name mymcpserver \
--resource-group mygroup \
--plan myplan \
--deployment-container-image-name <yourregistry>.azurecr.io/<mymcpserver>:1.0.0
For detailed Azure deployment, see references/docker-azure.md.
List your server in the official MCP Registry for discoverability.
mcp-publisher:# macOS/Linux
brew install mcp-publisher
# Or download from https://github.com/modelcontextprotocol/registry/releases
.mcp/server.json (or run mcp-publisher init to generate interactively):{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"name": "io.github.username/servername",
"description": "Your server description",
"version": "1.0.0",
"packages": [{
"registryType": "nuget",
"registryBaseUrl": "https://api.nuget.org",
"identifier": "YourUsername.MyMcpServer",
"version": "1.0.0",
"transport": { "type": "stdio" }
}],
"repository": {
"url": "https://github.com/username/repo",
"source": "github"
}
}
Version consistency (critical): The root
version,packages[].version, and<Version>in.csprojmust all match. A mismatch causes registry validation failures or users downloading the wrong version.
mcp-publisher login github # name must be io.github.<username>/... for GitHub auth
mcp-publisher publish
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.<username>/<servername>"
For Registry details (namespace conventions, environment variables, CI/CD automation), see references/mcp-registry.md.
dnx PackageId@versionregistry.modelcontextprotocol.io| Pitfall | Solution |
|---|---|
| NuGet package doesn't run as a tool | Missing <PackAsTool>true</PackAsTool> in .csproj |
Version mismatch between .csproj and server.json | Keep <Version>, server.json root version, and packages[].version in sync |
| Docker container exits immediately | Check entrypoint DLL name matches project output. Run docker logs mymcpserver for errors |
| Azure Container App returns 502 | Target port mismatch. Ensure --target-port matches ASPNETCORE_URLS port in the container |
| MCP Registry rejects publish | Name must follow namespace convention: io.github.<username>/<name> for GitHub auth |
| API keys leaked in Docker image | Use multi-stage builds. Never COPY .env files. Pass secrets via --env-vars at runtime |
mcp-csharp-create — Create a new MCP server projectmcp-csharp-debug — Running and interactive debuggingmcp-csharp-test — Automated tests and evaluations.csproj configuration, server.json for MCP, NuGet.org push, testing with dnx, version management. Load when: publishing a stdio server to NuGet.mcp-publisher CLI installation, server.json schema, namespace conventions (GitHub vs DNS auth), CI/CD automation. Load when: publishing to the official MCP Registry.AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmcp-csharp-publishExecute the skills CLI command in your project's root directory to begin installation:
epx add dotnet/skills --skill mcp-csharp-publishFetches mcp-csharp-publish from dotnet/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/mcp-csharp-publish
Restart Cursor to activate mcp-csharp-publish. Access via /mcp-csharp-publish in your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
optimizing-ef-core-queries
dotnet/skills · dotnet-data · same repo
crap-score
dotnet/skills · dotnet-test · same repo
eval-performance
dotnet/skills · dotnet-msbuild · same repo
property-patterns
dotnet/skills · dotnet-msbuild · same repo
migrate-nullable-references
dotnet/skills · dotnet-upgrade · same repo
maui-data-binding
dotnet/skills · dotnet-maui · same repo
Useful defaults in mcp-csharp-publish — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
mcp-csharp-publish is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: mcp-csharp-publish is focused, and the summary matches what you get after install.
mcp-csharp-publish reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added mcp-csharp-publish from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
mcp-csharp-publish is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in mcp-csharp-publish — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend mcp-csharp-publish for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
mcp-csharp-publish fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: mcp-csharp-publish is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 39