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
      9 npm
      8
      MIT

    • My Ui MCP

      tony9020
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable IDEs to search 8,214 design-system components, retrieve exact source bundles and semantic tokens, and follow a copy-first handoff workflow with composition validation.
      6
      MIT

    • smart-figma-mcp

      drake-yuan
      F
      license
      B
      quality
      B
      maintenance
      Enables mapping Figma designs to a project's own component library — shadcn/ui, antd, mui, or Astryx — by resolving variants against authoritative component contracts instead of guessing. It compiles Figma nodes into code and then deterministically writes the resulting files into the codebase, cleaning node-id artifacts and updating exports.
      12
      9 npm
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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