mcp-dotnet-samples and MCP-Plugin-dotnet
About mcp-dotnet-samples
microsoft/mcp-dotnet-samples
A comprehensive set of samples of creating and using MCP servers and clients with .NET
Samples demonstrate building MCP servers that expose tools and resources to LLMs—including integrations with Azure services, GitHub, and Outlook—using .NET's structured approach to implement the standardized protocol. Projects are containerized for easy deployment and installable directly into VS Code and Visual Studio as AI model extensions. The collection covers both simple transformations (markdown-to-HTML) and complex workflows (email management, to-do tracking) to illustrate MCP's role in connecting LLMs to enterprise data sources and business logic.
About MCP-Plugin-dotnet
IvanMurzak/MCP-Plugin-dotnet
.NET MCP bridge: expose app methods/data as MCP tools, prompts, and resources via an in-app plugin + lightweight server (SignalR; stdio/http).
Implements a bridge architecture where a lightweight in-app SignalR client connects to a persistent MCP server gateway, enabling heavy .NET applications (Unity, WPF, game servers) to expose live functionality without independent lifecycle constraints. Built on ReflectorNet for automatic schema generation and fuzzy method matching, it supports attribute-based tool/prompt/resource registration with first-class dependency injection and assembly scanning. Offers both stdio and HTTP transport flexibility, with automatic reconnection resilience for maintaining long-lived connections.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work