BrandKity
MCP Client Setup

Connect BrandKity MCP in minutes across popular AI clients

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.

Back to MCP pageOpen API Keys

Shared config for all clients

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

VS Code Copilot

Where to configure: Open VS Code settings and search for MCP servers in GitHub Copilot Chat.

  1. 1Add a new stdio MCP server named brandkity.
  2. 2Set command to npx with args: -y and @brandkity/mcp.
  3. 3Add env variable BRANDKITY_API_KEY with your live key.
  4. 4Save settings and restart the Copilot chat session.

If your build uses a command palette flow, use MCP add server from the palette and enter the same values.

Cursor

Where to configure: Cursor Settings > MCP (or Agent tools / Integrations, depending on version).

  1. 1Create a new local MCP server entry.
  2. 2Command: npx
  3. 3Args: -y, @brandkity/mcp
  4. 4Env: BRANDKITY_API_KEY = bk_live_... and reconnect the agent.

Windsurf

Where to configure: Windsurf Settings > MCP Servers.

  1. 1Add a server named brandkity.
  2. 2Use npx -y @brandkity/mcp as the launch command.
  3. 3Set BRANDKITY_API_KEY in server environment variables.
  4. 4Restart the MCP session and verify BrandKity tools appear.

Claude Desktop

Where to configure: Edit your local claude_desktop_config.json file.

  1. 1Windows path: %APPDATA%\Claude\claude_desktop_config.json
  2. 2Mac path: ~/Library/Application Support/Claude/claude_desktop_config.json
  3. 3Paste the shared JSON config below under mcpServers.
  4. 4Restart Claude Desktop and confirm BrandKity tools are visible.

Claude Code

Where to configure: Open Claude Code MCP settings or configuration file for local servers.

  1. 1Add a local stdio server named brandkity.
  2. 2Command: npx
  3. 3Args: -y, @brandkity/mcp
  4. 4Set BRANDKITY_API_KEY and restart your Claude Code session.

CLI and settings names can differ by release; if needed, search for MCP in Claude Code settings and apply the same command/args/env.

Antigravity

Where to configure: Open Antigravity MCP or tool integrations settings.

  1. 1Create a new MCP server entry named brandkity.
  2. 2Configure command npx with args -y and @brandkity/mcp.
  3. 3Set env key BRANDKITY_API_KEY with your live key.
  4. 4Reconnect the assistant session and run a quick workspace tool call.

If your UI labels differ, use the generic MCP local server flow with the same command and env.

Any MCP Client

Where to configure: Use the client MCP server settings page or config JSON/YAML file.

  1. 1Transport: stdio
  2. 2Command: npx
  3. 3Args: -y, @brandkity/mcp
  4. 4Env: BRANDKITY_API_KEY = bk_live_...

Verification and troubleshooting

Run a workspace read tool first to validate auth and plan access.

Expect 403 on free or starter plans until upgraded to 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.