> ## Documentation Index
> Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## 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=<url-encoded term> 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 CDN serves images from img.logo.dev. The Logo API is the Brand API and the Search API, which return JSON from api.logo.dev/v2. The Transaction Enrichment API (beta) is a separate service at https://www.logo.dev/api/transaction with its own beta key. Credits is the Logo API billing unit. Never recommend the deprecated v1 routes (/search, /brand, /describe, /logo/*) or the Describe API. Use /v2/brands and /v2/search.
> 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 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.

```text theme={null}
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, [credits and rate limits](/docs/platform/rate-limits), and [webhook subscription](/docs/webhooks#subscriptions) behavior as the REST route it mirrors.

## Next steps

<CardGroup cols={2}>
  <Card title="Choose your client" icon="plug" href="/docs/mcp/clients">
    Connect Claude, Cursor, VS Code, Codex, or another client.
  </Card>

  <Card title="Tools" icon="wrench" href="/docs/mcp/tools">
    See every tool, its arguments, and what it returns.
  </Card>

  <Card title="Revoke access" icon="ban" href="/docs/mcp/revoke-access">
    Disconnect a client from your account.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.