MCP 2026-07-28 Migration + Compliance Check (TypeScript)
Upgrading the SDK alone changes nothing on the wire.
$5
Works with the AI Agents you already use
MCP 2026-07-28 Migration + Compliance Check (TypeScript)
Example session with this skill installed
Migrate my TypeScript MCP server to the MCP 2026-07-28 spec without breaking clients still on the 2025 handshake, then run the compliance checker against it and report pass/fail per requirement.
- Read your context and instructions
- Compiled the mcp 2026-07-28 migration
Summary
The agent follows the skill workflow to move the server to the stateless MCP 2026-07-28 spec while keeping 2025-handshake clients working, then runs the zero-dependency checker (scripts/check-compliance.mjs) against your real server.
What you get
- A baseline checker run before any changes
- The migration applied to your server, step by step
- A final checker run reporting pass/fail per requirement, each with its spec link
Next steps
- Review the checker report and fix any failing requirement
- Re-run the checker (its exit code works in CI)
Connects securely to your tools. The creator never sees your data.
About this skill
Long description
MCP 2026-07-28 is the biggest breaking revision since launch. It removes:
- the
initializehandshake andMcp-Session-Id - the GET stream and
ping
It also requires:
server/discoverresultTypeon every result, andttlMs/cacheScopeon list resultsMCP-Protocol-Version/Mcp-Method/Mcp-Nameheaders
At the same time, most MCP hosts still speak only the old protocol. Upgrading the SDK alone changes nothing on the wire. A hand-rolled server that misses one field can show no tools at all in Claude Code (its own changelog, 2.1.302).
This skill gives your coding agent:
- A 10-step workflow: baseline check, inventory, SDK v1→v2 codemod and its gaps, switch to
createMcpHandler/serveStdio, replace session state with handles, MRTR instead of server→client requests, the other changes, auth, verify, report. - A reference for every change in the revision, each with its official spec or SDK URL. A section lists what the spec leaves unclear, so your agent doesn't guess.
- Dual-era recipes, so one endpoint serves 2025 and 2026 clients, plus routing for a sessionful legacy deployment you can't drop yet.
- Auth changes for resource servers and clients: RFC 9207
iss, issuer-bound credentials, CIMD over DCR, and the v2OAuthErrortrap that turns invalid tokens into HTTP 500. - A client-support table where every row has a date and a source, marked primary, secondary or unconfirmed (checked 2026-10-21).
- 17 common pitfalls.
check-compliance.mjs, a black-box checker with no install, for HTTP (27 checks) and stdio (17 checks). It covers discover, versions,-32022, headers/-32020,resultType, cache fields,-32602, removedping, 404 for unknown methods, sessions, GET → 405, and legacy-client support. Its exit code works for CI.
What's been tested (honest)
Tested on 2026-10-21 on Linux with Node 20.19, @modelcontextprotocol/server 2.3.1 and @modelcontextprotocol/sdk 1.32.1:
-
We built a small old-spec server: SDK v1, sessionful Streamable HTTP plus stdio, with state keyed by session. We migrated it by following only the skill.
-
Compliance checker results:
Transport Before After HTTP FAIL (no server/discover), legacy clients OK27/27 PASS, including legacy-client checks stdio FAIL 17/17 PASS -
9 automated tests pass:
- before and after checker runs on both transports
- the checker catching 8 deliberate bugs in a hand-rolled "2026" server
- real SDK clients against the migrated server: a v2 client in auto mode negotiates the modern era over HTTP and stdio, and the default v2 client and the v1.32.1 client still work over HTTP and stdio
- a session-free handle flow across stateless calls
Not tested:
- OAuth/auth flows (the checker doesn't check auth)
- MRTR/elicitation,
subscriptions/listen, per-request log levels,x-mcp-header, tasks - Origin validation by the checker
- Express/Hono/Fastify/Next/Workers mounts (only plain
node:http) - sessionful legacy routing with
isLegacyRequest - any real host app (Claude Code, Cursor, VS Code)
- non-SDK servers beyond our one synthetic broken server
The checker's expected error for removed methods (-32601) is our reading of the spec, matching the SDK. It isn't spelled out in the spec text. Several client-support rows are secondary or unconfirmed, and they're labelled that way.
What's included
SKILL.md, scripts/check-compliance.mjs, scripts/check-sources.mjs, references/ (spec-changes, sdk-v2, dual-era, auth, client-support, pitfalls, sources), REFRESH.md, CHANGELOG.md, VERSION.md, README.md.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
Requires Node.js 20+ for the v2 SDK. Not tested: OAuth/auth flows, MRTR/elicitation, Express/Hono/Fastify/Next/Workers mounts (only plain node:http), or any real host app (Claude Code, Cursor, VS Code). The checker does not check auth.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 26 days ago
- Software
- Session Id MCPMethod MCP
Node.js@modelcontextprotocol/codemodX Header MCPProtocol Version MCPName MCPParam MCPStateless Migration Guide MCP
Git