MCP Stateless Migrator
Migrate MCP servers to the 2026-07-28 stateless spec
Scan, diff, patch, and verify an MCP server stack across the 2025-11-25 to 2026-07-28 RC spec jump. Eight detection rules, AST rewrite via ts-morph, CLI-first. Foundation pillar by StudioMeyer (MCP Factory). TypeScript, MIT.
What it solves
The MCP release candidate of 2026-07-28 moved a lot at once: a stateless core, headers that became mandatory, deprecated features, an error code that shifted, hardened OAuth and changed endpoint shapes. Reading the spec and finding all of it by hand in a TypeScript codebase is the part nobody has time for.
How it works
It scans a server codebase for incompatibilities with the new spec and applies safe rewrites to the syntax tree where the change is mechanical. Detection rules carry the spec revision they were written against and cite the canonical SEP files, so a finding points at the document that justifies it rather than at an opinion. Every command is marked read-only or destructive, so you can see before you run it whether it touches your files.
When to use it
It is aimed at maintainers of TypeScript and JavaScript servers, which is the largest group of SDK users. Run the scan first to see the size of the job, then let it rewrite what is mechanical and do the rest by hand.
When not to use it
It is at version 0.1 and pre-final: the rules target the release candidate, not the finished spec, and the next version is meant to revalidate against the final SDK release. It also only speaks TypeScript and JavaScript, and it needs Node 20 or newer. For the read-only view of the same migration, mcp-herald lints without rewriting anything.
Stars
★ 0
installs
↓ 516
Clones (14d)
⊟ 57
Language
TypeScript
Updated
2026-08-21
Install
npx -y mcp-stateless-migrator