Brandize

Brandize MCP server

Hosted MCP server for Brandize, an AI logo generator. It generates logos and full brand kits — lockups, favicons, social assets, print collateral — plus brand color palettes, SEO meta tags, and JSON-LD schema markup, and searches the Brandize design guides.

There is nothing to install. The server is remote and runs over streamable HTTP:

This repository holds the documentation and the Claude Code and Codex plugin (plugins/brandize) — the server itself is part of the Brandize application. Issues and questions about the MCP surface belong here.

Connect

Claude Code — plugin

/plugin marketplace add minim-l/brandize-mcp
/plugin install brandize@brandize

Codex — plugin

codex plugin marketplace add minim-l/brandize-mcp
codex plugin add brandize@brandize

Or install brandize from /plugins inside Codex.

Claude Code — CLI

claude mcp add --transport http brandize https://brandize.me/api/mcp

Clients that take a JSON config (Claude Desktop, Cursor, Windsurf)

{
  "mcpServers": {
    "brandize": {
      "type": "http",
      "url": "https://brandize.me/api/mcp"
    }
  }
}

MCP Inspector

npx @modelcontextprotocol/inspector
# transport: Streamable HTTP → https://brandize.me/api/mcp

Call echo first to confirm the endpoint is reachable.

Tools

Free, no account, rate-limited:

Paid — each mints a Stripe checkout link the user opens and pays in a browser. No card is stored and no call charges anyone on its own:

generate_logo asks the calling agent to collect a real brief — tier, style, colors, layout, surface, industry — and to take the user's explicit acceptance of the Terms and Privacy Policy before it will generate.

Tiers

The tier argument to generate_logo picks what gets delivered. Call get_pricing_tiers for the current prices and feature lists — they are set server-side, not hardcoded here.

The brand-kit tiers have fixed deliverables — generate_logo_variations refuses on a purchased one. Only COMPLETE accepts more alternates after payment.

A paid run, end to end

1. generate_logo → watermarked preview, a jobToken, a checkoutUrl, and the higher tiers on offer.
2. The user opens checkoutUrl and pays.
3. get_logo_result with that jobToken, polled every ~5 seconds — payment confirmation is not instant — until the status is paid.
4. Download the returned asset URL.

A refunded purchase reverts the job: get_logo_result reports pending_payment again and the asset URL stops resolving.

Registry listing

The official MCP Registry entry is me.brandize/brandize, published from server.json in the Brandize application repo and verified against the brandize.me domain.