How to connect Brandfetch to OpenClaw
Connect Brandfetch to OpenClaw with ClawLink: paste your Brandfetch key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
BrandfetchAPI KEYMCPBrandfetch offers an API that retrieves company logos, brand colors, and other visual assets, helping marketers and developers maintain consistent branding across apps.. Once connected, OpenClaw can read and act on Brandfetch from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Brandfetch access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Brandfetch setup: install one ClawHub skill, connect Brandfetch in the browser, and OpenClaw can call real Brandfetch actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Brandfetch.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Brandfetch
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Brandfetch?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Brandfetch in the ClawLink dashboard — paste your Brandfetch API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Brandfetch, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Brandfetch is connected in the dashboard, that agent calls the same 7 Brandfetch tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Brandfetch MCP for OpenClaw
Looking for a Brandfetch MCP server for OpenClaw? ClawLink connects Brandfetch to OpenClaw and exposes 7 Brandfetch tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Brandfetch integration works the same way.
What the OpenClaw Brandfetch integration can do
7 Brandfetch tools are ready for OpenClaw once the account is connected.
All 7 Brandfetch tools for OpenClaw
| Tool | What it does |
|---|---|
Get brand info brandfetch_get_brand_info | Retrieves brand information including logos, colors, fonts, and company details using a domain |
Get graphql version brandfetch_get_graphql_version | Retrieve the Brandfetch GraphQL API version |
Get taxonomy brandfetch_get_taxonomy | Retrieve Brandfetch's taxonomy via GraphQL API |
Get transaction info brandfetch_get_transaction_info | Converts payment transaction labels into detailed merchant brand information |
List subscribable events brandfetch_list_subscribable_events | Retrieve all available webhook event types that can be subscribed to via the Brandfetch GraphQL |
List webhooks brandfetch_list_webhooks | Retrieve a list of all webhooks via GraphQL API |
Search brands brandfetch_search_brands | Searches for brands by name and returns matching brand information including URLs and icons |
Try it: find the Brandfetch tool you need
Browse the 7 Brandfetch tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Brandfetch, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Brandfetch, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Brandfetch, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Brandfetch, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brandfetch working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Brandfetch API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Brandfetch account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Brandfetch. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Brandfetch actions to the runtime in a format your agent can reliably use. | 7 tools for Brandfetch are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Brandfetch to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Brandfetch in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Brandfetch key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Brandfetch skill but can't call the tools
The ClawHub skill teaches OpenClaw about Brandfetch, but the calls run through the ClawLink plugin and your connected account. Make sure Brandfetch is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Brandfetch from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Brandfetch tools
Brandfetch tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Brandfetch call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Brandfetch returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Brandfetch has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Brandfetch integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Brandfetch: link your Brandfetch account once in the browser and OpenClaw can call the Brandfetch API through 7 ready-made tools — no custom code or token handling.
How do I add Brandfetch to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Brandfetch skill from ClawHub, then you click Connect in the dashboard to authorize Brandfetch. OpenClaw calls the tools from the next message — no config files, and the Brandfetch key you paste is stored server-side instead of in your environment.
How long does it take to connect Brandfetch to OpenClaw?
About two minutes. Sign in, click Connect next to Brandfetch in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Brandfetch up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brandfetch working from chat.
OpenClaw installed the Brandfetch skill but can't call the tools
The ClawHub skill teaches OpenClaw about Brandfetch, but the calls run through the ClawLink plugin and your connected account. Make sure Brandfetch is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
