Brandfetch MCP

The Brandfetch MCP server exposes Brandfetch’s brand data tools to any AI assistant that supports the Model Context Protocol (MCP), including Claude, Cursor, Windsurf, Gemini CLI, and others. Once configured, the assistant can search for brands, retrieve logos, brand assets, and firmographics data. The MCP server is available at:

https://mcp.brandfetch.io/mcp

Authentication

The Brandfetch MCP server uses OAuth. When you add the server, your MCP client opens a browser window where you sign in with your Brandfetch account. If you don’t have an account yet, sign up for free; the free plan includes 100 requests per month.

My client doesn't support OAuth

If your MCP client doesn’t support OAuth, or you’re running in a non-interactive environment (CI, scripted agents), you can generate an MCP token in the Keys and MCP section of the Developer Dashboard and send it as a bearer token:

{
  "url": "https://mcp.brandfetch.io/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_MCP_TOKEN"
  }
}

Treat the token like a password: don’t share or commit it.

Setup

Connect the MCP server

In Claude Desktop or claude.ai, go to Settings → Connectors → Add custom connector and enter:

Name: Brandfetch
URL: https://mcp.brandfetch.io/mcp

Click Add, then Connect — a browser window opens to sign in with your Brandfetch account.

Allow network access for asset downloads (if available)

To download or embed logos and other brand assets, Claude’s code execution environment needs network access to Brandfetch’s CDN.If your plan offers it, go to Settings → Capabilities, enable network egress for code execution, and add *.brandfetch.io to the domain allowlist. Availability of this setting varies by Claude plan. See Downloading brand assets for what happens without it.

Run the following command to add the Brandfetch MCP server:

claude mcp add brandfetch --transport http https://mcp.brandfetch.io/mcp

Then run /mcp inside Claude Code, select brandfetch, and follow the authentication prompt to sign in.

Use the Command Palette and look for MCP: Add Server, choose HTTP, then use the URL above.Or create or open .vscode/mcp.json in your project and add:

{
  "servers": {
    "brandfetch": {
      "type": "http",
      "url": "https://mcp.brandfetch.io/mcp"
    }
  }
}

When the server starts, VS Code prompts you to sign in to Brandfetch.

Add the following to ~/.codex/config.toml (or .codex/config.toml inside your project):

[mcp_servers.brandfetch]
url = "https://mcp.brandfetch.io/mcp"

Or run the CLI command:

codex mcp add brandfetch --url https://mcp.brandfetch.io/mcp

Then sign in with:

codex mcp login brandfetch

Open Cursor Settings → MCP and add a new server:

{
  "mcpServers": {
    "brandfetch": {
      "url": "https://mcp.brandfetch.io/mcp"
    }
  }
}

Click Login next to the server entry to sign in with your Brandfetch account.

Open your Windsurf MCP configuration file and add:

{
  "mcpServers": {
    "brandfetch": {
      "url": "https://mcp.brandfetch.io/mcp"
    }
  }
}

Windsurf prompts you to sign in to Brandfetch when the server connects.

Available tools

Tool	Description
`brand_search`	Search for brands by name. Useful when the domain is unknown or ambiguous.
`get_brand`	Retrieve full brand data (logos, colors, fonts, company info) by domain, ticker, ISIN, or crypto symbol.
`get_brand_context`	Get LLM-ready brand context for a domain: voice, audience, positioning, and style. Use when generating content or reasoning about brand fit.
`enrich_transaction`	Identify a merchant brand from a raw credit card or bank statement string.
`build_logo_urls`	Construct Brandfetch CDN logo URLs for one or more brands without making an API call.
`get_asset_base64`	Fetch a CDN asset (logo, icon, symbol, image) as checksummed base64 — a last resort for sandboxed environments that can’t reach the CDN. Prefer fetching the `src` URLs from `get_brand` directly.
`send_feedback`	Send feedback about the MCP server (bugs, data quality, feature requests) to the Brandfetch team.

Downloading brand assets

When your assistant needs actual image bytes — embedding a logo in a generated document (PPTX, DOCX, PDF), saving files to disk, or processing pixels — the reliable path is to fetch the credentialed src URLs returned by get_brand directly from its code-execution environment (curl, requests, fetch). That keeps image bytes out of the conversation entirely.

Using Claude? Allowlist cdn.brandfetch.io first.On claude.ai (web, desktop, and mobile apps) sandboxed code execution can only reach domains permitted by your network-egress settings. When the Brandfetch CDN is blocked, Claude falls back to routing image bytes through the conversation as base64 (get_asset_base64), which is slower, can produce corrupted files, and drives up token usage and cost.To enable direct downloads, go to Settings → Capabilities, enable network egress for code execution, and add *.brandfetch.io to the domain allowlist (availability of this setting varies by Claude plan). We strongly recommend this for any workflow that downloads or embeds brand assets.

Note that URLs from build_logo_urls are display-only under the hotlinking policy and can’t be downloaded programmatically — always use the src URLs from get_brand, whose ?c= token carries per-request credentials. Reserve get_asset_base64 for environments where the CDN is truly unreachable.

Usage and quotas

MCP requests count against your Brand API quotas. You can monitor your usage in the Developer Dashboard.

General

Products

Accuracy

Delivery methods

Support

Authentication

Setup

Available tools

Downloading brand assets

Usage and quotas

​Authentication

​Setup

​Available tools

​Downloading brand assets

​Usage and quotas

Authentication

Setup

Available tools

Downloading brand assets

Usage and quotas