Logo.dev for AI agents
Logo.dev is a logo and brand database API that returns official high-resolution logos and brand details for a given company domain. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Logo.dev.
Fetch a company's logo
Pull the official logo image for a domain to use in a partner page or invoice.
Search for a brand by name
Search the brand database to find the right domain match for a company name, read-only.
Verify a logo before publishing
Check a fetched logo's details before it is used publicly, since brand assets need accuracy.
2 Logo.dev actions, graded by risk.
Every Logo.dev action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- logo_dev.search_brandSearch Brand
- logo_dev.get_logo_imageGet Logo Image
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Logo.dev in three steps.
- 01Your users connect Logo.devThey add their Logo.dev api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Logo.dev through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('logo_dev', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Logo.dev connects.
Users add their Logo.dev api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Logo.dev connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Logo.dev from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Logo.dev and Arc0, answered.
Can I use Logo.dev with Claude, ChatGPT or Cursor?
Yes. Connect Logo.dev to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Logo.dev actions you allow.
How do users connect Logo.dev?
Users add their Logo.dev api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Logo.dev actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Logo.dev?
Yes. Allow read actions and deny writes in the Logo.dev policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Logo.dev too?
Yes. The same Logo.dev connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Logo.dev into your agent.
Your users connect Logo.dev once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan