mcp

# MCP C# SDK for .NET ## Trigger On - building or consuming MCP servers from a .NET application or library - choosing between stdio and HTTP transport for MCP - exposing tools, resources, prompts, completions, or logging to an MCP host - connecting a .NET app to an existing MCP server and passing discovered tools into `IChatClient` - bootstrapping a minimal MCP client/server from the `.NET AI` quickstarts or publishing a server to the MCP Registry - implementing capability-aware flows such as roots, sampling, elicitation, subscriptions, session resumption, or enterprise managed authorization ## Use This Skill Instead Of - Use `mcp` when **protocol interoperability** is the requirement. - Use `microsoft-extensions-ai` when you only need model/provider abstraction or local tool orchestration without the MCP wire protocol. - Use `microsoft-agent-framework` when the main problem is agent orchestration; combine it with `mcp` only when those agents must consume or expose MCP endpoints. - Use the `.NET AI` quickstarts for the very first vertical slice, then come back here to harden transport, capability negotiation, publishing, and host interoperability. ## Documentation - [MCP C# SDK overview](https://csharp.sdk.modelcontextprotocol.io/) - [Getting Started](https://csharp.sdk.modelcontextprotocol.io/concepts/getting-started.html) - [API reference](https://csharp.sdk.modelcontextprotocol.io/api/ModelContextProtocol.html) - [Conceptual docs](https://csharp.sdk.modelcontextproto...