Skip to main content
Glama
kdinisv

upgrade-pilot-mcp

by kdinisv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to upgrade-pilot-mcp

No user-submitted related servers found.

    Related Servers

    • dep-scope

      FlorianBruniaux
      A
      license
      Not graded
      quality
      A
      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.
      139
      19
      MIT

    • dependency-migration-mcp

      SolvoHQ
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.
      -

    • driftwatch-mcp

      dhughes6071
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.
      MIT

    • Programmatic

      DarkLordGeo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to perform structural code operations on TypeScript/TSX projects—finding symbols and references and renaming them semantically while preserving source.
      27
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    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 issues

    Resources