Summary
A brand kit assembled from a brief, not from an editor.
Because the kit, its blocks, its assets and the publish step are all tools, one instruction can go from an empty workspace to a public kit URL — and the same tools update it afterwards without a round trip through the UI.
What it is
BrandKity's own MCP server for its hosted brand kit builder. Twenty-two tools cover the whole object model: the workspace, file storage, kits, the blocks inside a kit, and publishing.
What you get
- A kit created, updated, published to a public URL, or unpublished again
- Blocks added, updated, removed, or created only when they are missing
- Colour palettes and typography written into a kit as blocks
- Local files uploaded to workspace storage and returned as public URLs, singly or in a batch
- A kit's logo and cover image uploaded directly onto the kit
- The brand story set as text, and a note attached to any block
- Kits and files listed with filters and pagination, and one kit fetched with all its blocks
- Workspace plan, kit count and storage read back
Requirements
A BrandKity account on the Starter, Pro or Agency plan, and an API key generated at Settings then API Keys. It goes in the client config as BRANDKITY_API_KEY. Runs through npx, so there is nothing to build locally.
Setup effort
One command plus a key — npx -y @brandkity/mcp, then supply credentials