.NET MCP Server
Let your coding agent run dotnet CLI workflows—new projects, NuGet packages, build, and test—without you context-switching out of the agent chat.
Overview
io.github.jongalloway/dotnet-mcp is a MCP server for the Build phase that exposes .NET SDK project, package, build, and test commands to AI assistants over stdio.
What is this MCP server?
- .NET MCP Server exposing SDK operations: projects, packages, build, test, dev tools
- NuGet package Community.Mcp.DotNet v1.1.2 with dnx runtime hint
- stdio MCP transport with optional DOTNET_SKIP_FIRST_TIME_EXPERIENCE and DOTNET_NOLOGO env defaults
- Bridges AI assistants to the same CLI you would use in a terminal
- Server version 1.1.2
- NuGet identifier Community.Mcp.DotNet
- stdio transport with dnx runtimeHint
Community signal: 26 GitHub stars.
What problem does it solve?
Your agent helps you write C# but cannot reliably run dotnet new, restore, build, or test without you manually pasting terminal output.
Who is it for?
Indie and solo developers building on .NET who use Claude Code or Cursor and want SDK commands as first-class agent tools.
Skip if: Pure JavaScript/Python shops with no .NET SDK, or teams that forbid agents from executing local CLI commands.
What do I get? / Deliverables
After registration, the agent drives official .NET CLI workflows through MCP so project setup and verification stay inside the coding session.
- Agent-invokable dotnet project, package, build, and test operations
- Reduced manual terminal context-switching during .NET implementation
Recommended MCP Servers
Journey fit
.NET SDK operations are core backend build work for solo developers shipping C# APIs, tools, or Blazor apps with agent assistance. backend is the shelf for MCP servers that wrap the .NET SDK rather than frontend or docs-only tooling.
How it compares
.NET SDK MCP bridge, not a Claude Code planning skill or a cloud-only PaaS deploy integration.
Common Questions / FAQ
Who is dotnet-mcp for?
Solo builders and small teams on .NET who want their MCP-enabled coding agent to run SDK workflows safely from chat.
When should I use dotnet-mcp?
Use it during backend build and test loops when the agent should create projects, add packages, build, and run tests via dotnet.
How do I add dotnet-mcp to my agent?
Install or reference NuGet package Community.Mcp.DotNet with dnx per registry docs, add the stdio MCP server entry, set DOTNET env vars if desired, and ensure the .NET SDK is installed locally.