Logo.dev review, pricing and limits

Any company's logo, brandmark, colours and socials for an agent, by domain, ticker or name, over MCP or REST.

  • data
  • media
  • integration
  • developer

Use Logo.dev when an agent must place correct logos and brand colours into pages, decks, CRMs or directories and you want it reached by OAuth with no key handling. It is brand assets, not firmographics or contacts; pair it with an enrichment skill for those. Free API and MCP access makes the trial costless.

Logo.dev is a brand-data API that returns a company's logo, brandmark, hex colours and social handles for a domain, stock ticker, ISIN, crypto symbol or name. Agents use it through mcp.logo.dev, a hosted Model Context Protocol server with OAuth sign-in and 14 tools mirroring the v2 REST routes, including search, brand lookup, image retrieval, subscriptions and webhook endpoints.

Maker: Logo.dev · Protocol: MCP · Auth: oauth

Compatible agents: Claude Code (user-scope HTTP server), Claude Desktop and claude.ai (custom connector), Cursor, VS Code with GitHub Copilot, Codex CLI (codex mcp add, then codex mcp login), Any streamable-HTTP MCP client

Required runtime: Any MCP client with streamable HTTP and OAuth (the docs cover Claude, Cursor, VS Code Copilot and Codex), Any HTTP client for the REST API, Nothing to install; the server is hosted

About Logo.dev

Logo.dev is a brand-data service that most developers meet as an image URL: put a domain after img.logo.dev and a company's logo comes back. The skill side is newer. A hosted Model Context Protocol server at mcp.logo.dev gives Claude, Cursor, Codex, VS Code or any streamable-HTTP client a tool for every route of the v2 API, so an agent asked to add a partner's logo and brand colours to a page can search the company by name, fetch the brand record with real hex values, pull the square brandmark or the wide wordmark lockup, and subscribe to change events, all without the user pasting a key. Sign-in is OAuth in the browser; the server answers an unauthenticated call with a 401 that points the client at its OAuth metadata, and the client starts the flow itself.

The two products are metered separately. The CDN at img.logo.dev counts requests against a monthly allowance and needs only a publishable key in the URL. The API at api.logo.dev/v2 spends API credits, one credit being one cent, with a per-request price for a full brand record, a logo, a brandmark and a search, and MCP calls spend the same credits at the same rates. Lookups accept a domain, a stock ticker, an ISIN, a crypto symbol or a plain name, and a brand the service has never seen is indexed and returned within about half a minute, with a pending status in the meantime. Rate limits are two pools, one for brand and image lookups (per minute plus concurrent requests) and one for search, reported in RateLimit headers on every response; the MCP tools draw on the same allowance and return a retry-in-a-minute error when it is hit. Anything the API returns, logo files included, may be cached and served from your own infrastructure on every plan.

For agents the natural jobs are small and frequent: decorating a CRM or directory record with the right logo, resolving a messy company name to a domain before an enrichment call, pulling brand colours for a generated slide or landing page, and keeping a partner wall current through brand.updated webhooks. On HokAI it pairs with the contact-data skills rather than competing with them: Hunter and Tomba return firmographics and people for a domain but not usable brand assets, Riveter can fill a logo column but does so through its own agents, and Composio is the kind of gateway where an agent would combine a Logo.dev lookup with a CRM write. The Google Sheets skill is where many of the resulting brand tables live.

Plans are a free Community tier and two self-serve paid tiers plus Enterprise, differing in the monthly CDN allowance, the included API credits, whether more credits can be bought, per-minute limits, team seats and whether commercial projects must show a "Logos provided by Logo.dev" attribution. Webhook subscriptions have per-plan caps, and webhook-changing tools need an owner or admin role on the team.

The documentation is agent-ready in the literal sense: an llms.txt index, a per-client MCP setup guide, a tools page that maps every tool to its REST route and arguments, and a paste-this-into-your-agent onboarding prompt on the product page. If you are deciding how a product should source logos, brand data or company enrichment, Smart Match asks the questions that settle it.

