How to connect Logo dev to Claude

Connect Claude Web, Desktop and Cowork to Logo dev MCP. Fetch high-res logo for tesla.com, search brands in fintech industry, us only, and more using natural language, with authentication handled for you.

Logo dev logoLogo dev
Api Key

Logo.dev is an API and database for high-resolution company logos and brand metadata. Instantly fetch official logos from any domain without scraping or manual searching.

2 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Logo dev account to Claude via Composio Connect, enabling it to fetch high-res logo for tesla.com, search brands in fintech industry, US only, get the SVG logo for github.com, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Logo dev with

Connecting Logo dev to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Logo dev account

Back in Claude, ask it to connect to Logo dev or give it any Logo dev-related task.

For example, ask Claude to:

  • "Fetch high-res logo for tesla.com"
  • "Search brands in fintech industry, US only"
  • "Get the SVG logo for github.com"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Logo dev account is ready to use.

What is the Logo dev Claude Connector, and what's possible with it?

The Logo dev MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Logo.dev account. It provides structured and secure access to a vast company brand database, so your agent can fetch official high-res logos, search brands by name, filter by industry, and retrieve brand details—automatically, and on demand.

  • Instant logo retrieval: Effortlessly fetch high-resolution logo images for any company domain, ready for use in presentations, apps, or reports—no manual searching required.
  • Brand search by keyword: Let your agent search for brands using a query string and retrieve a list of matching companies with details, perfect for enriching datasets or verifying company info.
  • Industry and country filtering: Narrow down brand searches by specifying industry or country filters, so your agent can surface only the most relevant results.
  • Logo format selection: Enable your agent to request logos in the preferred format (SVG or PNG), making integration into various workflows seamless.

Troubleshooting

1. Why does Claude not use the Composio connector for Logo dev?

The connector can show as connected, but Claude must use it in each Logo dev conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Logo dev again.

2. Why does Claude show an MCP server error before Logo dev connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Logo dev.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Logo dev.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Logo dev authorization link not work?

The Composio connector is one server. Your Logo dev account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Logo dev connection.
  • Composio creates a fresh Logo dev authorization link.
  • Open that link in your browser and finish the Logo dev sign-in.

4. Why do Logo dev actions fail after they worked before?

The Logo dev connection can expire or lose permission.

  • Ask Claude to inspect the Logo dev connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Logo dev account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Logo dev.
  • If the action still fails with a permission error, check that the connected account has that permission in Logo dev itself.

5. How do I switch to a different Logo dev account?

Claude can manage the Logo dev connection for you.

  • Ask Claude to disconnect or delete the current Logo dev account.
  • Ask Claude to connect Logo dev again.
  • Open the new Composio authorization link for Logo dev.
  • Sign in with the other Logo dev account in the browser.
  • After the account connects, ask Claude to retry the Logo dev task.

6. Why is my Logo dev connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Logo dev connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Logo dev tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Logo dev.
TOOLS

Supported Tools

Every Logo dev action and event your agent gets out of the box.

Get Logo Image

Tool to retrieve the logo image for a domain.

Search Brand

Tool to search for brands based on a query string.

FAQ

Frequently asked questions

With a standalone Logo dev MCP server, the agents and LLMs can only access a fixed set of Logo dev tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Logo dev and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Logo dev tools.

Yes, absolutely. You can configure which Logo dev scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Logo dev data and credentials are handled as safely as possible.

Start with Logo dev.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Logo dev tool your agent needs.Free to start.

Start building