mcp and MCP-Plugin-dotnet
These are ecosystem siblings: Microsoft's official MCP server implementations provide the protocol specification and reference implementations that .NET developers can integrate with, while the .NET MCP bridge enables .NET applications to expose their own methods as MCP-compatible tools and resources within that same ecosystem.
About mcp
microsoft/mcp
Catalog of official Microsoft MCP (Model Context Protocol) server implementations for AI-powered data access and tool integration
This project provides official server implementations of Microsoft's Model Context Protocol (MCP). It helps developers connect their AI assistants, like those in IDEs, with various Microsoft services such as Azure, Microsoft Fabric, and Azure DevOps. By enabling these connections, developers can leverage AI to access data and integrate tools consistently, enhancing the capabilities and flexibility of their AI applications.
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).
This tool helps .NET developers integrate their desktop applications, game servers, or Unity projects with AI assistants like Claude. It allows the AI to trigger methods, access data, and utilize prompts from a running .NET application. The developer defines what their app can offer, and the AI can then interact with the live application instance.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work