BrandKity MCP Server — Create and manage brand kits from AI agents
BrandKity MCP Server — Create and manage brand kits from AI agents. That is what the brandkity mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Model Context Protocol server for BrandKity — create and manage brand kits from any AI agent (Claude Desktop, Cursor, Windsurf, or any MCP-compatible client).
The server publishes 14 tools. What each one is for:
Workspace — The Workspace tool exposed by this serverget_workspace — Get workspace info (plan, kit count, storage)Files — The Files tool exposed by this serverupload_file — Upload any local file to workspace storage → returns a public URLlist_files — List workspace files with type filter and paginationKits — The Kits tool exposed by this serverlist_kits — List all brand kits (filter by draft/published/all)create_kit — Create a new kit → returns kit_idget_kit — Get a kit with all blocks and contentupdate_kit — Update kit settings (name, color, template, logo_url, cover_image_url, white-label fields)publish_kit — Publish a kit → returns public URLunpublish_kit — Unpublish a kit (reverts to draft)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: BRANDKITY_API_KEY, BRANDKITY_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Brandkity MCP's toolset — Workspace, get_workspace, Files and 11 more — is a fair guide to whether it matches your workflow. It is maintained by brandkity; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Brandkity MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Workspace | The Workspace tool exposed by this server. |
| get_workspace | Get workspace info (plan, kit count, storage) |
| Files | The Files tool exposed by this server. |
| upload_file | Upload any local file to workspace storage → returns a public URL |
| list_files | List workspace files with type filter and pagination |
| Kits | The Kits tool exposed by this server. |
| list_kits | List all brand kits (filter by draft/published/all) |
| create_kit | Create a new kit → returns kit_id |
| get_kit | Get a kit with all blocks and content |
| update_kit | Update kit settings (name, color, template, logo_url, cover_image_url, **white-label fields**) |
| publish_kit | Publish a kit → returns public URL |
| unpublish_kit | Unpublish a kit (reverts to draft) |
| Blocks | The Blocks tool exposed by this server. |
| list_blocks | List all blocks in a kit with IDs and types |
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": ["-y", "@brandkity/mcp"],
"env": {
"BRANDKITY_API_KEY": "bk_live_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BRANDKITY_API_KEY | Credential the server authenticates with. | Yes |
| BRANDKITY_API_URL | Endpoint or connection string the server talks to. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.