MCP 2026 Migration
Migrate MCP servers, gateways, and clients to the 2026-07-28 specification: stateless request-response core (no initialize handshake, no Mcp-Session-Id, version/capabilities in _meta), required Mcp-Method/Mcp-Name headers, Multi Round-Trip Requests replacing server-initiated elicitation/sampling/roots, cacheable list results (ttlMs/cacheScope), CIMD auth over deprecated DCR, the extensions framework (Tasks, Apps, Skills over MCP), and the 12-month deprecation offramp for Roots/Sampling/Logging and HTTP+SSE. Trigger when upgrading any MCP implementation from protocol 2025-11-25 or earlier, writ
Install
npx skills add Archive228/lab-skills --skill mcp-2026-migrationgit clone --depth 1 https://github.com/Archive228/lab-skills.git /tmp/lab-skills
mkdir -p ~/.claude/skills
cp -r /tmp/lab-skills/skills/mcp-2026-migration ~/.claude/skills/mcp-2026-migrationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# MCP 2026-07-28 Migration (Stateless Core, MRTR, CIMD) This skill is an operating procedure for moving MCP servers, gateways, and clients from protocol 2025-11-25 (or earlier) to 2026-07-28 — which the maintainers call MCP's most important release since remote MCP first launched. It gives you the exact headers, `_meta` keys, result fields, error codes, and deprecation offramps from the official spec and the maintainers' deep-dive, plus a per-role migration checklist. ## When to use - Upgrading an existing MCP server, client, or SDK integration to protocol version `2026-07-28`. - Writing any NEW MCP implementation (start on the new patterns; do not adopt deprecated features). - Configuring gateways, load balancers, rate limiters, or WAFs in front of MCP servers. - Debugging `UnsupportedProtocolVersion` (-32022), `HeaderMismatch` (-32020), or session-related breakage after an SDK upgrade — the blog notes the migration cost lands hardest on developers who depended on session identifiers. Do NOT use when the deployment is deliberately pinned to 2025-11-25 or earlier with no upgrade planned, or for OAuth work unrelated to MCP. Do not use it to justify ripping out deprecated features immediately — Roots, Sampling, and Logging keep working for at least twelve months under the formal deprecation policy. ## Rules ### Stateless core
Details
- Skill name
mcp-2026-migration- Repository
- Archive228/lab-skills
- Path
skills/mcp-2026-migration/SKILL.md- License
- MIT
- Repo updated
- 12 August 2026
FAQ
What does the MCP 2026 Migration skill do?
Migrate MCP servers, gateways, and clients to the 2026-07-28 specification: stateless request-response core (no initialize handshake, no Mcp-Session-Id, version/capabilities in _meta), required Mcp-Method/Mcp-Name headers, Multi Round-Trip Requests replacing server-initiated elicitation/sampling/roots, cacheable list results (ttlMs/cacheScope), CIMD auth over deprecated DCR, the extensions framework (Tasks, Apps, Skills over MCP), and the 12-month deprecation offramp for Roots/Sampling/Logging and HTTP+SSE. Trigger when upgrading any MCP implementation from protocol 2025-11-25 or earlier, writ
How do I install the MCP 2026 Migration skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Archive228/lab-skills --skill mcp-2026-migration. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is MCP 2026 Migration popular?
It lives in Archive228/lab-skills, which has 10 GitHub stars and 2 forks.
Related skills
Agent Design Fundamentals
10Archive228/lab-skills
Decision rules for whether to build an LLM agent and how to architect it, distilled from OpenAI's "A Practical Guide to Building Agents": build/no-build criteria, model selection, tool design, single-agent vs multi-agent orchestration (manager pattern vs decentralized handoffs), layered guardrails, and human-in-the-loop triggers. Use when designing, reviewing, or refactoring an agent system — before choosing an architecture, adding more agents, defining tools, or shipping an agent to production without guardrails.
Agent Evals
10Archive228/lab-skills
Build and maintain evaluation suites for AI agents: bootstrap 20-50 tasks from real failures, pick code-based vs model-based vs human graders by agent architecture (coding, conversational, research, computer-use), write unambiguous tasks with reference solutions, and keep suites alive via ownership and transcript reading. Use when creating evals from zero, adding graders or eval cases, debugging suspicious eval scores, or deciding pass@k vs pass^k metrics for an agent product.
Agent Failure Preflight
10Archive228/lab-skills
Pre-deployment failure-mode gate for agentic AI systems, distilled from Microsoft AI Red Team's Taxonomy of Failure Modes in Agentic AI Systems v2.0 (grounded in 12 months of red-team engagements). Run it before shipping or materially changing an agent — adding tools/MCP servers/plugins, enabling persistent memory, adding sub-agents or orchestration, enabling computer use, or expanding permissions — to verify concrete controls against memory poisoning, HitL bypass, goal hijacking, supply-chain compromise, session context contamination, capability disclosure, and multi-agent cascade failures.
MCP Code Execution
10Archive228/lab-skills
Cut agent token consumption by calling MCP servers through generated code instead of direct tool invocations: present tools as typed wrapper files on a filesystem, discover them progressively, and keep intermediate data in the execution environment (Anthropic measured 150,000 → 2,000 tokens, a 98.7% saving). Trigger when an agent connects to many MCP servers/tools, when tool definitions eat a large share of the context window before work starts, when workflows pipe large intermediate results (transcripts, spreadsheets) between tools, or when sensitive data should not enter model context.
Long Running Harness
10Archive228/lab-skills
Operating procedure for agent work that spans many context windows: split the run into a one-time initializer session (init.sh, feature_list.json, claude-progress.txt, initial git commit) and repeated coding sessions that each ship exactly one feature, verify it end-to-end via browser automation, and leave the repo in clean committed state. Trigger whenever a build will outlive a single context window (multi-hour/multi-day autonomous coding, session handoffs, resuming a scaffolded project), or when designing a harness/loop for such work.
Minimal Patch with Subagents
9kargnas/skills
Minimal patching workflow that debates fix options across parallel independent subagents and applies the smallest safe diff. Use only when you want risk-free code, and to code real minimal that only needs to fix the issue.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.