Best for
- Teams developing MCP integrations with C# or .NET.
- Projects needing client APIs, low-level server APIs, hosting support, or ASP.NET Core integration.
- Developers who want the official MCP C# SDK documentation and samples.
M
MCP C# SDK
Official
The official C# SDK for building MCP clients and servers.
GitHub source repository ↗
56FMRS · C
This is the official MCP C# SDK maintained by the modelcontextprotocol project in collaboration with Microsoft. The source confirms support for .NET client and server development and several extensions, but provides no standalone server manifest, tool list, transport declaration, or client configuration example.
The MCP C# SDK is the official C# SDK for the Model Context Protocol, enabling .NET applications, services, and libraries to implement and interact with MCP clients and servers. It is maintained in collaboration with Microsoft and provides core APIs, hosting and dependency-injection extensions, ASP.NET Core HTTP server support, and MCP Apps and MCP Tasks extensions.
Tools
The tool list has not been reviewed yet.
Setup
Choose and install ModelContextProtocol.Core, ModelContextProtocol, ModelContextProtocol.AspNetCore, or the relevant extension package for the project. See the Getting Started documentation and the samples directory for installation guidance and examples. The repository root contains SDK source code and is not a standalone MCP server configuration.
Fit and risk
Not for
- Users looking to install and run a ready-made MCP tool server.
- Projects that do not use C# or .NET.
- Users expecting a repository manifest with declared tools, transports, or client configuration.
Required permissions
- The source does not define fixed runtime permissions for the SDK itself.
- Actual permissions depend on the application, server, data sources, and tools built with the SDK.
Risks and side effects
- The SDK is not a configured standalone MCP server, so using the repository directly as a server may not work.
- Applications built with the SDK may access external data sources or execute tools; implementers must review the actual scope.
- The source does not provide specific version, compatibility, or runtime requirements, so deployment should be checked against the project documentation and package information.
Troubleshooting
- Confirm that the selected NuGet package matches the project requirements.
- Check that the client or server was configured according to the Getting Started documentation.
- Use the samples directory and API documentation to verify API usage.
- Confirm that the integration runs an application built with the SDK rather than the repository root itself.
- For an HTTP server, check that ModelContextProtocol.AspNetCore is referenced.
Use cases
Build MCP clients or servers in .NET applications.
Integrate MCP using hosting and dependency-injection extensions.
Build HTTP-based MCP servers with ASP.NET Core.
Develop MCP Apps with interactive interfaces or MCP Tasks with asynchronous status polling.
Supported clients
Supported clients have not been confirmed yet.