Skip to main content
Glama
MarwanDevSpace

mcp-claude-design-arabic

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pipeline_designC

Executes the unified multi-agent design pipeline (Brief Inference -> Art Direction -> RTL & BiDi Forms -> Arabic Typography -> Micro-Interactions -> Anti-Slop Audit -> Pre-Flight Checklist -> Benchmark) to generate clean, production-ready Arabic/Bilingual UI code.

run_full_design_pipelineB

Executes the unified multi-agent design pipeline (Brief Inference -> Art Direction -> RTL & BiDi Forms -> Arabic Typography -> Micro-Interactions -> Anti-Slop Audit -> Pre-Flight Checklist -> Benchmark) to generate clean, production-ready Arabic/Bilingual UI code.

anti_slop_auditA

Audits UI code for anti-AI-slop violations, em-dash bans, rounded left-border cards, and fake metrics.

arabic_typographyB

Audits an Arabic or bilingual text snippet for optical alignment, font pairing, line-height compensation, and ligature integrity.

analyze_arabic_typographyA

Audits an Arabic or bilingual text snippet for optical alignment, font pairing, line-height compensation, and ligature integrity.

rtl_layout_matrixB

Converts legacy physical CSS/Tailwind/Flutter component code into modern bidirectional (RTL/LTR) logical components with directional icon flip and Form BiDi rules.

generate_rtl_ltr_layout_matrixB

Converts legacy physical CSS/Tailwind/Flutter component code into modern bidirectional (RTL/LTR) logical components with directional icon flip and Form BiDi rules.

evaluate_design_benchmarkA

Evaluates UI code, CSS, or Tailwind markup against Level-5 Claude Design standards, returning overall score, sub-scores, strengths, and actionable visual polish recommendations.

invoke_design_agentA

Dispatches design challenges to specialized adaptive AI design agents (ArabicArtDirector, RTLArchitect, MicroInteractionEngineer, BilingualDesignStrategist, CognitiveUXAuditor) to get deep design critique, strategic guidance, and code optimizations.

invoke_interactive_design_agentB

Dispatches design challenges to specialized adaptive AI design agents (ArabicArtDirector, RTLArchitect, MicroInteractionEngineer, BilingualDesignStrategist, CognitiveUXAuditor) to get deep design critique, strategic guidance, and code optimizations.

design_tokensC

Generates ultra-premium Claude Level-5 design tokens (OKLCH color palettes, semantic layers, glassmorphism shadows, motion physics, Arabic typography scales) for Tailwind v4, CSS, JSON, or Flutter.

generate_claude_design_tokensB

Generates ultra-premium Claude Level-5 design tokens (OKLCH color palettes, semantic layers, glassmorphism shadows, motion physics, Arabic typography scales) for Tailwind v4, CSS, JSON, or Flutter.

accessibility_auditB

Audits HTML/JSX code markup for Arabic screen reader compatibility (dir="rtl", lang="ar"), BiDi text isolation, touch targets (24px/44px), focus rings, and WCAG 2.2 AA compliance.

audit_bilingual_accessibilityA

Audits HTML/JSX code markup for Arabic screen reader compatibility (dir="rtl", lang="ar"), BiDi text isolation, touch targets (24px/44px), focus rings, and WCAG 2.2 AA compliance.

Prompts

Interactive templates invoked by user choice

NameDescription
arabic_ui_masterpieceGenerates a prompt instructions package to guide any AI model in crafting Level-5 Claude visual masterpiece UIs tailored for Arabic/Bilingual apps.
creative_direction_briefGenerates a Creative Director Brief (Step 0) defining the 1-line Design Read, 3-dial taste values (Variance, Motion, Density), and anti-patterns before UI code generation.
anti_slop_auditGenerates a comprehensive Anti-AI-Slop audit prompt to check any UI code snippet for the 7 cardinal sins, em-dash violations, and soft tells.
pre_flight_checklistGenerates a 20-point mechanical pre-flight audit checklist to verify logical CSS properties, Arabic typography ratios, and BiDi form rules before publishing.
rtl_layout_conversionGenerates a step-by-step conversion prompt to refactor legacy LTR UI code into clean, logical RTL/LTR code.
design_system_arabic_briefGenerates a complete Arabic Design System specification brief with typography rules, color tokens, and spatial grids.

Resources

Contextual data attached and managed by the client

NameDescription
قواعد وحرفية الاتجاهات وتداخل النصوص (RTL & BiDi Craft Rules)Comprehensive directional craft rules: logical property mappings, form BiDi rules, icon mirroring lists, and native mobile parity.
قواعد منع التصميم السطحي والذكاء الاصطناعي (Anti-AI-Slop Rules)The 7 cardinal sins, soft tells, polish tells, and mechanical pre-flight checks to ensure human-grade design quality.
معدّلات الذوق والتصميم الذكي (Design Taste Dials System)The 3-dial system (Variance, Motion, Density), brief inference protocol, and design system selection matrix.
دليل الطباعة وتنسيق الخطوط العربية (Arabic Typography Guide)Comprehensive guidelines on font pairing, line-height compensation, baseline offsets, and diacritic handling for Arabic UI design.
قواعد التحويل ثنائي الاتجاه (RTL/LTR Mirroring Engine)Logical property mappings, flexbox/grid flips, icon rotation rules, and bidirectional text isolation.
معايير جودة التصميم الفاخر (Claude Level-5 Design Standards)Criteria for visual depth, glassmorphism layers, OKLCH color palettes, dynamic shadows, and micro-interactions.
دليل وكلاء التصميم التفاعليين (Interactive Adaptive Agents)Catalog of dynamic AI design agent roles, cognitive loops, and domain specializations.

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