Skip to main content
Glama
gapra

@gapra/nuxt-migration-mcp

by gapra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @gapra/nuxt-migration-mcp

No user-submitted related servers found.

    Related Servers

    • HeroUI Migration MCP

      sctg-development
      A
      license
      B
      quality
      D
      maintenance
      Assists in migrating HeroUI v2 and NextUI projects to HeroUI v3 beta through automated project scanning, file analysis, and guided code rewrites. It provides specialized tools for auditing Tailwind configurations and comparing component changes using an integrated documentation corpus.
      6
      15
      AGPL 3.0

    • vitest-migrator-mcp

      Manvi1203
      F
      license
      A
      quality
      B
      maintenance
      Enables automated migration of JavaScript/TypeScript packages from legacy test runners like Karma, Webpack, and Mocha to Vitest, including AST codemods, multi-project test scaffolding, and self-learning diagnostics for resolving runtime errors.
      7
      -

    • upgrade-pilot-mcp

      kdinisv
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
      14
      14 npm
      MIT

    • 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.
      64 npm
      19
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are mostly distinct, but the comprehensive audit_nuxt_migration overlaps with specific audits like audit_async_data. However, descriptions clarify their scope, so confusion is minimal.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (audit_*, generate_*, configure_migration, etc.), making naming predictable and clear.

    Tool Count5/5

    23 tools cover the migration lifecycle thoroughly without being excessive. Each tool serves a clear purpose in auditing, generating, or managing the migration process.

    Completeness4/5

    The tool surface covers the core migration workflow (audit, generate, write, summary), but lacks verification or rollback tools. Minor gaps that agents can work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources