mcp-migration-auditorlisted

Use this skill when the user wants to audit my MCP setup, check MCP compatibility, asks will my MCP servers break, mentions MCP spec migration, wants an MCP 2026 spec check, or says scan mcp config — also on any readiness question about the MCP 2026-07-28 specification (stateless transport, removed Mcp-Session-Id, deprecated roots/sampling/logging, experimental Tasks migration, OAuth hardening). Locates MCP configs (.mcp.json, claude_desktop_config.json, mcp.json, settings files) or accepts a pasted one, checks each server against rules verified from the official MCP blog and spec changelog, and outputs a per-server BREAKS/DEGRADED/SAFE table naming the triggering rule and specific fix, plus a prioritized migration checklist against the 2026-07-28 final date. Stdio-only local setups get an honest all-clear. Do NOT use for context-window cost audits of MCP connectors (cli-over-mcp-auditor's job), for debugging a broken MCP connection, or for installing new servers.
Abhillashjadhav/AI-PM-essential-skills · ★ 2 · AI & Automation · score 58

Install: claude install-skill Abhillashjadhav/AI-PM-essential-skills

# MCP Migration Auditor Scan MCP server configs against the verified breaking changes in the MCP **2026-07-28** specification and report exactly which servers break, which degrade, and which are safe — with the rule and official source behind every verdict. **The clock:** the release candidate locked May 21, 2026; the final specification ships **July 28, 2026**. Every rule below comes from the official announcement and spec changelog — full quotes and URLs in `references/spec-changes.md`. If a check isn't in that file, this skill doesn't make it. ## Step 1 — Locate configs Search the project for MCP configs, in this order: `.mcp.json`, `mcp.json`, `claude_desktop_config.json`, `mcpServers` blocks inside `.claude/settings.json` / `.claude/settings.local.json` / other settings files. If none found, ask the user to paste one — never audit an imagined config. ## Step 2 — Classify transport per server - `command`-based entries → **stdio/local**. Per the official announcement, stdio and local transports "operate independently of Streamable HTTP statelessness requirements and session infrastructure changes" — these start at SAFE. - `url`-based entries (HTTP / Streamable HTTP / SSE) → remote. These get the full rule pass. ## Step 3 — Apply the verified rules | Rule | Evidence to look for | Verdict | Source | |---|---|---|---| | **R1 — Protocol session dependency** | `Mcp-Session-Id` in headers, session-affinity/sticky-session settings, session-store references for an MCP endp