Dotnetdevmcp MCP server
io.github.csa7mdm/dotnetdevmcp·v0.3.4MCP server that gives AI coding agents Roslyn's compiler view of a .NET solution.
0 stars
Reviews
Write oneNobody has reviewed Dotnetdevmcp yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dotnetdevmcp tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Dotnetdevmcp compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
Release history: 3 versions in the registry since 2026-09-23, latest 2026-09-25, typically one every 1 day.
Install Dotnetdevmcp in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Dotnetdevmcp repository's README, as published. We do not edit it. Read it on GitHub
DotNetDevMCP
<!-- mcp-name: io.github.csa7mdm/dotnetdevmcp -->
An MCP server that gives AI coding agents real .NET tooling: Roslyn code intelligence, dotnet build/test, git, and an orchestrator that runs those tools concurrently as a dependency graph.
Agents working on .NET code usually get by with grep and shelling out to dotnet. That means they read files instead of symbols, edit text instead of syntax trees, and run one command at a time. DotNetDevMCP replaces that with 53 tools that use the compiler's view of your solution and can run builds, tests and analysis in parallel.
Install
Requires the .NET 10 SDK.
Claude Code
claude mcp add dotnetdevmcp -- dnx DotNetDevMCP --yesVS Code / Visual Studio (.mcp.json or .vscode/mcp.json)
{
"servers": {
"dotnetdevmcp": {
"type": "stdio",
"command": "dnx",
"args": ["DotNetDevMCP", "--yes"]
}
}
}Claude Desktop / Cursor / any stdio client (mcpServers form)
{
"mcpServers": {
"dotnetdevmcp": {
"command": "dnx",
"args": ["DotNetDevMCP", "--yes", "--", "--load-solution", "C:/src/MyApp/MyApp.sln"]
}
}
}dnx downloads the package from NuGet.org on first run. Prefer a permanent install? dotnet tool install -g DotNetDevMCP, then use dotnetdevmcp as the command.
Pass --load-solution to have Roslyn load your solution at startup, or let the agent call SharpTool_LoadSolution when it needs to. --http --port 3001 serves Streamable HTTP instead of stdio. dotnetdevmcp --help lists everything.
By default, the Roslyn edit tools (SharpToolRenameSymbol, OverwriteMember, AddMember, MoveMember, FindAndReplace, CreateRoslynDocument, OverwriteRoslynDocument, ManageUsings, ManageAttributes) never touch git - they apply changes to disk and return the usual compile-check output, nothing else. Pass --git-commit-edits to opt into the old behavior: each edit creates a sharptools/ branch (if you aren't already on one) and commits the change, which is also what SharpToolUndo needs in order to revert. Without the flag, SharpTool_Undo returns an explanatory error instead of failing obscurely. (--disable-git still exists but is a no-op now that git integration is opt-in by default.)
What the agent gets
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Dotnetdevmcp: common questions
- Is Dotnetdevmcp MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Dotnetdevmcp safety report
- Does Dotnetdevmcp need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Dotnetdevmcp maintained?
- The last commit was 16 days ago (2026-10-19). The latest release is v0.3.4.