Skip to content
Integrations

Connect your AI app

Your coding agent can build with your brand directly: your colors, type, logo files and finished designs. You connect it once with an API key from your account, and every project on that computer can use it.

Works with Claude Code, Claude desktop app (Code tab), Codex, Cursor, VS Code.

1. Create an API key
One key connects every app you use. It is shown once, so copy it right away.
Once you have an account, keys live in Settings, API keys. Give it Read to build from your brand; add Send work back if the agent should upload designs for your review. More about keys
2. Add BrandPilot to your app
Pick your app, copy the setup and replace YOUR_API_KEY with your key.

Server address

server address
https://brandpilot.dev/api/mcp

Add BrandPilot to Claude Code once; every project on this computer can use it.

  1. Create an API key, then run this in your terminal with YOUR_API_KEY replaced by the key.
  2. Start Claude Code and run /mcp to check that brandpilot shows as connected.
Run in your terminal
claude mcp add --transport http --scope user brandpilot https://brandpilot.dev/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Another app that only runs local servers? Use the brandpilot-mcp npm package with your API key in its environment. It connects to the same account and tools.

Local server config
{
  "mcpServers": {
    "brandpilot": {
      "command": "npx",
      "args": [
        "-y",
        "brandpilot-mcp"
      ],
      "env": {
        "BRANDPILOT_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
3. Check that it works
Send this to your agent. It should name your workspace and list your brands.
test prompt
Ask BrandPilot who I am and list my brands.
What your agent can do
The tools it gets once connected.
  • Check the connection whoamiWho this connection is: the workspace, the key name and prefix, and the permissions it holds. Use it to confirm a new connection works.
  • List the brands in this workspace list_brandsThe brands in the workspace this key belongs to, each with its designs (id, name, status, whether it is ready to build from). Start here to find a design id.
  • Get a design's build context get_design_contextThe design's continuation bundle as JSON: brief, tokens, board digest, the continuation contract (hard floor first, then the latitude level), live inventory, coherence audit and the import contract.
  • Get the repo rules pack get_repo_rules_packThe files that teach a coding agent this brand inside your repo: AGENTS.md, CLAUDE.md, a Cursor rule, DESIGN.md and the token files, each with its path and content. Merge the marked blocks, never overwrite the rest of a file.
  • Get the Claude Design kit manifest get_claude_design_kitThe Claude Design kit for a design: its title, file list with sizes and validation result, plus the download URL for the zip (fetch it with the same API key as a Bearer token).
  • Import externally designed artifacts import_design_artifactsImport externally designed work back into DesignFlow. Rows land as DRAFT on the carrier project's Deliverables tab for human review - nothing auto-approves. Components: self-contained HTML with inline styles. Pages: standalone HTML documents. Assets: PNG (base64 or URL) with optional sourceCode.
  • Finish a mid-flow external design run finish_external_designValidates that components and pages were imported, optionally accepts every pending imported draft, then resumes the pipeline at the coherence audit toward Design Review. Only valid while the project is paused at EXTERNAL_DESIGN.
Go further