dotnet-mcp

Integrates .NET applications with MCP servers via the official SDK.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcp-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-mcp
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-mcp
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcp-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build or consume Model Context Protocol (MCP) servers and clients in .NET using the official MCP C# SDK, enabling seamless interoperability and capability negotiation across stdio and HTTP transports.

Core Features & Use Cases

  • MCP-enabled .NET servers and clients with tooling to publish, discover, and negotiate capabilities.
  • Support for stdio and HTTP transports, including Streamable HTTP, ASP.NET Core hosting, and client composition.
  • Guidance and examples for integrating tools, prompts, resources, and logging within MCP workflows.

Quick Start

Use the MCP .NET SDK to spin up a minimal client and enumerate tools from a simple MCP server.

Frequently Asked Questions about dotnet-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Model Context Protocol server in .NET?

You can build a Model Context Protocol server in .NET using the official MCP C# SDK to define tools, prompts, and resources. It supports ASP.NET Core hosting and Streamable HTTP for remote MCP server workflows.

Can I connect a .NET application to a remote MCP server over HTTP?

Yes, you can connect a .NET application to a remote MCP server over HTTP using HttpClientTransport. The MCP .NET SDK enables client composition and capability negotiation across both local stdio and HTTP transports.

What .NET version is required for MCP client and server integration?

MCP client and server integration requires .NET 8 or later. The SDK provides package options including ModelContextProtocol.Core, ModelContextProtocol, and ModelContextProtocol.AspNetCore to support various hosting scenarios.

How does capability negotiation work with MCP in C#?

Capability negotiation in C# is handled by the MCP SDK, allowing .NET clients and servers to automatically discover and agree on supported tools, resources, and prompts during the interop workflow over stdio or HTTP transports.

What is the best way to enumerate tools from an MCP server in .NET?

The best way to enumerate tools is to spin up a minimal MCP client using the .NET SDK. The client connects via StdioClientTransport or HttpClientTransport and queries the server to discover available tools and capabilities.

Does the MCP C# SDK support local stdio transports?

Yes, the MCP C# SDK fully supports local stdio transports through StdioClientTransport. This allows .NET applications to launch and communicate with local MCP servers seamlessly for tool and resource integration.