← All integrations

Logo.dev MCP server

14 operations0 webhooks

Look up company logos and brand profiles (name, colors, socials, logo files) by domain, ticker, ISIN, crypto symbol or name, search brands by name, and manage brand update webhooks.

Try Logo.dev with your agent

Connect Logo.dev, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Logo.dev on my account, then run one read-only example and show me the result.

Runs once, when you ask

Logo.dev tools and triggers

Tools are what your agent can do in Logo.dev through Corsair's MCP server. Triggers are the Logo.dev events a routine can start from.

Webhook Endpoints

  • CreateWrite

    Register a URL to receive brand.updated and brand.indexed events (paid plans).

    webhookEndpoints.create

  • DeleteDestructive

    Delete a webhook endpoint. This cannot be undone.

    webhookEndpoints.delete

  • GetRead-only

    Get one webhook endpoint.

    webhookEndpoints.get

  • ListRead-only

    List the team's webhook endpoints.

    webhookEndpoints.list

  • UpdateWrite

    Change a webhook endpoint's URL, description, event types or disabled state.

    webhookEndpoints.update

Brands

  • GetRead-only

    Get a brand profile by its Logo.dev brand id. 5 API credits.

    brands.get

  • LookupRead-only

    Look up a brand profile (name, description, colors, socials, logo) by domain, ticker, ISIN, crypto symbol or name. 5 API credits.

    brands.lookup

  • SearchRead-only

    Search brands by name and get each match with its domain and logo URL. Billed at 1 API credit per 1,000 searches.

    brands.search

Subscriptions

  • GetRead-only

    Check whether the account follows a brand's update events (paid plans).

    subscriptions.get

  • SubscribeWrite

    Follow a brand's update events (paid plans with webhooks).

    subscriptions.subscribe

  • UnsubscribeWrite

    Stop following a brand's update events.

    subscriptions.unsubscribe

Logos

  • FetchRead-only

    Get a brand's logo as a temporary download URL with its size, format and blurhash. 2 API credits.

    logos.fetch

Connect Logo.dev to Claude, ChatGPT or Cursor

  1. 1

    Connect Logo.dev in Corsair

    Add your Logo.dev API key once in Corsair. Corsair stores the credential encrypted and makes the Logo.dev API calls for your agent, so it never goes into a prompt or a config file. Connect Logo.dev

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Logo.dev. On a ChatGPT personal plan, connect Logo.dev here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Logo.dev's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/logodev, add the Logo.dev plugin, and connect with an API key. Then call methods like corsair.logodev.api.account.get() from your app. Corsair syncs data per tenant.

Yes. Logo.dev requires an API key from your Logo.dev account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Logo.dev, GitHub, Notion, Stripe, and the rest. Trigger Logo.dev from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for look up company logos and brand profiles (name, colors, socials, logo files) by domain, ticker, ISIN, crypto symbol or name, search brands by name, and manage brand update webhooks. Common builds include sync jobs, admin tooling, and agents that call Logo.dev APIs from your backend. Local DB entities let you query synced Logo.dev records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Logo.dev API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/logodev in the open repo. When Logo.dev ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Logo.dev data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Logo.dev data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Logo.dev on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive Logo.dev operation. You can change a link's mode at hub.corsair.dev/me.