Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UI_UX_MCP_API_KEYYesThe API key required to authenticate with the VibeCraft MCP server.

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation3/5

Most tools have clear boundaries, but audit_ux_compliance and get_ux_guidelines reference nearly the same set of UX rules and heuristics, making their purposes easy to confuse. get_layout_blueprint also overlaps with get_ux_guidelines via NN/g IA content, though the descriptions help differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: audit_*, get_*, search_*. This makes the toolset predictable and easy to navigate.

Tool Count5/5

Seven tools is well-scoped for a design/UX assistant server. Each tool covers a distinct part of the workflow: auditing, guidelines, layout, components, and design tokens, without feeling bloated or thin.

Completeness4/5

The toolset covers the core design/UX loop well: retrieve guidelines and tokens, find and fetch components, and audit both system performance and UX compliance. Minor gaps exist, such as no explicit tool for applying fixes or generating a consolidated audit report, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues