ux

The ux MCP server delivers a comprehensive suite of UX best practices and patterns as MCP resources. It exposes tools for accessibility checks, usability reviews, UI pattern recommendations, component examples, design system auditing, color and typography guidance, performance and SEO optimization, internationalization patterns, animation guidance, and advanced UX analytics. You can interact with these capabilities via the MCP client ecosystem or by running the server locally and using the built-in tools to analyze, generate, and validate UX artifacts. Whether you're building accessible components, validating contrast ratios, or selecting appropriate UI patterns for a given use case, the ux MCP server provides structured, machine-readable outputs to integrate into CI pipelines or design tooling. Tools cover core analysis (e.g., analyze_accessibility, review_usability, check_contrast), design and content support (generate_color_palette, generate_typography_scale, suggest_microcopy), testing and validation (generate_accessibility_report, calculate_ux_metrics, detect_dark_patterns), and UI generation (generate_wireframe, suggest_microinteraction).

Prerequisites:

• Node.js and npm installed on your system
• Optional: Git for cloning from source

Install from npm (recommended):

npm install -g @elsahafy/ux-mcp-server

Run with npx (no installation required):

npx @elsahafy/ux-mcp-server

From source:

git clone https://github.com/elsahafy/ux-mcp-server.git
cd ux-mcp-server
npm install
npm run build

Usage (local development):

• Start the server after build (if using from source):

node dist/index.js

Adapt the path in mcp_config accordingly to point to dist/index.js.

Tips:

• If you deploy behind a reverse proxy, ensure long-running MCP processes have appropriate timeout settings.
• Configure environment-specific settings via the mcpServers.env section if your deployment uses distinct environments (e.g., development, staging, production).
• Common issues: missing dependencies after cloning from source; run npm install and npm run build to generate dist/index.js. When using npx or npm globally, verify your PATH includes the npm global bin.
• The server supports integration with Claude Desktop, Cursor IDE, Continue.dev, Cline, and other MCP clients via the standard mcpServers configuration. Ensure the client configuration references the correct command and path for your deployment.
• For debugging, run in a verbose mode if available in your build to capture tool outputs like accessibility reports and pattern recommendations.