MCP server

Web Stylebook MCP: Scored Design Directions for AI Agents

Web Stylebook MCP is an offline MCP server that scores design directions, plans UI states, and exports WCAG checked design tokens for an AI coding agent, with no API key.

Run
claude mcp add web-stylebook -- npx -y web-stylebook-mcp@latest
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is Web Stylebook MCP?

Web Stylebook MCP is a Model Context Protocol server that hands an AI coding agent scored design direction candidates, placement aware interface and UX principle plans, UI state plans, and role based design tokens, drawn from a bundled catalog of real world references and styles, entirely offline with no API key, model call or network access.

Web Stylebook MCP is a Model Context Protocol server built from a bundled, offline catalog. An agent describes a product, and the server scores styles, structure and tokens from that catalog, rather than generating code or calling a model itself.

Scored directions, not one guess

recommend_design_direction returns ranked style candidates with reason codes, a winner and runner up with a score gap, styles it rejected and why, and pairing suggestions, so the agent picks with evidence instead of committing to one look.

Tokens, structure and states

compose_design_tokens turns a chosen style into role based color, type, spacing and motion tokens with WCAG contrast warnings. Candidates also carry a layout archetype and signature moves, and get_ui_state_plan lists the states a surface needs.

Auditing a built page

audit_page_structure checks submitted HTML and CSS against banned generic patterns and the chosen style's own bans, naming each location and a replacement move. validate_design_audit_result then checks an audit's evidence and verdicts for consistency.

Who it suits

Best for

  • Agents that need a defensible reason for one visual direction over another, with rejected candidates on record.
  • Teams that want WCAG checked tokens and documented UI states before any code is written.
  • Projects that want a page checked for the default hero plus three cards template after it is built.

Not for

  • Researching real product references before locking one design direction, where Refero Design runs that research and lock step itself.
  • Running blocking questions and adversarial critique before handing over component specs, where Octopus UI/UX Design enforces that question and critique workflow.
  • Extracting real tokens by scraping an already live site, where Extract Design pulls those exact values instead of scoring a new direction.
  • Turning one brief directly into finished brand color ramps and tokens, where Brandkit builds that foundation from scratch rather than a scored catalog.