Brandkit MCP

What ejwhite7/brandkit-mcp MCP server does

The ejwhite7/brandkit-mcp MCP server makes a brand’s atomic system available as structured MCP tools and resources. It covers verbal identity documents such as positioning, audience, messaging, differentiation, creative concepts, and voice. It also serves visual material including CSS color and typography properties, font files, logos and other assets, component specifications, design tokens, motion definitions, and raw CSS.

The server includes read operations for each major content area, full-text search across indexed brand material, usage validation for HTML and CSS snippets, and context comparisons. A separate local synchronization tool can update brandkit.config.yaml, DESIGN.md, and PRODUCT.md; network transports hide this write-capable operation by default. The human-authored magic_trick.md file is returned as a taste primer and is not written by the synchronization tool.

How it works

A brandkit.config.yaml file identifies the brand name, description, root directory, supported contexts, ignored paths, and ingestion limits. Version 2 is required. By default, brand content lives in brand_atomic_system/, with verbal files under agent/verbal/ and visual files under agent/visual/.

The server indexes content below the configured brand root while excluding paths such as human/ when configured. The human/ area is intended for PDFs and other material that should remain outside the MCP-facing system. File, byte, depth, and count limits bound ingestion, and linked files cannot bypass the root or those limits.

Visual contexts use a shared base foundation plus optional web and product overrides. Verbal content applies globally. Token results can be returned as JSON, CSS, SCSS, Tailwind configuration, or W3C Design Tokens output. The MCP resource catalog uses brand:// URIs for overview, verbal documents, visual indexes, and motion data.

Setup and configuration

Install the npm package globally with npm install -g brandkit-mcp, then run brandkit-mcp init to create a starter brand system. Edit the generated files and connect the server to an MCP client using the brandkit-mcp serve command. Claude Desktop configuration uses a server entry with that command and no required credential.

The ejwhite7/brandkit-mcp MCP server expects a version 2 configuration. A typical configuration declares brand.root, contexts such as base, web, and product, and optional ignore and ingestion settings. The initializer refuses to replace an existing configuration or brand directory unless explicitly forced. Version 1 configurations are rejected at startup and require manual migration.

Tools and capabilities

Available capabilities include:

• Retrieve brand overview data and the human-authored taste primer.
• Read positioning, audience, messaging, differentiation, concepts, and voice documents.
• Return colors, typography, assets, fonts, components, tokens, motion, and raw CSS.
• Search across verbal and visual brand content.
• Validate token and component usage in HTML or CSS snippets.
• Compare base, web, and product visual contexts.
• Expose brand material through MCP resources as well as tools.

The ejwhite7/brandkit-mcp MCP server is suited to website, application, and marketing workflows where generated output must follow an existing brand system rather than inventing its own visual or verbal rules.