Skip to main content
Glama
dchavezp

design-os-migration-mcp

by dchavezp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to design-os-migration-mcp

No user-submitted related servers found.

    Related Servers

    • Design-Code Registry MCP

      mrasadi
      A
      license
      A
      quality
      C
      maintenance
      Maps design components, tokens, and patterns to their code implementations, providing AI coding agents with exact-match resolution across any design tool and framework. Enables agents to reliably discover and reuse existing components across React, Vue, Flutter, SwiftUI, and more.
      20
      MIT

    • figma-spec-mcp

      zaferdace
      A
      license
      A
      quality
      C
      maintenance
      Bridge Figma designs to any platform with structured specs for Unity, React, Flutter, SwiftUI, and more, including layout audit, design tokens, and accessibility checks.
      19
      19 npm
      8
      MIT

    • Mimic AI

      miapre
      A
      license
      A
      quality
      B
      maintenance
      Transforms HTML into Figma designs using only the user’s design system, ensuring correct component usage or safe fallback to primitives, while continuously learning from each build to improve mapping accuracy and consistency.
      26
      35 npm
      13
      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.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: analyzing target project, building migration context, listing export sections, reading components/files from export, reading entire package, and reading target docs. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., analyze_target_project, read_component, get_migration_context). The naming is predictable and clear.

    Tool Count5/5

    7 tools is well-scoped for a migration analysis server. It covers the necessary operations without being excessive or insufficient.

    Completeness4/5

    The tool set covers analysis of both source and target, reading various granularities of the export package, and generating migration context. A minor gap is the lack of a tool to apply changes or generate migration scripts, but the set is complete for analysis purposes.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources