Logo.dev MCP Server

Logo.dev MCP is an MCP integration. Look up company logos and brand data via the logo.dev API.

Packages and local setup

The published pypi package is logodev-mcp, version 1.1.0. Its declared MCP transport is stdio.

The package declares FASTMCP_LOG_LEVEL: Log level (DEBUG, INFO, WARNING, ERROR); LOGODEV_MCP_SERVER_NAME: MCP server name shown to clients; LOGODEV_MCP_BEARER_TOKEN: Bearer token for authentication; LOGODEV_MCP_AUTH_MODE: OIDC auth mode: 'remote' (JWKS validation) or 'oidc-proxy' (OAuth proxy). Auto-detected if not set.; LOGODEV_MCP_BASE_URL: Public base URL of this server (required for OIDC); LOGODEV_MCP_OIDC_CONFIG_URL: OIDC discovery endpoint URL; LOGODEV_MCP_OIDC_CLIENT_ID: OIDC client ID; LOGODEV_MCP_OIDC_CLIENT_SECRET: OIDC client secret; LOGODEV_MCP_OIDC_JWT_SIGNING_KEY: Signing key for OIDC session JWTs (critical on Linux/Docker); LOGODEV_MCP_OIDC_AUDIENCE: Expected OIDC token audience; LOGODEV_MCP_OIDC_REQUIRED_SCOPES: Space-separated required OIDC scopes.

The published oci package is ghcr.io/pvliesdonk/logodev-mcp:v1.1.0. Its declared MCP transport is streamable-http.

The package declares FASTMCP_LOG_LEVEL: Log level (DEBUG, INFO, WARNING, ERROR); LOGODEV_MCP_KV_STORE_URL: Persistent-state backend URL for pvl-core subsystems. Schemes: file:///path (survives restarts), memory:// (dev/ephemeral).; LOGODEV_MCP_SERVER_NAME: MCP server name shown to clients; PUID: Run as this UID (Docker entrypoint); PGID: Run as this GID (Docker entrypoint); LOGODEV_MCP_BEARER_TOKEN: Bearer token for authentication; LOGODEV_MCP_AUTH_MODE: OIDC auth mode: 'remote' (JWKS validation) or 'oidc-proxy' (OAuth proxy). Auto-detected if not set.; LOGODEV_MCP_BASE_URL: Public base URL of this server (required for OIDC); LOGODEV_MCP_OIDC_CONFIG_URL: OIDC discovery endpoint URL; LOGODEV_MCP_OIDC_CLIENT_ID: OIDC client ID; LOGODEV_MCP_OIDC_CLIENT_SECRET: OIDC client secret; LOGODEV_MCP_OIDC_JWT_SIGNING_KEY: Signing key for OIDC session JWTs (critical on Linux/Docker); LOGODEV_MCP_OIDC_AUDIENCE: Expected OIDC token audience; LOGODEV_MCP_OIDC_REQUIRED_SCOPES: Space-separated required OIDC scopes.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.