MCP工具

Requirements

• For Quick Install: .NET 10 SDK
• For Manual Install: .NET 10 SDK
• Visual Studio Code, Visual Studio 2022 (v17.13+), or Claude Desktop

Trust the certificate (may require elevation)

dotnet dev-certs https --trust

*Certificate is now trusted. Try running your app again. If you're using Docker, you can export the certificate:*

Quick Install

Click to install in your preferred environment:

Note: Quick install requires .NET 10 SDK.

Installation

Option 1: Quick Install (Recommended)

Use the install badges at the top of this page to automatically configure the MCP server in your environment. The server will be downloaded from NuGet.org on first use.

Install dotnet-ef tool globally

dotnet tool install dotnet-ef --global

Clean and rebuild

dotnet clean dotnet build -c Release

HTTPS Development Setup

User: "I'm getting HTTPS certificate errors when running my web app"

AI: Let me check your HTTPS development certificate...

```bash

Export for Docker containers

dotnet dev-certs https --export-path ./certs/aspnetapp.pfx --password "SecurePassword123!" ```

Certificate exported to ./certs/aspnetapp.pfx. You can now mount it in your Docker container.

Mobile and MAUI Development Setup

User: "I want to develop a .NET MAUI app for Android and iOS"

AI: I'll help you set up the necessary workloads for MAUI development...

```bash

Install MAUI workloads for Android and iOS

List installed workloads

dotnet workload list

*Output:*

Installed Workload Id Manifest Version Installation Source

maui-android 10.0.100/10.0.100 SDK 10.0.100 maui-ios 10.0.100/10.0.100 SDK 10.0.100

*Now you can create a MAUI project:*

Update all installed workloads

dotnet workload update ```

Building from Source

For development or contributing:

git clone https://github.com/jongalloway/dotnet-mcp.git
cd dotnet-mcp
dotnet build --project DotNetMcp/DotNetMcp.csproj

Run the server:

dotnet run --project DotNetMcp/DotNetMcp.csproj

The server communicates via stdio transport and is designed to be invoked by MCP clients.

Usage Examples

Once configured, you can use natural language with your AI assistant:

Quick Start - Single Project

User: "Create a new web API project called WeatherService"

AI: I'll create a new web API project for you...

dotnet new webapi -n WeatherService

The project has been created successfully in the WeatherService directory.

Option 2: Manual Configuration

Follow the instructions below for your specific development environment:

GitHub Copilot coding agent (Repository MCP configuration)

You can also configure this MCP server at the repository level for GitHub Copilot coding agent.

1. Open your repo on GitHub
2. Go to Settings > Copilot > Coding agent
3. Paste the JSON below into the MCP configuration box
4. Click Save

For details, see GitHub's documentation: Extending GitHub Copilot coding agent with the Model Context Protocol (MCP)

{
  "mcpServers": {
    "dotnet": {
      "type": "local",
      "command": "dnx",
      "args": ["Community.Mcp.DotNet@1.*", "--yes"],
      "tools": [
        "dotnet_project",
        "dotnet_package",
        "dotnet_solution",
        "dotnet_sdk",
        "dotnet_help",
        "dotnet_server_capabilities",
        "dotnet_server_info"
      ]
    }
  }
}

This configuration uses a curated allowlist of tools (instead of "*") so the agent can use the .NET MCP server safely and predictably.

Note: Copilot coding agent runs on GitHub Actions runners. If you need to ensure .NET 10 is installed for your repository, add a setup workflow like .github/workflows/copilot-setup-steps.yml.

Format all code according to .editorconfig

dotnet format

Secure Configuration with User Secrets

User: "Set up user secrets for my API project with a database connection string"

AI: I'll initialize user secrets for your project...

```bash

"Unrecognized option '--project'" or "Unknown switch" when running tests

- Cause: Test runner mismatch or SDK version incompatibility - Background: The --project flag is only supported by Microsoft Testing Platform (MTP). The legacy VSTest runner uses positional arguments instead. - Solution: The MCP server now auto-detects the test runner from global.json: 1. Auto mode (default): Add { "test": { "runner": "Microsoft.Testing.Platform" } } to global.json if using MTP, otherwise it defaults to VSTest 2. Explicit mode: Set testRunner: "MicrosoftTestingPlatform" or testRunner: "VSTest" when calling dotnet_project Test action 3. Legacy parameter: Use useLegacyProjectArgument: true (deprecated, use testRunner: "VSTest" instead) - Verify support: Run dotnet test --help | grep -- --project to check if your SDK supports the --project flag - More info: See doc/testing.md for detailed test runner compatibility and troubleshooting - References: dotnet test overview | MTP | VSTest

🧩 **MCP C# SDK Features Used**

dotnet-mcp uses the official MCP C# SDK and exercises a broad set of MCP features beyond basic tool invocation:

Create minimal API

dotnet new webapi -n MyMicroservices.Api --use-minimal-apis

Add project references for tests

dotnet add MyMicroservices.Api.Tests/MyMicroservices.Api.Tests.csproj reference MyMicroservices.Api/MyMicroservices.Api.csproj ```

Solution created with 4 projects: AppHost for orchestration, Web app, API, and unit tests. Ready to run with dotnet run --project MyMicroservices.AppHost.

Add Azure OpenAI API key

dotnet user-secrets set "Azure:OpenAI:ApiKey" "sk-..."

Add SendGrid API key

dotnet user-secrets set "SendGrid:ApiKey" "SG...."

*Let me show you what's configured:*

Warning: This will download several GB of SDKs and tools

dotnet workload install maui-android maui-ios

> **Note**: The command above shows the raw `dotnet` CLI syntax, which uses space-separated workload IDs. When calling the .NET MCP workload install tool, pass workload IDs as a single comma-separated parameter, for example: `workloadIds: "maui-android,maui-ios"`. The MCP server will translate this into the equivalent CLI command.

*Workloads installed! Let's verify:*

Add Entity Framework packages

dotnet add package Microsoft.EntityFrameworkCore dotnet add package Microsoft.EntityFrameworkCore.SqlServer dotnet add package Microsoft.EntityFrameworkCore.Design

Add integration test packages

dotnet add MyMicroservices.IntegrationTests package Microsoft.AspNetCore.Mvc.Testing dotnet add MyMicroservices.IntegrationTests package Microsoft.Testing.Extensions.CodeCoverage

Modernization Workflow

User: "Update all packages to latest versions, format all code to match our editorconfig rules, then build and run tests"

AI: I'll update packages, format code, build, and test...

```bash

Update all packages to latest compatible versions

dotnet package update

Troubleshooting