vibecraft-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UI_UX_MCP_API_KEY | Yes | Your API key for VibeCraft MCP |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_system_performanceA | Audits backend API code, database queries, network waterfalls, and frontend rendering for performance bottlenecks, N+1 queries, un-transactional mutations, IDOR security issues, and slow OFFSET pagination. |
| get_layout_blueprintA | Retrieves Nielsen Norman Group (NN/g) Information Architecture (IA) macro page layout scaffolds and Design System Task Patterns (AI Co-pilot generation, Destructive actions, SaaS Dashboards, Settings, Onboarding, Pricing). |
| get_ux_guidelinesC | Queries UX Intelligence Rules: AI-Slop Prevention Matrix, Source of Truth Hierarchy, Frank Chimero's TSOD 3 Levers, Design System 13-State Matrix, Apple HIG, Laws of UX, Nir Eyal's Hook Model, IxDF Foundations, NN/g IA, and transitions.dev rules. |
| audit_ux_complianceB | Audits UI code or prompt specs against AI-slop prevention matrix, competing primary CTAs, TSOD levers, Design System 13-state matrix, Laws of UX, Apple HIG, Hook Model habit loops, IxDF principles, hardcoded hex colors, and icon accessibility. |
| search_ui_componentsB | Searches 21st.dev & curated high-craft UI component registry by keyword, category, or tag. |
| get_component_codeA | Retrieves complete React, Tailwind, Framer Motion source code, demo, and dependencies for a component. Supports fallback live fetching. |
| get_design_tokensA | Provides HSL CSS color variables, globals.css setup, typography scales, spatial grid, icon stroke rules, shadows, and spring animation parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools are mostly distinct: audits target performance vs UX compliance, and get_component_code/search_ui_components form a clear pair. The only real ambiguity is between get_layout_blueprint and get_ux_guidelines, since both reference NN/g IA and design guidance.
All seven tools follow the same lowercase snake_case verb_noun convention: audit_, get_, search_. No mixed styles or vague generic verbs.
Seven tools is well-scoped for a design/UX assistant: guidance retrieval, component discovery/code retrieval, token retrieval, and two complementary audit paths. Each tool has a clear role.
The set covers the core workflow of a design-system copilot: retrieve guidelines/layouts/tokens, find and fetch components, and audit both UX compliance and system performance. No obvious dead ends or missing lifecycle steps for this domain.