Skip to main content
Glama
Forge-Space

@forgespace/ui-mcp

Official
by Forge-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @forgespace/ui-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-garendesign

      lyw405
      F
      license
      B
      quality
      D
      maintenance
      Enables AI-driven frontend component design and code generation from natural language requirements. Supports Vue, React, and Angular with intelligent component decomposition, API design, and complete project generation.
      4
      3
      -

    • ui-architect-mcp

      foduucom
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to generate production-ready, professional UI design systems and components from simple descriptions, with real images, animated components, and automated quality checks.
      16
      -

    • @21st-dev/magic

      mrbkrustamov
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-powered UI component generation from natural language descriptions, integrating with IDEs like Cursor, Windsurf, and VS Code.
      4
      16,000 npm
      ISC

    • figma-dev-tools

      qq1006492122
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables conversion of Figma designs into frontend code (React, Vue, HTML, etc.) with high fidelity, including design tokens, assets, and responsive layout. Integrates with AI editors via MCP for a seamless design-to-code workflow.
      124 npm
      1
      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

    B3/5.0

    Scored across 38 tools

    Disambiguation2/5

    Many tools have overlapping purposes, e.g., analyze_component_library, analyze_design_references, fetch_design_inspiration all extract design patterns; forge_assess, assess_legacy_codebase, forge_scan all assess code quality. Agents may struggle to select the correct tool.

    Naming Consistency2/5

    Tool names use inconsistent prefixes: analyze, assess, audit, fetch, figma, forge, generate, get, image_to, list, manage, payments, refine, scaffold, setup, submit, update, validate. No single verb_noun pattern is followed throughout.

    Tool Count2/5

    38 tools is excessive for a UI-focused server. Many tools could be consolidated (e.g., multiple generate_* and forge_* tools) or split into separate servers. The scope seems too broad.

    Completeness3/5

    Covers analysis, generation, design, accessibility, migration, Figma, project context, and feedback, but lacks tools for deployment, user management, project creation, and design token CRUD. The payments_refund stub is an odd inclusion.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources