BrandKity MCP Server
OfficialThe BrandKity MCP Server enables AI agents to programmatically create, manage, and publish brand kits from any MCP-compatible client (Claude Desktop, Cursor, Windsurf, etc.).
Workspace Management
Retrieve workspace details (plan, kit count, storage usage)
Upload files (images, fonts, videos, documents, ZIPs) to storage and get a public CDN URL
List workspace files with filtering by type and pagination
Brand Kit Management
Create kits with name, accent color, tagline, and template
List, get, update, publish, or unpublish existing brand kits
Block Management
List, idempotently create (
ensure_block), add, update (name/visibility), and delete blocksSupported block types: Colors, Typography, Logos, Visuals, Videos, Icons, Collaterals, Resources, Rich Text
Content & Style Definition
Add color swatches (hex, RGB, CMYK, Pantone) to Colors blocks
Define font entries (Google, Adobe, Custom, System) in Typography blocks
Set rich text content (brand story, tone of voice, values) in Rich Text blocks
Add editorial/usage guidance notes to any block
Asset Upload & Integration
Upload individual assets (logos, visuals, videos, icons, etc.) into specific blocks
Batch upload multiple files with deduplication and configurable concurrency
Upload kit-level logo and cover image directly
White-Label Branding (Pro+ Feature)
Set custom SEO title, description, favicon, and social share (OG) image for kit portals
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BrandKity MCP Server Create a brand kit for Acme Corp with accent #E55B00"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@brandkity/mcp — BrandKity MCP Server
Model Context Protocol server for BrandKity — create and manage brand kits from any AI agent (Claude Desktop, Cursor, Windsurf, or any MCP-compatible client).
Current Version: 1.4.3 — MCP now available on Starter, Pro, and Agency plans
Quick Start
1. Get an API Key
Sign in at brandkity.com
Go to Settings → API Keys
Click Generate New Key and copy the key (
bk_live_...)
Available on Starter, Pro, and Agency plans. Sign up free to explore, then upgrade Starter or above to run tool calls.
2. Configure Your AI Client
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": ["-y", "@brandkity/mcp"],
"env": {
"BRANDKITY_API_KEY": "bk_live_your_key_here"
}
}
}
}Cursor
Edit .cursor/mcp.json:
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": ["-y", "@brandkity/mcp"],
"env": {
"BRANDKITY_API_KEY": "bk_live_your_key_here"
}
}
}
}Windsurf
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": ["-y", "@brandkity/mcp"],
"env": {
"BRANDKITY_API_KEY": "bk_live_your_key_here"
}
}
}
}3. Use It
Once configured, ask your AI agent to create a brand kit:
"Create a brand kit for Acme Corp with the accent color #E55B00. Add a Colors block with the primary palette (Orange Flame #E55B00, Midnight #1A1A2E, Canvas #FAF9F7) and a Typography block with Inter for headings and DM Sans for body. Upload the logos from /Users/me/acme/logos/."
Related MCP server: brand-gen
Available Tools (22)
Tool | Description |
Workspace | |
| Get workspace info (plan, kit count, storage) |
Files | |
| Upload any local file to workspace storage → returns a public URL |
| List workspace files with type filter and pagination |
Kits | |
| List all brand kits (filter by draft/published/all) |
| Create a new kit → returns kit_id |
| Get a kit with all blocks and content |
| Update kit settings (name, color, template, logo_url, cover_image_url, white-label fields) |
| Publish a kit → returns public URL |
| Unpublish a kit (reverts to draft) |
Blocks | |
| List all blocks in a kit with IDs and types |
| Idempotent — returns existing block_id or creates a new block (preferred over add_block) |
| Add a block unconditionally (use ensure_block instead to prevent duplicates) |
| Update block name/visibility |
| Permanently delete a block and all its content |
Content | |
| Add color swatches to a Colors block |
| Add font entries to a Typography block |
| Set rich text content (brand story, tone of voice) |
| Set the editorial note displayed above any block |
Upload | |
| Upload a local file into a block (logos, visuals, videos, etc.) with auto-retry |
| Upload multiple local files into the same block; deduplicates by file path |
| Upload and set the kit's header logo |
| Upload and set the kit's cover image |
White-Label Branding (Pro+ Feature)
Customize your portal with custom favicon, social share image, and SEO metadata:
// Upload custom assets
const faviconUrl = await client.uploadFile('favicon.ico', faviconBuffer);
const ogImageUrl = await client.uploadFile('og-image.png', ogImageBuffer);
// Apply white-label branding
await client.updateKit('kit-id', {
og_title: 'Acme Corp Brand Guidelines',
og_description: 'Official brand assets and standards',
custom_favicon_url: faviconUrl,
og_image_url: ogImageUrl,
});Fields:
og_title(string, max 100 chars) — SEO title for social shareog_description(string, max 300 chars) — SEO descriptioncustom_favicon_url(string) — CDN URL to favicon (ICO/PNG/SVG)og_image_url(string) — CDN URL to social share image (1200×630 px recommended)
Plan Requirements:
Free: White-label fields are read-only; MCP tool calls return 403
Starter/Pro/Agency: Full MCP access; white-label fields are read-write on Pro/Agency
Environment Variables
Variable | Required | Default | Description |
| Yes | — | Personal Access Token ( |
| No |
| API base URL (for local dev) |
Typical Workflow
1. get_workspace → verify connection, check plan and storage
2. list_kits → confirm kit doesn't already exist
3. create_kit → returns kit_id
4. ensure_block → idempotent: returns existing block_id or creates a new one (for each block type)
5. add_colors → populate the Colors block
6. add_typography → populate the Typography block
7. upload_file → upload font/logo/cover files to workspace storage
8. upload_asset → upload logos, images, videos into blocks
9. set_brand_story → write the brand story in a rich_text block
10. set_block_note → add usage guidance to any block
11. publish_kit → make the portal liveReliability Notes (v1.4.0)
No duplicate blocks —
ensure_blockis idempotent. Re-running a workflow never creates duplicate blocks.Auto-retry on uploads —
upload_assetandupload_fileretry up to 3 times on network errors with exponential backoff.Size-aware timeouts — Upload timeout scales with file size (60 s base + 20 s per 10 MB, max 10 min). Large files like 64 MB video assets are handled reliably.
Batch deduplication —
upload_assets_batchsilently skips duplicatefile_pathentries so the same file is never uploaded twice in one batch.Agent instructions — The server now provides operating rules to AI clients at connection time, reducing duplicate operations from AI agents automatically.
White-label URL resolution — CDN URLs in white-label fields are automatically resolved to asset IDs server-side; agents don't need to manage asset IDs directly.
Storage tracking — All file uploads are tracked per workspace for accurate quota enforcement.
License
MIT
Available Tools
22 toolsadd_blockA
IMPORTANT: prefer ensure_block over this tool — ensure_block is idempotent and prevents duplicates. add_block creates a new block unconditionally. Calling it twice creates two separate blocks of the same type. Only use add_block when you have already confirmed via list_blocks that no block of this type exists. Block types: • colors — brand palette swatches (use add_colors) • typography — font entries (use add_typography) • rich_text — brand story / guidelines text (use set_brand_story) • logos — logo variants uploaded as SVG/PNG (use upload_asset with block_type=logos) • visuals — brand photography / illustrations (use upload_asset with block_type=visuals) • videos — brand video assets (use upload_asset with block_type=videos) • icons — SVG icon library (use upload_asset with block_type=icons) • collaterals — downloadable files like PDFs (use upload_asset with block_type=collaterals) • resources — source files, Figma, ZIPs (use upload_asset with block_type=resources)
Inputs: kit_id (required), type (required), name.
add_colorsA
Add color swatches to a Colors block. Valid fields per swatch: name (required), hex (required, #rrggbb), rgb ("R, G, B"), cmyk ("C, M, Y, K"), pantone. There is NO usage field on color swatches — put usage guidance in the block note via set_block_note instead.
Inputs: kit_id (required), block_id (required), colors (required).
add_typographyA
Add font entries to a Typography block. Four sources are supported: (1) "Google Fonts" — provide font_family, weights, usage. Fully automated. (2) "Adobe Fonts" — provide font_family + asset_url (Typekit CSS URL from fonts.adobe.com → Web Projects → Get embed code). (3) "Custom" — first upload the font file using upload_file tool, then pass asset_url (the returned URL) here. (4) "System" — provide font_family only (font must be available on the OS).
Inputs: kit_id (required), block_id (required), fonts (required).
create_kitA
Create a new brand kit. Returns the kit ID needed for subsequent operations like adding blocks and uploading assets.
Inputs: name (required), accent_color (required), template, tagline.
delete_blockA
Permanently delete a block and all its content from a kit. This cannot be undone.
Inputs: kit_id (required), block_id (required).
ensure_blockA
PREFERRED over add_block. Idempotent block creation: if a block of the given type already exists in the kit, returns its block_id without creating a duplicate. If no matching block exists, creates one and returns the new block_id. Use this for every block in your workflow so re-runs and retries never produce extra blocks. The "created" field in the response tells you whether a new block was created (true) or an existing one was returned (false).
Inputs: kit_id (required), type (required), name.
get_kitA
Fetch a kit's full data including all blocks and their content.
Inputs: kit_id (required).
get_workspaceA
Returns the workspace associated with the API key. Use this to verify the connection and check workspace details like plan, kit count, and storage usage.
Inputs: no named parameters.
list_blocksA
List all blocks in a kit with their IDs, types, names, and visibility. Use to find block_ids before adding content.
Inputs: kit_id (required).
list_filesA
List files in your workspace storage. Filter by type to find fonts, images, documents, etc. Returns public URLs for each file.
Inputs: type, page.
list_kitsA
List all brand kits in the workspace. Optionally filter by status (draft, published, or all).
Inputs: status.
publish_kitB
Publish a kit, making its portal publicly accessible. Returns the public URL.
Inputs: kit_id (required).
set_block_noteA
Set the sticky editorial note on any block (the "Block note" editor visible at the top of every block in the dashboard). Use this for usage guidance, rules, or context that applies to the whole block. For colors: "Electric Blue is always the primary CTA colour." For typography: "Never use Outfit below 600 weight." For logos: "Always use the SVG version on digital. Use reversed on dark backgrounds."
Inputs: kit_id (required), block_id (required), note (required).
set_brand_storyA
Set the content of a Rich Text block. Use for brand story, tone of voice, brand values, do's & don'ts extracted from guidelines documents. Accepts plain text or basic HTML.
Inputs: kit_id (required), block_id (required), content (required).
unpublish_kitA
Unpublish a kit, taking it offline. The kit remains in draft and can be re-published later.
Inputs: kit_id (required).
update_blockA
Update a block's name or visibility. To set the block note, use set_block_note instead.
Inputs: kit_id (required), block_id (required), name, is_visible.
update_kitA
Update a kit's top-level settings like name, accent color, template, tagline, logo, cover image, or white-label meta/favicon (Pro+). For logo_url and cover_image_url, pass CDN URLs returned by upload_file or upload_asset. For og_image_url and custom_favicon_url, pass CDN URLs from upload_file.
Inputs: kit_id (required), name, accent_color, template, +7 more.
upload_assetA
Upload a file from the local filesystem into a block in BrandKity. Use for: logos (SVG/PNG/JPG), visuals (brand photos), videos (MP4/WebM), icons (SVG only), collaterals (PDF/images), and resources (ZIPs, source files). For custom font files, use upload_file → add_typography(asset_url) instead.
Inputs: kit_id (required), block_id (required), file_path (required), block_type (required), +5 more.
upload_assets_batchA
Batch upload multiple local files into a single block with one tool call. Duplicate file_path values in the list are automatically skipped — each unique path is uploaded only once. Use for logos, visuals, videos, collaterals, resources, and icons. For files larger than 50 MB, prefer uploading individually with upload_asset. If the batch partially fails, resubmit only the failed files.
Inputs: kit_id (required), block_id (required), block_type (required), files (required), +2 more.
upload_cover_imageA
Upload an image to set as the kit's hero/cover image (shown at the top of the portal for supported templates). Uploads the file to workspace storage and then sets cover_image_url on the kit.
Inputs: kit_id (required), file_path (required).
upload_fileA
Upload any file from the local filesystem to your BrandKity workspace storage (R2). Returns a public URL you can use in other tools. Common use cases: • Font files (.ttf, .otf, .woff, .woff2) → use returned URL in add_typography asset_url • Kit logo or cover image → use returned URL in update_kit logo_url/cover_image_url • General brand assets → manage from your file library Supported: images (PNG, JPG, SVG, WebP), video (MP4, WebM), fonts (TTF/OTF/WOFF/WOFF2), documents (PDF, DOCX, PPTX), ZIP.
Inputs: file_path (required), tags.
upload_kit_logoA
Upload an image to set as the kit's main logo (shown in the portal header). This is different from the Logos block — this is the kit branding logo. Uploads the file to workspace storage and then sets logo_url on the kit.
Inputs: kit_id (required), file_path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Most tools have distinct purposes, but the multiple upload tools (upload_asset, upload_assets_batch, upload_file, upload_kit_logo, upload_cover_image) and add_block vs ensure_block may confuse an agent. Descriptions help, but some overlap remains.
All tools use snake_case with a consistent verb_noun pattern (e.g., add_colors, list_kits, publish_kit). No mixing of conventions, making the naming predictable.
22 tools is slightly high but still reasonable for a brand kit management server covering CRUD, uploads, publishing, and workspace info. Each tool has a clear role, though some could be consolidated.
Covers core workflows for kits, blocks, and assets, but missing delete_kit and delete_asset (only delete_block exists). Also lacks granular content retrieval for specific block types beyond get_kit.
Maintenance
Related MCP Connectors
Your brand's Styles, logos and asset library in your AI app, for on-brand assets that match.
Build and run AI image, video and on-brand ad workflows from chat, with brand kits and share links.
Brand-safe MCP for AI agents to create editable, on-brand graphics and automate variants.
On-brand creative studio for AI agents: images, video, audio, and 3D.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch company logos, brand colors, fonts, and corporate information from the Brandfetch API using domain lookups or keyword searches.1MIT
- AlicenseNot gradedqualityDmaintenanceA memory-backed brand generation runtime for agent-led creative iteration. Enables AI agents to plan, generate, review, and improve brand materials with persistent brand memory and structured workflows.MIT

Canvora MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents to generate on-brand visuals from ideas, URLs, documents, or PDFs in over 100 formats and 150+ languages, with consistent brand kits.1628 npm1MIT
BranderUX MCPofficial
AlicenseNot gradedqualityBmaintenanceBuild a full agentic application for a business from your AI client: brand, real data, custom elements, screens and a hosted agent, then publish a live website and MCP app. After launch, read the leads, bookings and orders your agent collects.MIT