Skip to main content
Glama
Alvi97

angular-signal-forms-migration-mcp

by Alvi97

Related Servers

Alternatives to angular-signal-forms-migration-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      66 npm
      19
      MIT
    • 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 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to navigate and edit TypeScript/JavaScript source by named declarations, reading symbols, imports, diagnostics, and replacing code via the TypeScript AST.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to apply Martin Fowler's 71+ refactoring patterns to codebases through a pluggable, language-agnostic architecture. Supports previewing and applying refactorings, analyzing code smells, and inspecting code structure with safe-by-default operations.
      5
      25 PyPI
      5
      MIT
    • 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
      35 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct in purpose: discovery, complexity analysis, report generation, recipe lookup, upgrade planning, and verification. The only potential overlap is between find_form_candidates, analyze_migration_complexity, and get_migration_report, but their distinct output shape (raw findings vs. summary vs. combined report) keeps them distinguishable.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: get_*, find_*, analyze_*, verify_*. The verbs and nouns are explicit and predictable, so an agent can infer tool behavior from the name.

    Tool Count5/5

    Six tools is well-scoped for a migration-assist server. Each tool covers a necessary part of the migration workflow—candidate discovery, recipe lookup, complexity analysis, report generation, upgrade planning, and post-migration verification—without redundancy or bloat.

    Completeness4/5

    The tool surface covers the full lifecycle of the migration assistance: analyzing the existing code, obtaining recipes, generating reports, planning version upgrades, and verifying the migrated result. It lacks a tool that applies the migration automatically, but the server explicitly positions itself as read-only and focuses on verification rather than execution.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues