Branding MCP Server

AI-powered brand identity generation via MCP with design tokens, typography, and logo assets. The branding mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

• Color Palette Generation — — HSL-based color harmonies (complementary, analogous, triadic, etc.) with WCAG contrast validation
• Typography System — — Modular type scales with curated font pairings
• Spacing Scale — — Geometric progression spacing system
• Shadow/Elevation System — — 6-level elevation scale with brand-tinted shadows, light/dark theme support
• Border/Shape System — — Style-aware radius scales and border widths for all 8 brand styles
• Motion/Animation System — — Duration scales, cubic-bezier easings, and transition presets per brand style

Its toolset

Everything the assistant can do here goes through one of these:

• generate_brand_identity — Complete brand from name, industry, and style
• generate_color_palette — Color palette with harmony and WCAG data
• generate_typography_system — Font pairing + modular type scale
• export_design_tokens — Export brand to JSON/CSS/Tailwind/Figma/React/Sass
• create_brand_guidelines — Generate HTML brand book
• validate_brand_consistency — Check WCAG compliance and completeness
• refine_brand_element — Iterate on specific brand elements
• generate_brand_assets — Generate favicons and OG images from brand
• generate_design_system — Complete design system in one call (identity + export)
• generate_brand_fintech — Fintech-specific strategy with compliance and security
• generate_brand_healthcare — Healthcare strategy with care models and safety signals

Configuration

You will need one environment variable: ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @forgespace/branding-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Branding's toolset — generate_brand_identity, generate_color_palette, generate_typography_system and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Forge-Space; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Branding.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the branding mcp server does with a few real requests.