Logodev MCP Server

Logo.dev MCP

Look up company logos and brand data via the logo.dev API.

Documentation | Config wizard | PyPI | Docker

Features

• Logo retrieval (get_logo) — fetch a company logo as an image plus URL by domain, ticker, ISIN, crypto symbol, or brand name; supports size, format, theme, greyscale, retina, and fallback options. Requires a publishable key (pk_…).
• Brand search (search_brands) — resolve a brand or company name to candidate domains and logo URLs via typeahead or exact-match. Requires a secret key (sk_…).
• Company description (describe_company) — return structured company data (name, description, brand colours, social links) for a domain. Requires a secret key (sk_…).
• Full brand profile (get_brand) — return the complete brand profile (logo, brandmark, banners, colours, description) for a domain — a richer superset of describe_company. Requires a secret key (sk_…).
• Graceful degradation — tools are registered only when the corresponding API key is present; missing-key tools are hidden from the MCP client rather than registered and failing at call time.

What you can do with it

With this server mounted in an MCP client (Claude, etc.), you can:

• Fetch a logo — "Get the logo for stripe.com." Uses get_logo (publishable key required).
• Identify a brand's domain — "What domain is behind the brand 'Stripe'?" Uses search_brands (secret key required).
• Look up company info — "What colours does Stripe use in their branding?" Uses describe_company (secret key required).
• Get the full brand kit — "Show me the complete brand profile for shopify.com." Uses get_brand (secret key required).
• Logo by ticker — "Fetch the logo for AAPL." Uses get_logo with identifier_type=ticker (publishable key required).

Installation

From PyPI

pip install logodev-mcp

If you add optional extras via the PROJECT-EXTRAS-START / PROJECT-EXTRAS-END sentinels in pyproject.toml, document them below:

From source

git clone https://github.com/pvliesdonk/logodev-mcp.git
cd logodev-mcp
uv sync --all-extras --all-groups

Docker

docker pull ghcr.io/pvliesdonk/logodev-mcp:latest

A compose.yml ships at the repo root as a starting point — copy .env.example to .env, edit, and docker compose up -d.

To attach a remote Python debugger (development only — the protocol is unauthenticated), see Remote debugging.

Linux packages (.deb / .rpm)

Download .deb or .rpm packages from the GitHub Releases page. Both install a hardened systemd unit; env configuration is sourced from /etc/logodev-mcp/env (copy from the shipped /etc/logodev-mcp/env.example).

Claude Desktop (.mcpb bundle)

Download the .mcpb bundle from the GitHub Releases page and double-click to install, or run:

mcpb install logodev-mcp-<version>.mcpb

Claude Desktop prompts for required env vars via a GUI wizard — no manual JSON editing needed.

For manual Claude Desktop configuration and setup options, see Claude Desktop deployment.

Quick start

logodev-mcp serve                                # stdio transport
logodev-mcp serve --transport http --port 8000   # streamable HTTP

For library usage (embedding the domain logic without the MCP transport), import from the logodev_mcp package directly — see the project's domain modules under src/logodev_mcp/ for entry points.

Server info

The server registers a built-in get_server_info tool (via fastmcp_pvl_core.register_server_info_tool) so operators can confirm the deployed version with a single MCP call. The default response carries server_name, server_version, and core_version. Servers that talk to a remote upstream wire upstream version reporting inside the DOMAIN-UPSTREAM-START / DOMAIN-UPSTREAM-END sentinel in src/logodev_mcp/server.py — see CLAUDE.md for the wiring pattern.

Configuration

Core environment variables shared across all fastmcp-pvl-core-based services:

Domain-specific variables go below under Domain configuration.

Authentication

Callers authenticate via a bearer token or OIDC (mutually exclusive). See the Authentication guide for setup, mapped multi-subject tokens, OIDC, and troubleshooting.

Post-scaffold checklist

After copier copy and gh repo create --push:

1. Fill in the DOMAIN blocks in this README (Features, What you can do with it, Domain configuration, Key design decisions) and in CLAUDE.md.
2. Configure GitHub secrets — see below.
3. Install dev + docs tooling: uv sync --all-extras --all-groups.
4. Install pre-commit hooks: uv run pre-commit install.
5. Run the gate locally: uv run pytest -x -q && uv run ruff check --fix . && uv run ruff format . && uv run mypy src/ tests/.
6. Push the first commit — CI should be green.

GitHub secrets

CI workflows reference three repository secrets. Configure them via Settings → Secrets and variables → Actions or with gh secret set:

gh secret set RELEASE_TOKEN
gh secret set CODECOV_TOKEN
gh secret set CLAUDE_CODE_OAUTH_TOKEN

GITHUB_TOKEN is auto-provided — no action needed.

Local development

The PR gate (matches CI):

uv run pytest -x -q                                  # tests
uv run ruff check --fix . && uv run ruff format .    # lint + format
uv run mypy src/ tests/                              # type-check

Pre-commit runs a subset of the gate on each commit; see .pre-commit-config.yaml for details, or CLAUDE.md for the full Hard PR Acceptance Gates.

Troubleshooting

Moving a scaffolded project

uv sync creates .venv/bin/* scripts with absolute shebangs pointing at the venv Python. If you move the repo after scaffolding (mv /old/path /new/path), uv run pytest fails with ModuleNotFoundError: No module named 'fastmcp' because the stale shebang resolves to a different interpreter than the venv's site-packages.

Fix:

rm -rf .venv
uv sync --all-extras --all-groups

uv run python -m pytest also works as a one-shot workaround (bypasses the stale entry-script shim).

uv.lock refresh after copier update

When copier update introduces new dependencies (e.g. a new extra added to pyproject.toml.jinja), CI runs uv sync --frozen which fails against a stale lockfile. Run uv lock locally and commit the refreshed uv.lock alongside accepting the copier-update PR.

Links

• Documentation
• llms.txt
• FastMCP
• fastmcp-pvl-core

Domain configuration

Domain environment variables use the LOGODEV_MCP_ prefix:

At least one key must be set for any API tool to be registered. Both keys may be set simultaneously to enable all four tools.

Key design decisions

• Two-key gating — LOGODEV_MCP_PUBLISHABLE_KEY controls get_logo; LOGODEV_MCP_SECRET_KEY controls search_brands, describe_company, and get_brand. Tools for a missing key are never registered, not merely guarded at call time.
• Plan detection hides unentitled tools — describe_company needs a paid plan and get_brand needs Pro/Enterprise. logo.dev has no plan endpoint, so on startup the server probes each on logo.dev and disables the tool on a 401/403. search_brands is never gated; any ambiguous probe result (timeout, 5xx, 404, 429) fails open and keeps the tool enabled. The verdict is cached under LOGODEV_MCP_STATE_DIR for 7 days (re-probed on key rotation). Disable with LOGODEV_MCP_DETECT_PLAN=false.
• Domain logic stays FastMCP-free — src/logodev_mcp/domain.py contains the Service class and LogoDevError with no FastMCP imports; src/logodev_mcp/tools.py is the sole FastMCP layer.
• Errors surface as strings — LogoDevError raised in domain code is caught in each tool wrapper and returned as a plain text message so the MCP client sees a readable error, not a server exception.
• Logo tool returns URL + image — get_logo returns both the CDN URL (text) and the image bytes (image content block) unless url_only=True, in which case only the URL string is returned.