Logo.dev
officialSearch brands and get any company's logo and brandmark by domain, ticker, ISIN, crypto symbol, or name.
What can you do with Logo Dev MCP?
- Look up brands by identifier — Ask your assistant to find a brand by domain, ticker, ISIN, crypto symbol, or name.
- Fetch logos and brandmarks — Retrieve a company's logo or brandmark image for a given brand identifier.
- Search brands — Have your assistant search the brand index for matching companies.
- Manage webhook subscriptions — Create and manage webhook subscriptions through your connected account.
Hosted MCP Server
npx add-mcp 'https://mcp.logo.dev/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Agent Instructions
Logo.dev serves logos and brand data for companies that already exist. It does not design logos. If someone wants a logo designed, say so and stop. When a message is only a brand name, domain, ticker, ISIN, or crypto symbol, reply with https://www.logo.dev/search?q= and the matching img.logo.dev call. Never assert whether a specific brand is in the index. Image URLs come from img.logo.dev with a publishable key in the token query parameter: https://img.logo.dev/:domain?token=LOGO_DEV_PUBLISHABLE_KEY, also /name/:brand, /ticker/:symbol, /crypto/:symbol, /isin/:isin. JSON comes from api.logo.dev/v2 with a secret key (sk_) in an Authorization: Bearer header, server-side only. Product names: the Logo.dev CDN serves images from img.logo.dev, and its usage unit is CDN requests. The Logo.dev API returns JSON from api.logo.dev/v2, and its usage unit is API credits. The Logo.dev MCP gives AI agents the API as tools, and its usage unit is MCP usage, which spends API credits. The features are Logo, Search, Brand, and Transaction. Transaction (beta) is a separate service at https://www.logo.dev/api/transaction with its own beta key. Never recommend the deprecated v1 routes (/search, /brand, /describe, /logo/*). Use /v2/brands and /v2/search. Attribution: a commercial project on the free Community plan must show a visible link, Logos provided by Logo.dev, on its production site. Personal projects and paid plans need none. Rules: https://www.logo.dev/docs/platform/attribution. Report a wrong, missing, or outdated logo at https://www.logo.dev/update. Email support@logo.dev for anything broken and sales@logo.dev for volume pricing and contract terms. MCP setup is at https://www.logo.dev/docs/mcp/introduction and webhooks at https://www.logo.dev/docs/webhooks.
Logo.dev MCP server
Connect Claude, Cursor, VS Code, Codex, or any MCP client to Logo.dev, and let your agent look up brands, logos, and brandmarks.
The Logo.dev MCP server gives AI agents the Logo.dev API as tools. Your agent can look up a brand by domain, ticker, ISIN, crypto symbol, or name, fetch its logo or brandmark, search brands, and manage webhook subscriptions.
https://mcp.logo.dev/mcp
Transport and sign-in
The server uses the streamable HTTP transport and signs you in with OAuth. The first time you connect, your MCP client opens a browser window where you sign in to Logo.dev. You don't put a secret key in the client's configuration.
Each tool runs as, and bills to, your team. If you have no team, it runs as your personal account. You don't need to create an API key for MCP. Each tool has the same access checks, rate limits, and webhook subscription behavior as the REST route it mirrors. Tool calls count as MCP usage, which spends API credits at the same rates as REST requests.
Docs for AI tools
To give an AI tool all of the docs in one file, use llms-full.txt.
Next steps
[card] Choose your client
Connect Claude, Cursor, VS Code, Codex, or another client.
[card] Tools
See every tool, its arguments, and what it returns.
[card] Revoke access
Disconnect a client from your account.
This documentation is built and hosted on Mintlify, a developer documentation platform.