Docs
BrandPilot is built for a solo technical founder who ships their own product with a coding agent, not a design team. Every brand system it produces - tokens, components, pages, brand assets - is reachable two ways: as an MCP server your agent connects to directly, or as a plain public REST API you can curl. Both surfaces read the same underlying data, so nothing here can drift out of sync with what your agent actually gets.
{
"mcpServers": {
"brandpilot": {
"command": "npx",
"args": ["-y", "brandpilot-mcp"],
"env": {
"DESIGNFLOW_HANDOFF_KEY": "your-design-handoff-key"
}
}
}
}The brandpilot-mcp package is not on npm yet. Until it publishes, run the repo-local server the same way from inside the BrandPilot app checkout:
npx tsx scripts/mcp-server.ts| Tool | What it does | Auth | REST equivalent |
|---|---|---|---|
| list_systems | List the public design systems in the BrandPilot pool (name, slug, brand color, token count, status). | public | GET /api/v1/systems |
| get_system_adoption | Full adoption manifest for a public system: tokens, components, pages, brand asset URLs and the binding design-direction block. | public | GET /api/v1/systems/{name}/adoption |
| get_system_tokens | Export a public system's tokens in one format: globals-css, colors-ts, spacing-ts, typography-ts, tailwind-theme or brand-manifest. Calls the legacy /api/systems/export endpoint, not a v1 path - the export route has no v1 equivalent yet. | public | GET /api/systems/export/{name} |
| get_agent_prompt | Markdown onboarding doc for a public system: the two copy-paste prompts an external AI coding agent uses to bootstrap a design package and sync it to Claude Design. | public | GET /api/v1/systems/{name}/agent-prompt |
| get_design_handoff | The 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. Available mid-flow (project paused at EXTERNAL_DESIGN) and post-completion. | handoff key | GET /api/v1/designs/{designId}/handoff |
| get_design_prompt_pack | The app-authored sequential Claude Design prompt pack (markdown): anchor sheet first, then template-aware component sheets and page prompts, each embedding the latitude contract in force. Regenerated from live data on every call. | handoff key | GET /api/v1/designs/{designId}/prompt-pack |
| import_design_artifacts | Import 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. | handoff key | POST /api/v1/designs/{designId}/external-artifacts |
| finish_external_design | Validates 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. | handoff key | POST /api/v1/designs/{designId}/finish-external |
The list_systems, get_system_adoption, get_system_tokens and get_agent_prompt tools are public - anyone can call them for a system the owner has published. The design-scoped tools (get_design_handoff, get_design_prompt_pack, import_design_artifacts, finish_external_design) need the design's own handoff key, a Bearer token the design's owner shares with you directly. Pass it per call as the handoffKey argument, or set it once as the DESIGNFLOW_HANDOFF_KEY environment variable and every design-scoped tool call falls back to it.
curl https://brandpilot.dev/api/v1/systemscurl https://brandpilot.dev/api/v1/systems/launchwp/agent-promptFull endpoint reference, response shapes, and a ZIP-bundle walkthrough live in the integration guide.