Skip to main content
Glama

upgrade-pilot-mcp

English | Русский

MCP server that helps AI agents safely upgrade JavaScript / TypeScript projects — from dependency analysis to PR summary generation.

Supported packages

Languages & tooling: TypeScript, ESLint, Prettier, Babel, SWC Bundlers: Vite, Webpack, Rollup, esbuild, tsup, PostCSS, Sass Testing: Vitest, Jest, Mocha, Playwright, Cypress, Storybook, Supertest, MSW Frameworks: React, Next.js, Vue, Nuxt, Astro, SvelteKit, Remix, Angular, NestJS, Express, Fastify, Hono Data & state: Prisma, Drizzle ORM, TypeORM, Mongoose, Redux Toolkit, TanStack Query, Pinia, RxJS Networking: Axios, GraphQL, Socket.IO, Zod Infra & DX: Turbo, Nx, Husky, lint-staged, commitlint, Tailwind CSS, Lodash

Scoped families @nestjs/*, @storybook/*, @remix-run/*, @angular/* are recognized automatically.

Related MCP server: lurq

Tools

Analysis & planning

Tool

Purpose

analyze_project

Fingerprint the project: deps, configs, lockfile, stack

detect_upgrade_paths

Compute safe upgrade steps per package

find_breaking_changes

Surface version-aware migration guides and risk areas

scan_repo_for_deprecations

Find deprecated patterns in the codebase

generate_upgrade_plan

Build a phased upgrade plan

run_upgrade_pipeline

All-in-one: analyze → paths → breaking → scan → plan

Execution

Tool

Purpose

apply_safe_codemods

Run deterministic codemods (dry-run by default)

install_upgrade

Install specific package versions via npm/yarn/pnpm

check_compatibility

Verify peerDependency compatibility before installing

Validation & rollback

Tool

Purpose

validate_upgrade

Run type-check, lint, test, build

create_checkpoint

Tag current HEAD for safe rollback

restore_checkpoint

Hard-reset to a previous checkpoint

list_checkpoints

List all upgrade-pilot checkpoint tags

Reporting

Tool

Purpose

write_upgrade_pr_summary

Generate a reviewer-friendly markdown summary

Token-saving features

  • Compact output — 5 diagnostic tools accept outputFormat: "compact" (default) to strip verbose fields and return counts instead of arrays.

  • Analysis caching — validate_upgrade, generate_upgrade_plan, and write_upgrade_pr_summary reuse a cached analysis when available, eliminating redundant project scans.

  • Quiet validation — validate_upgrade accepts quietOnSuccess: true (default) to return a one-line summary when all checks pass.

  • Pipeline tool — run_upgrade_pipeline replaces 5 sequential calls with one, storing full artifacts as resources while returning only a compact summary.

Resources

Each URI returns the latest artifact from the current session:

URI

Content

upgrade://analysis/latest

Project analysis snapshot

upgrade://paths/latest

Upgrade path results

upgrade://breaking-changes/latest

Breaking change references

upgrade://findings/latest

Deprecation findings

upgrade://plan/latest

Upgrade plan

upgrade://pipeline/latest

Full pipeline result

upgrade://codemods/latest

Codemod results

upgrade://validation/latest

Validation results

upgrade://summary/latest

PR summary (markdown)

Prompts

  • plan_upgrade_route — walk the agent through a safe upgrade workflow

  • draft_upgrade_pr — turn artifacts into a PR description

Codemods

ID

Purpose

prisma-relation-mode

Add relationMode = "prisma" to Prisma schema

eslint-flat-config

Generate eslint.config.mjs FlatCompat bridge from legacy

tailwind-v4-import

Replace @tailwind directives with @import "tailwindcss"

Setup

npm install
npm run build

MCP client configuration

Recommended after publishing:

Use this when the package is consumed from npm. If you are inside this repository itself, prefer the local development config below.

{
  "mcpServers": {
    "upgrade-pilot": {
      "command": "npx",
      "args": ["-y", "upgrade-pilot-mcp@latest"]
    }
  }
}

Local development:

{
  "mcpServers": {
    "upgrade-pilot": {
      "command": "node",
      "args": ["path/to/upgrade-pilot-mcp/dist/server.js"]
    }
  }
}

Windows note: if a client does not resolve npx, use npx.cmd as the command.

Security

  • stdio transport only — no HTTP listener

  • All operations are read-only by default

  • Codemods require explicit mode: "apply"

  • install_upgrade runs the detected package manager (npm/yarn/pnpm install)

  • restore_checkpoint performs git reset --hard — destructive by design

  • Validation runs only local scripts from the target repo

  • No remote code execution


upgrade-pilot-mcp (RU)

English | Русский

MCP-сервер, помогающий AI-агентам безопасно обновлять JavaScript / TypeScript проекты — от анализа зависимостей до генерации описания PR.

Поддерживаемые пакеты

Языки и тулинг: TypeScript, ESLint, Prettier, Babel, SWC Сборщики: Vite, Webpack, Rollup, esbuild, tsup, PostCSS, Sass Тестирование: Vitest, Jest, Mocha, Playwright, Cypress, Storybook, Supertest, MSW Фреймворки: React, Next.js, Vue, Nuxt, Astro, SvelteKit, Remix, Angular, NestJS, Express, Fastify, Hono Данные и стейт: Prisma, Drizzle ORM, TypeORM, Mongoose, Redux Toolkit, TanStack Query, Pinia, RxJS Сеть: Axios, GraphQL, Socket.IO, Zod Инфра и DX: Turbo, Nx, Husky, lint-staged, commitlint, Tailwind CSS, Lodash

Scoped-семейства @nestjs/*, @storybook/*, @remix-run/*, @angular/* распознаются автоматически.

Инструменты

Анализ и планирование

Инструмент

Назначение

analyze_project

Отпечаток проекта: зависимости, конфиги, lockfile, стек

detect_upgrade_paths

Безопасные шаги обновления по каждому пакету

find_breaking_changes

Версионные migration guides и зоны риска

scan_repo_for_deprecations

Поиск устаревших паттернов в коде

generate_upgrade_plan

Пофазный план обновления

run_upgrade_pipeline

Всё-в-одном: анализ → пути → breaking → скан → план

Выполнение

Инструмент

Назначение

apply_safe_codemods

Детерминистические кодмоды (dry-run по умолчанию)

install_upgrade

Установка конкретных версий через npm/yarn/pnpm

check_compatibility

Проверка совместимости peerDependencies

Валидация и откат

Инструмент

Назначение

validate_upgrade

Запуск type-check, lint, тестов и build

create_checkpoint

Тег текущего HEAD для безопасного отката

restore_checkpoint

Hard-reset к предыдущему чекпоинту

list_checkpoints

Список всех чекпоинт-тегов upgrade-pilot

Отчётность

Инструмент

Назначение

write_upgrade_pr_summary

Markdown-описание для PR

Экономия токенов

  • Компактный вывод — 5 диагностических инструментов принимают outputFormat: "compact" (по умолчанию), убирая многословные поля и заменяя массивы на счётчики.

  • Кеширование анализа — validate_upgrade, generate_upgrade_plan и write_upgrade_pr_summary используют кешированный анализ, если он есть, устраняя повторные сканирования.

  • Тихая валидация — validate_upgrade принимает quietOnSuccess: true (по умолчанию) и возвращает однострочный итог, если все проверки пройдены.

  • Pipeline — run_upgrade_pipeline заменяет 5 последовательных вызовов одним, сохраняя полные артефакты в ресурсах и возвращая только компактный итог.

Ресурсы

Каждый URI возвращает последний артефакт текущей сессии:

URI

Содержимое

upgrade://analysis/latest

Снимок анализа проекта

upgrade://paths/latest

Пути обновления

upgrade://breaking-changes/latest

Breaking changes

upgrade://findings/latest

Найденные устаревшие паттерны

upgrade://plan/latest

План обновления

upgrade://pipeline/latest

Полный результат pipeline

upgrade://codemods/latest

Результаты кодмодов

upgrade://validation/latest

Результаты валидации

upgrade://summary/latest

Саммари для PR (markdown)

Промпты

  • plan_upgrade_route — проводит агента через безопасный процесс обновления

  • draft_upgrade_pr — превращает артефакты в описание PR

Кодмоды

ID

Назначение

prisma-relation-mode

Добавляет relationMode = "prisma" в схему Prisma

eslint-flat-config

Генерирует eslint.config.mjs FlatCompat-мост из legacy-конфигов

tailwind-v4-import

Заменяет директивы @tailwind на @import "tailwindcss"

Установка

npm install
npm run build

Конфигурация MCP-клиента

Рекомендуемый вариант после публикации:

Используй этот вариант, когда пакет ставится из npm. Если ты находишься внутри самого репозитория, лучше использовать локальную конфигурацию ниже.

{
  "mcpServers": {
    "upgrade-pilot": {
      "command": "npx",
      "args": ["-y", "upgrade-pilot-mcp@latest"]
    }
  }
}

Для локальной разработки:

{
  "mcpServers": {
    "upgrade-pilot": {
      "command": "node",
      "args": ["path/to/upgrade-pilot-mcp/dist/server.js"]
    }
  }
}

Примечание для Windows: если клиент не находит npx, укажи в command значение npx.cmd.

Безопасность

  • Только stdio transport — без HTTP

  • Все операции read-only по умолчанию

  • Кодмоды требуют явный mode: "apply"

  • install_upgrade запускает обнаруженный пакетный менеджер (npm/yarn/pnpm install)

  • restore_checkpoint выполняет git reset --hard — деструктивная операция

  • Валидация запускает только локальные скрипты целевого репозитория

  • Никакого удалённого выполнения кода

Available Tools

14 tools
analyze_projectAnalyze JS/TS projectB

Read package metadata, lockfiles, and config files to fingerprint the upgrade surface.

Inputs: rootPath, outputFormat, includeScripts.

apply_safe_codemodsApply safe codemodsC

Run deterministic, local codemods that are explicitly allowed by the v1 safety model.

Inputs: mode, rootPath, codemodIds.

check_compatibilityCheck peer dependency compatibilityA

Verify peerDependency compatibility for a set of packages before installing.

Inputs: packages (required).

create_checkpointCreate git checkpointB

Tag current HEAD so the upgrade can be rolled back if needed.

Inputs: label, rootPath.

detect_upgrade_pathsDetect upgrade pathsC

Compute constrained, package-aware upgrade steps for the supported route.

Inputs: targets, rootPath, outputFormat.

find_breaking_changesFind breaking changesD

Attach official migration references and curated risk areas to selected packages.

Inputs: targets, rootPath, outputFormat.

generate_upgrade_planGenerate upgrade planC

Turn dependency intelligence and repo findings into an ordered upgrade plan.

Inputs: targets, rootPath.

install_upgradeInstall package upgradesC

Install specific package versions using the detected package manager (npm/yarn/pnpm).

Inputs: packages (required), rootPath.

list_checkpointsList git checkpointsC

List all upgrade-pilot checkpoint tags in the repository.

Inputs: rootPath.

restore_checkpointRestore git checkpointC

Hard-reset to a previously created checkpoint tag.

Inputs: label (required), rootPath.

run_upgrade_pipelineRun full upgrade pipelineB

Run analyze → paths → breaking changes → deprecations → plan in a single call. Returns a compact summary to save tokens while storing all artifacts for later resource access.

Inputs: targets, rootPath, skipSteps.

scan_repo_for_deprecationsScan repository for deprecated patternsC

Find high-signal repo-level patterns that are known to complicate upgrades.

Inputs: targets, rootPath, maxFindings, outputFormat.

validate_upgradeValidate upgradeC

Execute type-check, lint, test, and build commands when they are available.

Inputs: include, rootPath, timeoutMs, outputFormat, +1 more.

write_upgrade_pr_summaryWrite upgrade PR summaryC

Generate a reviewer-friendly markdown summary of the planned upgrade route.

Inputs: targets, rootPath.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct phase or operation in the upgrade workflow (e.g., analysis, planning, codemods, validation, rollback). There is no overlap in purpose, and the descriptions clearly differentiate them.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., generate_*, analyze_*, detect_*, apply_*) with one exception: run_upgrade_pipeline vs. the more descriptive 'run' verbs elsewhere. Overall the pattern is clear and predictable.

    Tool Count4/5

    14 tools is a reasonable count for a specialized upgrade assistant. Each tool covers a needed step, and the set is not overly large or sparse for its domain.

    Completeness5/5

    The tool set provides end-to-end lifecycle coverage: project analysis, upgrade path detection, breaking changes, safe codemods, validation, installation, checkpoint/rollback, and PR summary. No obvious gaps in the upgrade workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides symbol-level dependency analysis and LLM-ready migration prompts for TypeScript/JavaScript projects, enabling AI editors to scan projects, analyze packages, and generate refactoring prompts.
      66 npm
      19
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to verify, compare, and safely upgrade npm packages by scoring packages from public signals and sandboxed co-installation, detecting breaking API surface changes, and rewriting code that upgrades break.
      36 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous AI agents and CI/CD runners to discover repository modules, scan outdated dependencies, fetch version histories, and apply verified dependency updates with major-version safety guardrails across polyglot monorepos.
      877 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.
      1
      MIT