An MCP (Model Context Protocol) server for building and testing .NET projects using `dotnet build` and `dotnet test` from Cursor.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dotnet-tools": {
"name": "DotNet Tools Server",
"stdio": true,
"command": "C:\\path\\to\\your\\DotNetToolsMcpServer.exe"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server for building and testing .NET projects using `dotnet build` and `dotnet test` from Cursor.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP Security Weekly
Get CVE alerts and security updates for Dotnet Tools Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server for building and testing .NET projects using dotnet build and dotnet test from Cursor.
This server provides a workaround for Cursor's current terminal issues when trying to build and test .NET projects directly.
You can either:
dotnet publish (AOT compiled into a single file, must be configured for the correct platform)Add this to your Cursor settings to use the MCP server:
{
"mcpServers": {
"dotnet-tools": {
"name": "DotNet Tools Server",
"stdio": true,
"command": "C:\\path\\to\\your\\DotNetToolsMcpServer.exe"
}
}
}
Replace the command path with the actual location of the executable on your system.
When run without command line arguments, the server operates as an MCP server for Cursor integration.
When run with command line arguments, the server operates as a CLI tool for managing library documentation configuration.
add-library --name="LibraryName" --url="https://..." - Add a library documentation URLremove-library --name="LibraryName" - Remove a library from configurationlist-libraries - List all configured librariesconfig-path - Display the path to the configuration fileopen-config - Open the configuration file in the default editor-h, -help, --help - Show help information# Show help
DotNetToolsMcpServer -h
DotNetToolsMcpServer --help
# Add a library
DotNetToolsMcpServer add-library --name="EasyReasy" --url="https://raw.githubusercontent.com/AdamTovatt/easy-reasy/refs/heads/master/EasyReasy/README.md"
# List all libraries
DotNetToolsMcpServer list-libraries
# Show config file location
DotNetToolsMcpServer config-path
# Open config file for editing
DotNetToolsMcpServer open-config
The configuration is stored in a local markdown file at:
%APPDATA%\DotNetToolsMcpServer\libraries.md~/.config/DotNetToolsMcpServer/libraries.mdThe file uses markdown format:
- [LibraryName](https://url-to-documentation.md)
This MCP server provides the following tools:
mcp_dotnet-tools_build - Builds a .NET project using dotnet buildmcp_dotnet-tools_build_solution - Builds a .NET solution using dotnet buildmcp_dotnet-tools_run_tests - Runs all tests in a .NET test projectmcp_dotnet-tools_run_specific_tests - Runs specific tests using custom filtersmcp_dotnet-tools_list_available_documentation_files - Lists all available documentation filesmcp_dotnet-tools_get_documentation_for_library - Gets documentation for a specific library by NuGet package nameThe server supports user-configurable library documentation. Instead of using a hardcoded URL, users can add their own library documentation files through the CLI commands. The documentation tool will read from the local configuration file to provide documentation for configured libraries.