Brandfetch MCP Server

Search brands and retrieve design assets, company data, other brand context from Brandfetch's API. The brandfetch mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

Full documentation: https://docs.brandfetch.com/mcp/overview

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• brand_search — Search for brands by name using Brandfetch's search index
• get_brand — Look up full brand data by domain, stock ticker, ISIN, or crypto symbol
• enrich_transaction — Identify a merchant brand from a credit-card or bank-statement string
• get_brand_context — Get LLM-ready brand context for a domain — voice, audience, positioning, style
• build_logo_urls — Construct Brandfetch Logo CDN URLs for one or more brands (no API call)
• get_asset_base64 — Fetch a Brandfetch CDN asset (logo, icon, symbol, image) as base64
• Cursor — Add to ~/.cursor/mcp.json (or the project .cursor/mcp.json):

Configuration

You will need one environment variable: YOUR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the brandfetch mcp server does with a few real requests.

When to reach for it

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Brandfetch's toolset — brand_search, get_brand, enrich_transaction and 4 more — is a fair guide to whether it matches your workflow. It is maintained by io.brandfetch; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Brandfetch's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.