Claude Brandfetch connectorWhat Claude can do in your Brandfetch account.
The Claude Brandfetch connector exposes 6 tools. 5 of them read brand data, 0 is documented as changing anything, and 1 is described by no source. Below: what Claude pulls into the chat, what blocks logo downloads, and where the publisher and the directory differ.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Brandfetch into Claude
You ask Claude for a pitch deck aimed at a prospect, and it comes back in generic blue. With Brandfetch connected, Claude looks up that company first: its logo files, its palette, its typefaces and the way it talks. What it writes next starts from how the brand really looks instead of a guess.
A deck that looks like the client. Before a sales meeting, get_brand returns the prospect's logos, colors and fonts from a domain, an email address or even a stock ticker. Claude then drafts the slides with the right hex codes rather than approximations.
Copy in the right register. get_brand_context gives Claude a summary of a company's voice, audience and positioning. Useful when a cold email has to sound like it was written by someone who knows the account.
A cleaner expense report. enrich_transaction turns a cryptic card-statement line into the merchant behind it, which helps when finance asks what an abbreviated charge on the company card was.
What it does not do, by default: according to its sheet, nothing in the listed tools edits your Brandfetch account, and one tool has no description anywhere. Logo downloads also hit a wall until network access is opened for Claude's code sandbox. Nothing runs on a schedule either; Claude calls these tools only while it answers you. If you want brand data to flow into another app on its own, that is an automation job, covered by our Brandfetch n8n integration page.
The words you will meet
Five terms, each explained once, so the rest of the page reads easily.
- Connector
- A link you set up once between Claude and an account you already own, so Claude can use that account while it answers.
- Tool
- One named action a connector gives Claude. Claude picks the ones it needs by itself, and the directory lists them by name.
- Authorization
- The Brandfetch sign-in window where you grant Claude the access it will use. Given once per person, and revocable the same way.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The open standard connectors rely on: the common language that lets an assistant like Claude call an outside service such as Brandfetch.
Connect Brandfetch to Claude in three steps
- 01
Open the connector list
In Claude's settings, go to Customize then Connectors and find Brandfetch. On a Team or Enterprise workspace, an Owner or Primary Owner must switch it on for the organization before anyone can sign in.
- 02
Sign in to Brandfetch
Press Connect on its row. Brandfetch opens its own window where you log in with your Brandfetch account. If the link breaks later, use Disconnect and plug it back in.
- 03
Check what you grant
Read the authorization screen before you accept. It is Brandfetch's page, not Claude's, and it decides what the access covers. You can also withdraw that access later from the Brandfetch side.
The 6 tools, split by what they do
Brandfetch gives Claude 6 tools: 5 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups here: what Claude reads, and one name no source explains. Tool names stay as Claude displays them.
- 5 read
- 1 not documented
What Claude reads (5)
5 toolsFive lookups into Brandfetch's brand index. None of them is documented as touching your account.
brand_search
Finds a company by its name when you do not know its web address, or when several firms share a similar label. Claude gets candidates back and can pick the right one before going further.
build_logo_urls
Assembles ready-made logo addresses on Brandfetch's CDN for one or several companies at once, without making an API call. Handy for showing a row of logos on a web page or a mock-up.
enrich_transaction
Takes the raw text of a card or bank statement line and tells Claude which merchant sits behind it. You get a recognisable company name instead of a truncated code.
get_brand
Pulls a company's complete identity from a domain, an email, a ticker, an ISIN or a crypto symbol: logos, colors, fonts and company facts. On claude.ai and Claude Desktop, Brandfetch says the answer shows up as an interactive card with tabs.
get_brand_context
Hands Claude a written portrait of a brand: tone of voice, target audience, positioning and style. Claude uses it as a brief before drafting text meant to sound like that company.
Undocumented (1)
1 toolListed on the directory sheet, missing from the publisher's tool table. We do not guess its role from its name.
get_asset_base64
This name appears on the directory sheet and nowhere in Brandfetch's own documentation. No official source describes it, so this page says nothing about its role.
What Claude asks before acting
By default, Claude pauses and asks before each action it takes on an account for someone, right in the conversation.
On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt every time. They can also narrow a connector for the whole organization, for example keeping reading open and closing writing, and nobody lifts that from a personal account. Claude works with the rights of the person who connected, nothing more. The official per-tool label, read only versus write and delete, only exists inside a signed-in account's settings.
Which plans include Brandfetch in Claude
None of the 819 sheets in the official directory states plan availability. That answer is not published anywhere, connector by connector.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members connect. Brandfetch's docs mention plans about a separate setting, network access; the limits section quotes it. For the live state, check the connector's sheet in the directory.
Where the Claude Brandfetch connector stops
A connector is not an automation. Claude calls these tools while replying, so nothing fires when a brand changes its logo.
A tool list that only shows reading is an observed floor, not a promise: an administrator can open actions that no public sheet lists. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools or vouch for how they behave. Everything known about this connector comes from Brandfetch's own documentation; no Claude help article covers it. For a case where official sources openly disagree, see our Claude gmail connector page.
Who can open the network access that logo downloads need?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner enables each connector first.
- Brandfetch MCP documentation ↗Read September 2026, undatedThe publisher says the network setting varies by Claude plan: users on Pro and Max change it themselves, while on Team and Enterprise it is an org-level setting for an Owner or Admin.
What this page followsThe two texts are not about the same thing: Anthropic's rule covers access to connectors, Brandfetch's line covers a Claude setting and it is the publisher speaking. Neither settles it for your account, so check the directory sheet and your own Claude settings.
Need help connecting Brandfetch to Claude?
A person reads every message.
