This guide covers VS Code Copilot, Antigravity, Cursor, Claude Code, Claude Desktop, Windsurf, and any other MCP-compatible client. Use the same server definition in every tool, then authenticate with your BrandKity API key.
Most clients accept a local stdio MCP server with command, args, and env values. Start here, then paste this in your client-specific MCP settings.
{
"mcpServers": {
"brandkity": {
"command": "npx",
"args": ["-y", "@brandkity/mcp"],
"env": {
"BRANDKITY_API_KEY": "bk_live_..."
}
}
}
}Required command
npx -y @brandkity/mcp
Required environment key
BRANDKITY_API_KEY
Where to configure: Open VS Code settings and search for MCP servers in GitHub Copilot Chat.
If your build uses a command palette flow, use MCP add server from the palette and enter the same values.
Where to configure: Cursor Settings > MCP (or Agent tools / Integrations, depending on version).
Where to configure: Windsurf Settings > MCP Servers.
Where to configure: Edit your local claude_desktop_config.json file.
Where to configure: Open Claude Code MCP settings or configuration file for local servers.
CLI and settings names can differ by release; if needed, search for MCP in Claude Code settings and apply the same command/args/env.
Where to configure: Open Antigravity MCP or tool integrations settings.
If your UI labels differ, use the generic MCP local server flow with the same command and env.
Where to configure: Use the client MCP server settings page or config JSON/YAML file.
Run a workspace read tool first to validate auth and plan access.
Expect 403 on free plans until upgraded to Starter, Pro, or Agency.
If tools do not appear, restart the client and re-check env variable names.
Need a faster walkthrough? Open the MCP page demo video, then copy the shared JSON config into your client and test with a single workspace call.