run-conformance-from-branch

Runs MCP conformance tests in the C# SDK against unpublished conformance branches from GitHub.

4.5k|796|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill run-conformance-from-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-conformance-from-branch
Source: https://github.com/modelcontextprotocol/csharp-sdk/tree/main/.github/skills/run-conformance-from-branch
Command: npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill run-conformance-from-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating C# SDK behavior against conformance changes normally requires waiting for the conformance package to be published to npm, which blocks early testing of pull requests and fork-based scenario changes.

Core Features & Use Cases

  • Branch-Based Installation: Installs the @modelcontextprotocol/conformance package directly from any GitHub branch, including forks, using npm with --no-save.
  • Targeted Test Execution: Runs client or server conformance tests via dotnet test filters against the AspNetCore test project.
  • Dependency Restoration: Restores pinned dependencies with npm ci after testing to keep the repo clean.
  • Use Case: A maintainer wants to validate a conformance PR before it ships to npm, so they install the branch version, run the conformance test suite, and report scenario results and new check IDs.

Quick Start

Run the C# SDK conformance tests against the conformance branch modelcontextprotocol/conformance#main and restore pinned dependencies afterward.

Frequently Asked Questions about run-conformance-from-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run MCP conformance tests against an unpublished branch?

Install the conformance package directly from GitHub using npm install --no-save @modelcontextprotocol/conformance@github:<owner>/conformance#<branch>, then run dotnet test with the appropriate client or server conformance filter.

How do I test a conformance fork branch in the C# SDK?

Use the fork owner in the GitHub install URL, for example npm install --no-save @modelcontextprotocol/conformance@github:myuser/conformance#sep-2350-check. Then run the conformance tests and restore pinned dependencies with npm ci afterward.

What tools are required to run C# SDK conformance tests?

You need npm, node, and the dotnet SDK installed. The workflow uses the repo's package.json and package-lock.json plus the tests/ModelContextProtocol.AspNetCore.Tests project.

How do I restore pinned dependencies after testing a conformance branch?

Run npm ci from the csharp-sdk repository root. This reinstalls the locked dependency versions from package-lock.json, undoing the temporary --no-save branch installation.

Why should I start from a clean git state before running conformance tests?

A clean git state prevents uncommitted local changes from being mixed with temporary dependency swaps. Commit or stash local changes first so the repo can be reliably restored to its pinned state afterward.