modelcontextprotocol/csharp-sdk

The official C# SDK for Model Context Protocol servers and clients. Maintained in collaboration with Microsoft.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 15th, 2026
Created on March 10th, 2025
Open Issues & Pull Requests: 181 (+0)
GitHub issues: Enabled
Number of forks: 807
Total Stargazers: 4,528 (+0)
Total Subscribers: 71 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 8
Closed in 7 days: 4
Avg open age: 230 days
Stale 30+ days: 86
Stale 90+ days: 0

Recent activity

Opened in 7 days: 6
Closed in 7 days: 3
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (248)
  • bug (235)
  • needs confirmation (88)
  • ready for work (76)
  • P2 (60)
  • P3 (52)
  • area-auth (45)
  • area-tests (19)

Detailed Description

The MCP C# SDK is an official SDK for implementing Model Context Protocol servers and clients in .NET applications.

The Model Context Protocol standardizes how applications provide context to large language models by enabling secure integration between LLMs and various data sources and tools. This SDK allows .NET developers to build both MCP clients that consume protocol services and MCP servers that expose capabilities to LLMs. The implementation is maintained in collaboration with Microsoft and provides multiple packages tailored to different use cases: a minimal Core package for projects needing only client or low-level server APIs, a main package with hosting and dependency injection support for typical server implementations, an AspNetCore package for HTTP-based servers, and extension packages for building interactive UI applications and handling long-running asynchronous tool invocations.

Developers building .NET applications that need to integrate with LLMs or expose tools and data sources through a standardized protocol should consider this tool. It suits projects ranging from simple client implementations to complex server deployments, with the package structure allowing teams to include only the dependencies they need. The AspNetCore integration makes it particularly well-suited for teams already working within the .NET ecosystem who want to expose MCP servers over HTTP. The extension packages for apps and tasks address specific patterns: interactive UI rendering within MCP hosts and asynchronous long-running operations with status polling.

The project maintains active collaboration with Microsoft and provides comprehensive documentation including getting started guides, API reference, and sample implementations. Development activity shows consistent attention to the protocol specification with support for cross-application access through identity assertion authorization grant flows.