get_workspaceLABSCO 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
USE CASES
01
Standing up a brand kit for a new client
Create the kit, write the palette and typography in as blocks, upload the logo, and publish it to a public URL.
02
Getting a folder of assets into the workspace
Upload files one at a time or as a batch, then list what landed with the type filter to confirm it is all there.
03
Updating a kit that is already live
Fetch the kit with its blocks, change the ones that moved, then publish again.
04
Adding a section only if it is missing
ensure_block creates the block when it is not there and leaves it alone when it is, so a repeated run does not duplicate sections.
05
Writing the story and the reasoning around a kit
The brand story is set as text on the kit, and each block can carry a note explaining why it is what it is.
06
Taking a kit off the public web
Find the published kits, unpublish the one that should no longer be reachable.
22 tools
Listed in project docs. Your client may show a different list.
upload_filelist_fileslist_kitscreate_kitget_kitupdate_kitpublish_kitunpublish_kitlist_blocksensure_blockadd_blockupdate_blockdelete_blockadd_colorsadd_typographyset_brand_storyset_block_noteupload_assetupload_assets_batchupload_kit_logoupload_cover_imageBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
Requires
- npx on PATH
- BRANDKITY_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @brandkity/mcpMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": [
"-y",
"@brandkity/mcp"
],
"env": {
"BRANDKITY_API_KEY": "<YOUR_BRANDKITY_API_KEY>"
}
}
}
}
