Skip to main content
Glama
MarwanDevSpace

mcp-claude-design-arabic

by MarwanDevSpace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-claude-design-arabic

No user-submitted related servers found.

    Related Servers

    • arabicfmt-mcp

      cc1a2b
      A
      license
      A
      quality
      A
      maintenance
      MCP server for correct Arabic formatting — currency, Hijri dates, number-to-words, RTL fixes and validation across all 22 Arab countries. Zero-dependency.
      17
      101 npm
      3
      MIT

    • v0-mcp-ts

      Conce-AI
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that bridges design and code by generating UI components, layouts, and themes from text prompts using v0.dev, with features like code refactoring and accessibility auditing.
      10 npm
      1
      MIT

    • Font MCP

      Microck
      F
      license
      Not graded
      quality
      C
      maintenance
      An expert design advisor MCP server that researches live discussions, scans project files, and automatically downloads font files for your project setup.
      9
      -

    • vertaaux-mcp

      VertaaUX
      A
      license
      A
      quality
      D
      maintenance
      MCP server for VertaaUX.ai — run UX & accessibility audits, generate fixes, and monitor quality from your LLM or IDE. 38 tools covering the full audit-to-fix lifecycle across 7 UX categories.
      29
      46 npm
      MIT

    • design-review

      davekim917
      F
      license
      Not graded
      quality
      B
      maintenance
      This MCP server renders UI design artifacts headlessly, runs deterministic linters, and manages stateful design review loops with an independent vision critic.
      -
    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 14 tools

    Disambiguation1/5

    Every unique tool has an exact duplicate with a different name but identical description (e.g., pipeline_design and run_full_design_pipeline). An agent cannot distinguish between them, leading to misselection and confusion. This is the worst possible overlap.

    Naming Consistency2/5

    Naming conventions are inconsistent: some tools use verb-first patterns (analyze_arabic_typography, generate_design_tokens) while others are noun-first (arabic_typography, design_tokens). The same functionality uses different naming styles (pipeline_design vs run_full_design_pipeline), making the API unpredictable.

    Tool Count4/5

    14 tools is within the expected range for a design pipeline server, but the count is inflated by exact duplicates. With only 7 unique tools, the effective surface is well-scoped, though the redundancy makes the actual count slightly higher than ideal.

    Completeness4/5

    The unique tools cover the core domain: pipeline execution, audits (visual, accessibility, typography), layout conversion, benchmark evaluation, design agents, and token generation. Minor gaps exist, such as standalone tools for individual pipeline stages, but the pipeline and agent tools provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources