Blender integration through the Model Context Protocol
Nothing to run from here
Brandize is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
AI logo generation, brand color palettes, SEO meta tags, JSON-LD schema markup, and blog search.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http brandize-mcp https://brandize.me/api/mcp
# 2 — ask your agent for something these tools do
# echo, get_pricing_tiers, search_blog and 7 more
Brandize costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BRAll 1 server
brandize1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http brandize-mcp https://brandize.me/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Health check that returns the provided message verbatim, confirming the Brandize MCP endpoint is reachable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | Text to echo back unchanged. |
List Brandize service tiers with their price (USD) and included features. Read-only; nothing is purchased.
No parameter schema on file.
Search Brandize blog posts (logo design and branding guides) by keyword. Returns matching post titles, excerpts, and URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keyword(s) to match against post titles and content. |
Generate a 5-color brand palette from a base hex color and a harmony rule. Returns CSS custom properties, a Tailwind config snippet, or a plain hex list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseColor | string | yes | Base color as a 6-digit hex, e.g. "#3B82F6". |
| harmony | string | no | Color harmony rule used to derive the palette. |
| format | string | no | Output format for the palette. |
Generate an HTML <head> meta-tag block (title, description, canonical, robots, Open Graph, Twitter Card) from page details. All fields optional.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | Page title (<title> and og:title fallback). |
| description | string | no | Meta description (og:description fallback). |
| keywords | string | no | Comma-separated keywords. |
| author | string | no | Content author. |
| canonical | string | no | Canonical URL (also used for og:url). |
| robots | string | no | Robots directive, e.g. "index, follow". |
| ogTitle | string | no | Open Graph title; defaults to title. |
| ogDescription | string | no | Open Graph description; defaults to description. |
| ogImage | string | no | Open Graph / Twitter image URL. |
| ogType | string | no | Open Graph type, e.g. "website" or "article". |
| twitterCard | string | no | Twitter card type, e.g. "summary_large_image". |
Generate a JSON-LD <script> block for a schema.org type (LocalBusiness, Organization, WebSite, Article, FAQPage, or Product) from a flat data object. For FAQPage, pass data.items as [{ question, answer }].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | schema.org type to generate. |
| data | object | no | Fields for the chosen type, e.g. { name, url, description, telephone }. FAQPage uses { items: [{ question, answer }] }. |
Generate a brand logo. Before calling, collect a short design brief from the user — do not assume defaults: (1) which package/tier they want to buy, (2) visual style, (3) color scheme (a primary brand color, and a secondary/accent if they want one), (4) layout (icon-only, wordmark, horizontal-lockup, or stacked), (5) the primary surface it must read well on, and (6) the industry. Ask for anything
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | string | yes | Delivery tier — ask the user which package they want to buy; do not assume one. PREMIUM: full-resolution PNG, vector SVG and a commercial license. COMPLETE: adds alternate logo variations (assembled a |
| brandName | string | yes | The brand or product name. |
| whatItDoes | string | yes | One short phrase describing what the brand does. |
| industry | string | yes | Industry category — ask the user; use "other" only if it genuinely fits none. |
| style | string | yes | Visual style. Ask the user which style they want. |
| layoutIntent | string | yes | Logo layout (icon-only, wordmark, horizontal-lockup, stacked). Ask the user. |
| primaryUseSurface | string | yes | Primary surface the logo must read well on. Ask the user. |
| colorPrimary | string | yes | Dominant brand color as a 6-digit hex. Ask the user for their color scheme; if unsure, propose one and confirm. |
| colorSecondary | string | no | Optional secondary/accent color as a 6-digit hex. Offer it as part of the color scheme. |
| antiReference | string | no | Anything the logo should avoid looking like. |
Poll a logo job by its jobToken. Once payment has settled, returns a URL to download the full-resolution, watermark-free asset; otherwise a pending status. Read-only and safe to poll — after the user pays, keep polling every ~5 seconds for up to a few minutes (payment confirmation is not instant) until the status is paid.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobToken | string | yes | The jobToken returned by generate_logo. |
Generate alternate style directions for an existing generate_logo job. Free — no checkout — but limited to this job's free-preview credit (1 by default; a COMPLETE purchase grants 2 more, other tiers grant none). Returns the same kind of watermarked, low-res preview as generate_logo, plus how many free credits remain. Before any purchase, each result's variationId can be passed to buy_logo_variati
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobToken | string | yes | The jobToken returned by generate_logo. |
| count | integer | no | How many alternate-style variations to generate (1-3), capped by the free-preview credits remaining on this job. |
Purchase one of the alternate designs from generate_logo_variations instead of the original logo. Priced the same as the PREMIUM tier. Mints a short checkout link; once paid, the chosen variation becomes the job's deliverable — poll get_logo_result with the same jobToken to retrieve it. This is a paid purchase; the hosted checkout page collects the user's acceptance of the Terms of Service and Pri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobToken | string | yes | The jobToken returned by generate_logo. |
| variationId | string | yes | The variationId of the design to purchase, from generate_logo_variations. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Brandize or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Brandize can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.