mcp

Build or consume Model Context Protocol (MCP) servers and clients in .NET using the official MCP C# SDK, including stdio, Streamable HTTP, tools, prompts, resources, and capability negotiation. USE FOR: .NET MCP servers or clients; stdio versus HTTP transport choices; tools, resources, prompts, completions, and capability negotiation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

Jump to install

Repository: managedcode/dotnet-skills
Last source activity: August 6, 2026 at 12:26
Detected SKILL.md language: English
Stars: 467
Forks: 35

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/managedcode/dotnet-skills --skill mcp

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

4 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

microsoft-agent-framework

Build .NET AI agents, harnesses, and multi-agent workflows with Microsoft Agent Framework using the right agent type, sessions, tools, workflows, hosting protocols, and enterprise guardrails. USE FOR: building or reviewing .NET code that uses Microsoft.Agents.*, Microsoft.Extensions.AI, AIAgent, HarnessAgent, AgentThread, AgentSession, or Agent Framework hosting packages; choosing agent, harness, workflow, and hosting shapes. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

2026-08-06

astro-developer

Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.

2026-08-06

configuring-opentelemetry-dotnet

Configure OpenTelemetry distributed tracing, metrics, and logging in ASP.NET Core using the .NET OpenTelemetry SDK. Use when adding observability, setting up OTLP exporters, creating custom metrics/spans, or troubleshooting distributed trace correlation.

2026-08-06

View all from this repository

name	mcp
description	Build or consume Model Context Protocol (MCP) servers and clients in .NET using the official MCP C# SDK, including stdio, Streamable HTTP, tools, prompts, resources, and capability negotiation. USE FOR: .NET MCP servers or clients; stdio versus HTTP transport choices; tools, resources, prompts, completions, and capability negotiation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility	Requires the official MCP C# SDK packages (`ModelContextProtocol.Core`, `ModelContextProtocol`, or `ModelContextProtocol.AspNetCore`) on .NET 8+; current guidance targets the v2.1 SDK and MCP 2026-07-28.

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.

Package	Choose when
`ModelContextProtocol.Core`	You only need a client or low-level server APIs and want the smallest dependency set.
`ModelContextProtocol`	You want the main SDK package with hosting, DI, attribute discovery, and stdio server support. Start here for most projects.
`ModelContextProtocol.AspNetCore`	You are hosting a remote MCP server in ASP.NET Core over HTTP. This includes the main package.

Transport	Use when	Notes
`StdioClientTransport` / `WithStdioServerTransport()`	The MCP server should run as a local child process.	Best for local tooling and editor/agent integrations.
`HttpClientTransport` + `HttpTransportMode.StreamableHttp`	The server is remote or should be reachable over HTTP.	Recommended HTTP transport; supports streaming and session resumption.
`HttpTransportMode.Sse`	You must connect to an older SSE-only server.	Legacy compatibility only; do not choose this for new servers.

Anti-pattern	Why it causes trouble	Better approach
Picking HTTP transport for a purely local child-process scenario	Adds unnecessary hosting, auth, and deployment surface	Use stdio for local/editor-hosted integrations
Treating SSE as the default remote transport	Locks new work to legacy behavior	Prefer Streamable HTTP and keep SSE only for backward compatibility
Writing tools without `[Description]` metadata	Hosts and models lose schema clarity	Describe tool purpose and parameters explicitly
Returning huge binary/text payloads from every tool call	Bloats context and slows hosts	Return focused content and move large data to resources
Logging to stdout on stdio servers	Corrupts the protocol stream	Send logs to stderr
Assuming prompts/resources/logging/completions exist	Breaks against partial implementations	Check negotiated capabilities first
Using filters for normal business logic	Makes handlers opaque and hard to reason about	Keep filters for cross-cutting policy, audit, or protocol plumbing

mcp

Install options

Review the source files

MCP C# SDK for .NET

Trigger On

Use This Skill Instead Of

MCP C# SDK for .NET

Trigger On

Use This Skill Instead Of

Documentation

References

Package Selection

Transport Selection

Current v2.1 Notes

Workflow

Anti-Patterns To Avoid

Deliver

Validate

mcp

Source facts

Install options

Review the source files

More from this repository

More from this repository

MCP C# SDK for .NET

Trigger On

Use This Skill Instead Of

MCP C# SDK for .NET

Trigger On

Use This Skill Instead Of

Documentation

References

Package Selection

Transport Selection

Current v2.1 Notes

Workflow

Anti-Patterns To Avoid

Deliver

Validate