Key Features

  • A tool for every v2 route: Search, brand, logo, brandmark, three subscription tools and seven webhook-endpoint tools, returning the same data and metadata as REST.
  • OAuth with no key to paste: The hosted server answers an unauthenticated call with OAuth metadata, so the client signs the user in by itself.
  • Five identifier types: Lookups accept domains, tickers, ISINs, crypto symbols and plain names, all drawing on one rate-limit pool.
  • Indexed in about half a minute: A brand the service has never seen returns a pending status and is processed in roughly 30 seconds, per the vendor.
  • Real brand colours and socials: The brand record carries hex colours, social handles, banners and freshness, not just an image.
  • Change webhooks: Subscribe to a brand and receive brand.updated deliveries, with signed endpoints and secret rotation.
  • Cache and self-serve: Logo files and records may be stored and served from your own CDN on every plan.

Use Cases

  • Partner wall from a list of names: For each partner, search by name, confirm the domain, fetch the brand record and brandmark URL, then subscribe so the page updates when the brand changes.
  • Logos for a generated deck or landing page: The agent pulls the wide logo and primary colour for each company mentioned and writes them into the template with real hex values.
  • Name cleanup before enrichment: Resolve a messy company name or a ticker to a canonical domain with search or brand, then hand the domain to Hunter or Tomba.
  • CRM record decoration: On record creation, look the account up by domain and store the logo URL and colours; webhooks keep them current.

Install

claude mcp add --transport http logo-dev https://mcp.logo.dev/mcp

Requirements

  • A Logo.dev account (free Community plan, no card); the MCP server signs you in by OAuth and never asks for a key
  • For REST calls: a secret key for api.logo.dev and a publishable key for img.logo.dev, from the dashboard
  • Webhooks enabled on the account for the subscribe and webhook-endpoint tools, and an owner or admin role to change endpoints
  • Attribution ("Logos provided by Logo.dev") on commercial projects while on the free plan

Actions

Search

Finds candidate brands by name, with match or typeahead ranking, and returns each candidate's domain.

{ "q": "Stripe", "method": "match", "limit": 5 }
  • q (string) — required: The company name to look for.
  • method (string): Ranking: match or typeahead.
  • limit (number): Candidates to return.

Brand

Looks a brand up by exactly one identifier (domain, ticker, ISIN, crypto symbol or name) or by brand_id, returning name, description, colours, socials and images.

{ "ticker": "AAPL", "nosubscribe": true }
  • domain (string): Website domain, e.g. lego.com.
  • ticker (string): Stock ticker.
  • isin (string): Security ISIN.
  • crypto (string): Crypto symbol.
  • name (string): Company name.
  • brand_id (string): Stable brand id in place of an identifier.
  • nosubscribe (boolean): Do not auto-subscribe to the brand's updates.

Logo

Gets a brand's wide logo with wordmark as a temporary download URL with dimensions and blurhash.

{ "domain": "lego.com" }
  • domain (string): One identifier: domain, or ticker, isin, crypto or name instead.
  • ticker (string): Alternative identifier.
  • name (string): Alternative identifier.

Brandmark

Gets a brand's square mark; returns a short-lived download link plus size and blurhash.

{ "name": "Shopify" }
  • domain (string): Identifier; exactly one of domain, ticker, isin, crypto or name.
  • isin (string): Alternative identifier.
  • crypto (string): Alternative identifier.

Subscription

Checks whether the account is subscribed to a brand's update events.

{ "brand_id": "brand_ctpx7djvd15596p3fe2zjkdrec" }
  • brand_id (string) — required: The brand's stable id.

Subscribe

Subscribes the account to brand.updated events for one brand, within the plan's follow limit.

{ "brand_id": "brand_8hq2kd0vx7m3" }
  • brand_id (string) — required: Brand to follow.

Unsubscribe

Stops update events for a brand; confirms the unsubscribed state either way.

{ "brand_id": "brand_z41pq9ab" }
  • brand_id (string) — required: Brand to stop following.

Create Webhook Endpoint

Registers a URL to receive brand webhook deliveries.

{ "url": "https://hooks.example.com/logo-dev", "description": "partner wall refresh", "events": ["brand.updated"] }
  • url (string) — required: HTTPS endpoint to deliver to.
  • description (string): Label.
  • events (array): Event types to deliver.

Webhook Endpoints

Lists the team's webhook endpoints.

{}

Webhook Endpoint

Gets one webhook endpoint.

{ "id": "ep_7f3a" }
  • id (string) — required: Endpoint id.

Update Webhook Endpoint

Changes an endpoint's URL, description or events.

{ "id": "ep_1a2b", "url": "https://alerts.example.org/brands" }
  • id (string) — required: Endpoint to change.
  • url (string): New delivery URL.
  • description (string): New label.
  • events (array): New event list.

