- Home
- MCP servers
- UX Laws
UX Laws
- typescript
0
GitHub Stars
typescript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"agencia-tecnologica-multiverse-limitada-ux-ui-mcp": {
"command": "node",
"args": [
"C:/ruta/a/UX-UI-MCP/dist/index.js"
]
}
}
}You can analyze and audit UX interfaces across multiple platforms using a single MCP server. It automatically detects the target platform, applies platform-specific patterns, and provides a suite of analysis tools to evaluate how well a design adheres to UX laws and heuristics.
How to use
To use the MCP server, run it and connect with your MCP client. You can perform a full audit against all UX laws or target specific patterns for a given platform. The server will analyze the provided code and return actionable insights, checklists, and cross-platform comparisons to help you improve usability.
How to install
Prerequisites: Node.js (version 14.x or newer) and npm. Make sure Node is available in your environment before proceeding.
npm install
npm run build
Configuration and startup
You can configure the MCP server in your desktop client by adding the following MCP server entry. This runs the server locally using Node and the compiled index file.
{
"mcpServers": {
"ux_laws": {
"command": "node",
"args": ["C:/ruta/a/UX-UI-MCP/dist/index.js"]
}
}
}
Operational notes
The MCP server automatically detects the platform from the code you supply, or you can specify it directly. You gain access to per-platform patterns, a collection of 37 tools, and dedicated checklists for faster, more consistent UX improvements.
Security and maintenance
Keep your Node.js environment updated and review access controls for any MCP client connections. Regularly rebuild when dependencies change to ensure you are using the latest platform patterns and UX rules.
Troubleshooting
If the server fails to start, verify that Node is installed, the path to the compiled dist/index.js is correct, and that your client is configured to connect to the local stdio server as shown.
Available tools
analyze_fitts_law
Analyzes the Fitts's Law pattern by evaluating target sizes and distances to predict interaction efficiency.
analyze_hicks_law
Assesses decision complexity by evaluating the number of choices and required effort to reach an action.
analyze_jakobs_law
Measures familiarity and ease of use by checking common interaction patterns and conventions.
analyze_millers_law
Evaluates memory load by considering the number of items a user must retain (7±2 rule).
analyze_postels_law
Checks tolerance and robustness in input handling following Postel’s Law.
analyze_peak_end_rule
Analyzes user experience by focusing on the peak moments and the end of interactions.
analyze_aesthetic_usability
Assesses how aesthetic quality impacts perceived usability and effectiveness.
analyze_doherty_threshold
Evaluates response times to ensure interactions stay under optimal thresholds.
analyze_teslers_law
Measures irreducible complexity and the amount of information a user must process.
analyze_pareto_principle
Identifies 80/20 patterns to prioritize essential UI elements and interactions.
analyze_proximity_law
Examines grouping cues to improve visual harmony and comprehension.
analyze_common_region_law
Assesses grouping based on shared regions to reduce cognitive load.
analyze_pragnanz_law
Applies Gestalt principles to streamline perception and interpretation.
analyze_similarity_law
Evaluates similarity to convey consistent meaning and reduce confusion.
analyze_uniform_connectedness
Checks how evenly elements are connected visually to guide attention.
analyze_closure_law
Ensures incomplete shapes still convey a complete idea, improving interpretation.
analyze_common_fate_law
Assesses how related items share a common trajectory or outcome.
analyze_continuity_law
Analyzes how elements guide the eye along a smooth path.
analyze_figure_ground
Distinguishes foreground vs background to improve readability.
analyze_serial_position
Evaluates ordering effects, such as primacy and recency, on perception.
analyze_von_restorff
Detects anomaly effects where distinct items stand out and affect recall.
analyze_zeigarnik
Accounts for motivation differences when tasks are interrupted.
analyze_chunking
Assesses grouping of information into manageable chunks to reduce load.
analyze_cognitive_load
Measures overall mental effort required to process a UI task.
analyze_selective_attention
Evaluates how well the UI directs user focus to critical elements.
analyze_goal_gradient
Analyzes progress indicators and feedback to smooth user motivation.
analyze_occams_razor
Simplifies design choices to reduce unnecessary complexity.
analyze_parkinsons_law
Considers how latency affects user expectations and patience.
analyze_progressive_disclosure
Controls information exposure to manage complexity over time.
analyze_feedback_principle
Provides timely feedback to confirm user actions and outcomes.
ux_full_audit
Performs a comprehensive audit across all 30 UX laws for a given component.
ux_get_law_info
Retrieves detailed information for a specific UX law across platforms.
ux_list_laws
Lists all UX laws, with optional category filtering.
ux_checklist
Generates a platform-specific checklist for a component type.
ux_list_platforms
Lists all supported platforms with their detection patterns.
ux_detect_platform
Detects the platform based on provided code or file extension.
ux_compare_platforms
Compares how a law applies across multiple platforms.