Official Logo.dev MCP

dev.logoPublished by logo.devOfficial publisherv0.1.0Updated Oct 24, 2026

Find brands, logos and brandmarks, and manage brand subscriptions and webhooks with Logo.dev.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant find brands, logos and brandmarks, and manage Logo.dev brand subscriptions and webhooks.

What you can do
This remote MCP server connects an assistant to Logo.dev. According to its description, it supports finding brands, logos and brandmarks, and it also covers managing brand subscriptions and webhooks. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to look up brand or logo information, or when you want subscription and webhook settings for Logo.dev handled from within an assistant session instead of the web dashboard. Less relevant if you only need generic image search.
Requirements
A remote MCP endpoint at reached over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
The server requires OAuth authorization, so the assistant acts with the permissions granted to that account. It can manage brand subscriptions and webhooks, which are write operations that may change or delete existing configuration; review what the account is allowed to modify before connecting.

Installation

In SourceWeft

  1. Open Official Logo.dev MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.logo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "official-logo-dev": {
      "type": "http",
      "url": "https://mcp.logo.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Logo integrations