Connect your assistant.

Codex

Download and extract the plugin bundle. From the directory containing its brandbrain folder, register the marketplace and install the plugin. Start a new chat and connect BrandBrain when prompted.

codex plugin marketplace add ./brandbrain
codex plugin add brandbrain@brandbrain

Start a new conversation after installation. Open the client’s MCP connection controls, authenticate BrandBrain, review the connection request, and continue with Google. Return to the assistant when sign-in completes.

Connector only

codex mcp add brandbrain-flow-orchestrator --url https://api.brandbrain.dev/mcp
codex mcp login brandbrain-flow-orchestrator

This adds tools without the bundled skill. Use this instead of the plugin, or remove the bare entry before installing the plugin.

Claude Code

Download and extract the plugin bundle. From the directory containing its brandbrain folder, install the plugin. Open /mcp in Claude Code, select BrandBrain, and authenticate.

claude plugin marketplace add ./brandbrain
claude plugin install brandbrain@brandbrain

Start a new conversation after installation. Open the client’s MCP connection controls, authenticate BrandBrain, review the connection request, and continue with Google. Return to the assistant when sign-in completes.

Connector only

claude mcp add --transport http brandbrain-flow-orchestrator https://api.brandbrain.dev/mcp

Then use /mcp to authenticate. To try the plugin directly from the extracted bundle, run claude --plugin-dir ./brandbrain/plugins/brandbrain.

Claude

In Claude settings, open Connectors and add a custom connector named BrandBrain. Paste this URL, then connect. Custom connector availability depends on your plan and workspace settings.

https://api.brandbrain.dev/mcp

Claude’s custom connector adds remote tools but does not install the Claude Code plugin’s skill. Use the first-workflow prompt below and ask the assistant to validate and mock before generation. If your organization manages connectors, ask its administrator to enable the connection.

Your first workflow

List my BrandBrain flows and available templates. Help me plan an icon set, validate it, and run a mock. Return the canvas link. Ask before any paid generation.

1. Confirm access with list_asset_flow_templates, then look for existing work with list_asset_flows.
2. Choose a returned template and create or edit a flow. For an asset set, draft and approve the manifest.
3. Validate the saved flow and finish a mock run.
4. Inspect run status and outputs. Open the returned canvas_url to continue in BrandBrain.

Mock runs check the workflow without paid image generation. To retrieve an existing result, use get_flow_outputs. Regeneration starts another run and may incur charges.

Access, sign-in, and costs

The hosted connector uses browser OAuth with Google and PKCE. You review the requesting app and callback host before continuing. Approval permits flow reads, edits, and execution through your BrandBrain agent session; it is not a read-only connection. Normal backend permissions still apply.

Sign in through the client’s connection controls. The tools login_brandbrain and logout_brandbrain are for local stdio sessions; do not use them to manage a hosted connection. Disconnect or remove the connection in your client to remove its stored credentials. That does not revoke other sessions.

Live runs need configured provider credentials and a server-side per-run spending ceiling. The hosted gateway defaults to mock-only when no ceiling is configured. The bundled skill requires fresh confirmation before each paid provider call. A skill instruction is not a server-enforced consent control.

For your own local spending ceiling or a local backend, use the stdio MCP guide or the canvas Connections panel. Keep tokens and provider keys out of prompts and checked-in configuration.

Troubleshooting

Operator details: deployment and OAuth contract.