mcp
mcp guides you through building or consuming Model Context Protocol servers and clients in .NET using the official C# SDK. It covers package selection, transport configuration (stdio for local processes, HTTP for remote endpoints), and capability negotiation patterns. Use this skill when you need protocol interoperability; reach for other tools if you only need model abstraction or agent orchestration without the MCP wire protocol.
mcp helps you build or consume Model Context Protocol servers and clients in .NET using the official C# SDK.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
mcp helps you build or consume Model Context Protocol servers and clients in .NET using the official C# SDK. mcp guides you through building or consuming Model Context Protocol servers and clients in .NET using the official C# SDK. It covers package selection, transport configuration (stdio for local processes, HTTP for remote endpoints), and capability negotiation patterns. Use this skill when you need protocol interoperability; reach for other tools if you only need model abstraction or agent orchestration without the MCP wire protocol.
Use it when
- mcp supports both transport modes.
- Yes.
Verify before relying
Read SKILL.md below before installing (4 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/mcp · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I build an MCP server in .NET?
mcp provides the official C# SDK for building Model Context Protocol servers. Start by adding the ModelContextProtocol.Core package, then instantiate a server, register your tools, resources, and prompts using the SDK's fluent API, and choose your transport: stdio for spawning as a child process or HTTP for remote endpoints. The SDK handles protocol negotiation and capability advertisement automatically.
What's the difference between stdio vs HTTP transport in MCP?
mcp supports both transport modes. Stdio transport runs your MCP server as a child process with bidirectional communication over standard streams—ideal for local, tightly-coupled deployments. HTTP transport exposes your server as a remote endpoint with streaming support, enabling distributed architectures and session resumption. Choose stdio for simplicity and HTTP when you need scalability or cross-machine connectivity.
Can I expose tools, resources, and prompts via MCP?
Yes. mcp's C# SDK lets you expose tools (callable functions), resources (data artifacts), and prompts (reusable instruction templates) through the Model Context Protocol. Register each capability type on your server instance, and mcp handles discovery and capability negotiation so clients can discover and invoke them according to their supported features.
How do I connect a .NET application to an MCP server?
mcp enables you to build MCP clients that discover and consume remote or local servers. Create an MCP client, connect it to your server's transport endpoint (stdio process or HTTP URL), perform capability negotiation, and integrate discovered tools into IChatClient workflows. The SDK abstracts transport details so your code works uniformly across deployment modes.
What does MCP capability negotiation and auth in C# involve?
mcp supports capability-aware flows where clients and servers exchange supported features during handshake. The SDK provides patterns for implementing authentication and authorization checks, negotiating which tools and resources are available based on client permissions, and handling capability mismatches gracefully. This ensures secure, interoperable protocol interactions.
Can I run an MCP server in ASP.NET Core over HTTP?
Yes. mcp supports HTTP transport for MCP servers deployed in ASP.NET Core. Map MCP protocol endpoints in your middleware, configure streaming for session resumption, and use the SDK's HTTP transport layer to handle incoming client connections. This approach scales better than stdio for multi-client scenarios and integrates cleanly with your existing ASP.NET infrastructure.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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
(truncated - see the full file via the links below)
File tree — 4 files
catalog/Libraries/MCP/skills/mcp/SKILL.md
catalog/Libraries/MCP/skills/mcp/manifest.json
catalog/Libraries/MCP/skills/mcp/references/patterns.md
catalog/Libraries/MCP/skills/mcp/references/security.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Build or consume MCP servers and clients in .NET using the official C# SDK”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Learn to develop Model Context Protocol servers across TypeScript, Python, and C# with support for tools, resources, and prompts. This guide covers Streamable HTTP transport configuration, OAuth authentication, and migration from deprecated SSE endpoints.
mcp-builder covers the essentials of building Model Context Protocol servers, from project structure and transport selection to tool and resource design. It walks through input validation, error handling, multimodal support, and configuration patterns for both local and remote deployments. Follow the included checklist to ensure your server is well-documented, secure, and ready for production use.
Learn to construct MCP servers using the Node/TypeScript SDK, implementing tools for model invocation, resources for data access, and prompt templates. This skill covers registration patterns, transport selection between stdio for local clients and Streamable HTTP for remote, and validation best practices with Zod.
Set up Model Context Protocol servers to give Claude and Codex access to databases, APIs, GitHub, and custom tools with fine-grained permission controls. Choose from official servers for PostgreSQL, SQLite, and popular platforms, or build custom TypeScript servers for internal integrations.
This skill guides you through building production-ready MCP servers using the mcp-use framework. Learn to scaffold projects with templates, define tools and resources, create reusable prompts, test locally with the Inspector UI, and deploy to mcp-use Cloud.
MCP Server Builder guides you through creating Model Context Protocol servers that extend Claude's capabilities with custom tools, resources, and prompts. The skill covers the full workflow from defining your server's purpose and choosing a transport layer through designing tool schemas, adding optional resources, and deploying to Claude Desktop or the API. It includes TypeScript project setup, basic server structure with request handlers, tool definition patterns with schema validation, and resource management examples.