Skip to main content
Glama
NOVA-3951

Logo.dev MCP Server

by NOVA-3951
README.md
# Logo.dev MCP Server

An MCP (Model Context Protocol) server for the Logo.dev API that enables searching for and retrieving company logos. Ready for deployment on [Smithery](https://smithery.ai/).

## Features

- **Search for logos**: Search for company logos by brand or company name
- **Get logo URLs**: Retrieve direct logo image URLs with customization options
- **Multiple formats**: Support for PNG, JPG, and WebP formats
- **Theme variants**: Light and dark theme options
- **Customizable**: Size, format, theme, and greyscale options
- **Smithery Ready**: Deploy directly to Smithery with automatic configuration

## Tools

### `search_logos`

Search for company logos by brand name or company name.

**Parameters:**
- `query` (string, required): The brand or company name to search for

**Returns:** A list of matching companies with their domains and logo URLs.

**Example:**
```json
{
  "query": "Google",
  "count": 1,
  "results": [
    {
      "name": "Google",
      "domain": "google.com",
      "logoUrl": "https://img.logo.dev/google.com?token=..."
    }
  ]
}
```

### `get_logo_url`

Get a direct logo image URL for a specific domain with customization options.

**Parameters:**
- `domain` (string, required): The company domain (e.g., 'google.com')
- `size` (string, optional): Logo size/dimensions
- `format` (string, optional): Image format - "png", "jpg", or "webp" (default: png)
- `theme` (string, optional): Logo theme - "light" or "dark"
- `greyscale` (boolean, optional): Convert logo to greyscale (default: false)

**Returns:** Logo URL with the specified options.

**Example:**
```json
{
  "domain": "apple.com",
  "logoUrl": "https://img.logo.dev/apple.com?token=...&format=webp&theme=dark",
  "options": {
    "size": "default",
    "format": "webp",
    "theme": "dark",
    "greyscale": false
  }
}
```

## Smithery Deployment

This server is designed for [Smithery](https://smithery.ai/) deployment:

1. Push this code to a Git repository
2. Connect the repository to Smithery
3. Smithery will automatically detect the TypeScript runtime
4. Enter your Logo.dev API key when prompted
5. Deploy and use!

## Local Usage

### Prerequisites

- Node.js 20 or higher
- A Logo.dev API key (get one at [logo.dev](https://logo.dev))

### Installation

```bash
npm install
npm run build
```

### STDIO Mode (for Claude Desktop)

```bash
export LOGO_DEV_API_KEY="your-api-key-here"
node build/index.js
```

### Claude Desktop Configuration

Add to your Claude Desktop config file (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "logo-dev": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-logo-dev/build/index.js"],
      "env": {
        "LOGO_DEV_API_KEY": "your-api-key-here"
      }
    }
  }
}
```

## Development

### Watch mode

```bash
npm run watch
```

### Testing with MCP Inspector

```bash
npm run inspector
```

## API Reference

This server uses the [Logo.dev API](https://docs.logo.dev/):
- Search endpoint: `https://api.logo.dev/search?q={query}`
- Image CDN: `https://img.logo.dev/{domain}`

## License

MIT

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_logo_url retrieves a specific logo for a given domain with customization options, while search_logos finds logos by brand/company name and returns a list of matches. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_logo_url and search_logos), using snake_case throughout. The naming is predictable and readable, with no deviations in style.

Tool Count3/5

With only 2 tools, the server feels thin for a logo service domain. While the tools cover basic retrieval and search, more operations like logo validation, batch processing, or metadata access could enhance completeness. The count is borderline for the apparent scope.

Completeness3/5

The server provides core lookup functionality (get and search), but there are notable gaps. For a logo service, operations like logo upload, update, deletion, or analytics are missing, limiting lifecycle coverage. Agents can work around this for basic tasks but may fail on advanced workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues