A Model Context Protocol server implementation for dotnet commands using the ModelContextProtocol NuGet package
{
"mcpServers": {
"dotnetmcpserver2": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol server implementation for dotnet commands using the ModelContextProtocol NuGet package
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 14 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for DotNetMcpServer2 and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A comprehensive Model Context Protocol (MCP) server that exposes .NET CLI commands and Entity Framework operations as MCP tools, built using the official Microsoft ModelContextProtocol library.
This version uses the Microsoft ModelContextProtocol library instead of MCPSharp, providing:
Microsoft.Extensions.Hosting for robust server lifecycle managementWithToolsFromAssembly()[McpServerTool] and [Description] attributes instead of custom MCP attributes[McpTool("dotnet_version", "Gets the installed .NET version")]
public static async Task<string> GetVersionAsync()
// Registration
MCPServer.Register<DotNetCoreCommands>();
await MCPServer.StartAsync("DotNetMcpServer", "1.0.0");
[McpServerTool, Description("Gets the installed .NET version")]
public static async Task<string> GetVersionAsync()
// Registration
builder.Services
.AddMcpServer()
.WithStdioServerTransport()
.WithToolsFromAssembly();
Single-file AOT compilation provides maximum performance and minimal deployment footprint:
Ultra-lightweight Docker containers with AOT-compiled binaries:
Standard .NET runtime for development and debugging.
# Build AOT executable
.\build-aot.ps1
# Use in Claude Desktop
{
"mcpServers": {
"dotnet-mcp-server2": {
"command": "C:\\path\\to\\publish\\win-x64\\DotNetMcpServer2.exe"
}
}
}
# Build Docker image
.\build-docker.ps1
# Use in Claude Desktop
{
"mcpServers": {
"dotnet-mcp-server2": {
"command": "docker",
"args": ["run", "--rm", "-i", "dotnet-mcp-server2:latest"]
}
}
}
# Run directly
cd DotNetMcpServer2
dotnet run
# Use in Claude Desktop
{
"mcpServers": {
"dotnet-mcp-server2": {
"command": "dotnet",
"args": ["run", "--project", "C:\\path\\to\\DotNetMcpServer2.csproj"]
}
}
}
Cross-platform PowerShell:
.\build-aot.ps1 # Interactive runtime selection
.\build-aot.ps1 -Runtime win-x64 # Specific runtime
Windows Batch:
.\build-aot-simple.bat # Interactive menu
# Windows x64
dotnet publish -c Release -r win-x64 --self-contained true
# Linux x64
dotnet publish -c Release -r linux-x64 --self-contained true
# macOS ARM64 (Apple Silicon)
dotnet publish -c Release -r osx-arm64 --self-contained true