Delete Webhook Endpoint

Deletes an endpoint and returns its id with deleted true.

{ "id": "ep_2c9d" }
  • id (string) — required: Endpoint to remove.

Webhook Endpoint Secret

Reads an endpoint's signing secret for verifying deliveries.

{ "id": "ep_9d44" }
  • id (string) — required: Endpoint whose secret to read.

Rotate Webhook Endpoint Secret

Replaces an endpoint's signing secret.

{ "id": "ep_5b1e" }
  • id (string) — required: Endpoint to rotate.

How to Invoke

Hosted MCP server at https://mcp.logo.dev/mcp (streamable HTTP, browser OAuth, no API key) with 14 tools, one per v2 route; or REST at https://api.logo.dev/v2 with a secret key, plus the img.logo.dev CDN with a publishable key for direct image URLs.

Pricing

Monthly plans, two months free on yearly (logo.dev/pricing, read 11 October 2026). Community: $0, 500,000 Logo CDN requests a month as a hard cap, $5 of API credits a month, API and MCP access, attribution required on commercial projects, community support. Startup: $33 a month, 1,000,000 CDN requests, $15 of API credits, team invites, no attribution. Pro: $150 a month, 5,000,000 CDN requests, $150 of API credits, extra credits purchasable. Enterprise: custom. One API credit is one cent; per request the Brand record costs $0.05, a wide logo $0.03, a brandmark $0.02 and a search $0.00001, and MCP tool calls spend the same credits. Everything the API returns may be cached and self-served on every plan.

Strengths

  • The free plan includes API and MCP access with a monthly credit grant, so an agent integration costs nothing to prove.
  • Tools return structured records with real hex values, which stops models from guessing brand colours.
  • The documentation maps every tool to its REST route, arguments and error behaviour on one page.

Weaknesses

  • Lookups are capped at 100 requests a minute and 5 concurrent below the Pro plan, so bulk decoration must be paced.
  • Credit and rate-limit headers are REST-only; an MCP tool reports a limit only when it is hit.
  • Commercial projects on the free plan must display attribution, and the CDN cap is hard until the month resets.

Frequently Asked Questions

What does Logo.dev cost, and what is free?

The Community plan is free with no card: 500,000 CDN requests a month, $5 of API credits, full API and MCP access, and an attribution link on commercial projects. Startup is $33 a month for 1,000,000 CDN requests and $15 of credits with no attribution, Pro is $150 for 5,000,000 requests and $150 of credits plus the right to buy more. Per request, a brand record costs 5 cents, a logo 3, a brandmark 2 and a search a hundredth of a cent.

How does an agent connect to Logo.dev without an API key?

Add the hosted server at mcp.logo.dev as a streamable-HTTP MCP server, for example with claude mcp add in Claude Code or codex mcp add followed by codex mcp login. The first call returns OAuth metadata instead of an error page, the client opens the browser sign-in, and from then on the tools run under your account. The product page even provides a paste-in prompt that walks the agent through setup and a test search.

Which clients and agents are supported?

The docs carry setup pages for Claude Code, Claude Desktop and web, Cursor, VS Code with GitHub Copilot and the Codex CLI, plus a generic page for any client that supports streamable HTTP and OAuth. Agents without MCP call the REST API with a secret key or load logos straight from the CDN with a publishable key.

When would a different data skill fit better?

If you need firmographics, employees or verified emails for a company, Hunter or Tomba return those and Logo.dev does not. If a whole table of attributes must be filled with sources, Riveter's enrichment runs do that. Logo.dev is the right call only when the deliverable is the brand asset itself.

Logo.dev or Hunter for company records in an agent?

They answer different questions about the same domain. Hunter tells the agent who works there and how to reach them, with verification scores. Logo.dev tells it what the company looks like: logo, brandmark, colours, socials, and a webhook when any of that changes. Most record-building agents call both, Hunter for the people columns and Logo.dev for the visual ones.

Top Alternatives

  • Hunter: Pick Hunter for the people and emails behind a domain; pick Logo.dev for the logo, colours and socials you can actually render.
  • Tomba: Tomba's autocomplete and company enrichment overlap with Logo.dev search, but only Logo.dev returns usable brand images and hex colours.

More Agent Skills on HokAI

View the official Logo.dev skill page