---
title: "MCP Spec Migrator 2025-11-25 · MCP Spec 2025-11-25"
description: "MCP Spec 2025-11-25 migration toolkit. Detect, diff, compatibility-matrix, plan, check. Foundation pillar by StudioMeyer (MCP Factory). Helps you upgrade an"
canonical: "https://matthiasmeyer.tech/repos/mcp-spec-migrator-2511"
language: "en"
last_updated: "2026-08-21"
markdown_versions: ["https://matthiasmeyer.tech/repos/mcp-spec-migrator-2511.md", "https://matthiasmeyer.tech/de/repos/mcp-spec-migrator-2511.md", "https://matthiasmeyer.tech/es/repos/mcp-spec-migrator-2511.md"]
image: "https://matthiasmeyer.tech/api/og/repo/mcp-spec-migrator-2511?lang=en"
publisher: "Matthias Meyer, https://matthiasmeyer.tech (llms.txt: https://matthiasmeyer.tech/llms.txt)"
---

factory stable TypeScript

# MCP Spec Migrator 2025-11-25

MCP Spec 2025-11-25 migration toolkit

Detect, diff, compatibility-matrix, plan, check. Foundation pillar by StudioMeyer (MCP Factory). Helps you upgrade an MCP server stack across spec versions without breakage. 35/35 tests, MIT.

[View on GitHub →](https://github.com/studiomeyer-io/mcp-spec-migrator-2511)[npm](https://www.npmjs.com/package/mcp-spec-migrator)

## What it solves

Before you can migrate an MCP server you have to know which spec it currently targets, and that is rarely written down anywhere. Working it out by reading the code is possible and tedious, and getting it wrong means planning a migration from the wrong starting point.

## How it works

Four steps in one tool: it detects which spec a repository targets, computes the difference to the version you want to reach, writes that out as a migration plan in a markdown file, and afterwards verifies whether the plan was actually completed. It is read-only throughout and never writes a patch into your repository, so the plan is a document you own rather than a change you have to review.

## When to use it

Run the detection first on any server whose spec version you are unsure about, including one you inherited. The generated plan is also the document you hand to whoever does the work, which is worth more than the detection itself when the work is not yours.

## When not to use it

It plans and verifies, it does not change anything. If you want the mechanical rewrites applied for you, that is mcp-stateless-migrator, and if you want a line-by-line lint against the 2026-07-28 spec specifically, that is mcp-herald.

Stars

★ 0

installs

↓ 558

Clones (14d)

⊟ 33

Language

TypeScript

Updated

2026-08-21

## Install

```
npx -y mcp-spec-migrator
```

## Related repos

- MCP Stateless Migrator

    ← next-spec sibling of

    →

    https://matthiasmeyer.tech/repos/mcp-stateless-migrator

- MCP Protocol Conformance

    → version-bridge for

    →

    https://matthiasmeyer.tech/repos/mcp-protocol-conformance

## Sitemap

Every page of this site as Markdown: [sitemap](https://matthiasmeyer.tech/sitemap.md). Curated entry point: [llms.txt](https://matthiasmeyer.tech/llms.txt).