BrandKit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_brand_overviewA | Get a high-level overview of the design system: brand name, active contexts, asset inventory counts, and available design system sections. |
| get_colorsA | Get the color palette with hex values, RGB values, usage guidelines, and semantic roles. Supports context filtering (marketing vs product) and output format selection. |
| get_typographyB | Get typography specifications: font families, sizes, weights, line heights, and usage guidelines per context. |
| get_logosA | Get logo variants (primary, mark, wordmark, monochrome) with usage guidelines, minimum sizes, clear space rules, and forbidden uses. Optionally returns base64-encoded image data. |
| get_componentsA | Get component specifications, variants, CSS properties, and usage guidelines. Filter by context (marketing vs product) or category. |
| get_guidelinesA | Get brand guidelines, voice and tone documentation, accessibility rules, and usage policies. Returns full markdown content. |
| get_tokensA | Export design tokens in a specific format: CSS custom properties, SCSS variables, Tailwind config, W3C Design Tokens format, or JSON. |
| get_texturesA | Get texture and pattern assets with usage context. Returns metadata and optionally base64-encoded image data. |
| get_cssB | Get raw CSS file contents and extracted custom property definitions from the design system. |
| search_brandA | Full-text search across all design system content: guidelines, component specs, color names, typography definitions, and brand documentation. |
| get_context_diffA | Compare marketing site vs product app design systems side-by-side, highlighting differences in colors, typography, and components. |
| validate_usageA | Validate whether a specific color, font, or logo usage complies with the brand guidelines. Returns pass/fail with specific guidance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design-with-brand | Build a UI feature using the brand design system. Auto-injects colors, typography, and component conventions for the given context. |
| audit-brand-compliance | Audit a snippet of CSS/HTML/JSX for brand compliance. Flags non-brand colors, fonts, and unapproved logo usage. |
| generate-tailwind-theme | Generate a Tailwind v3 / v4 theme extension that mirrors the current brand tokens. |
| explain-brand-decision | Explain how a particular brand-system rule should be applied for a given scenario. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Brand Overview | High-level summary of the brand and asset inventory |
| Design Tokens (CSS) | |
| Design Tokens (SCSS) | |
| Design Tokens (Tailwind) | |
| Design Tokens (W3C) | |
| Design Tokens (JSON) | |
| Colors -- all contexts | |
| Colors -- marketing | |
| Colors -- product | |
| Typography -- all contexts | |
| Components -- all contexts | |
| Logo System | |
| Raw CSS (concatenated) | |
| Guideline: Accessibility Guidelines | |
| Guideline: Logo Usage Guidelines | |
| Guideline: Brand Voice & Tone |
TDQS
Scored across 12 tools
Each tool targets a distinct aspect of the brand/design system: overview, colors, components, context diff, CSS, guidelines, logos, textures, tokens, typography, search, and validation. No two tools have overlapping purposes.
10 of 12 tools follow the 'get_' verb_noun pattern (e.g., get_colors, get_components). However, 'search_brand' and 'validate_usage' break this pattern by using different verbs, introducing slight inconsistency.
With 12 tools, the count is well within the optimal 3-15 range. Each tool represents a meaningful and distinct function for managing a brand kit, neither too few nor too many.
The set covers core retrieval and validation operations for brand assets (colors, typography, logos, etc.) and includes search and diff capabilities. The absence of mutation tools (create/update/delete) is a minor gap, but likely intentional for a read-only inspection server.