Logo.dev MCP integration for AI agents.
Connect AI agents to Logo.dev through 7 structured actions, including describe brand, get logo by crypto, and get logo by domain. Review authentication, inpu…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Logo.dev integration exposes
The Logo.dev Agent App exposes 7 provider-backed actions for design & media and developer tools work. Its current contract lets an authorized agent fetch structured logo.dev brand metadata for a domain, build a logo.dev image url for a crypto symbol, and build a logo.dev image url for a company domain. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Logo.dev account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Logo.dev capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
describe_brandREADFetch structured Logo.dev brand metadata for a domain.
INPUTS: domain
get_logo_by_cryptoREADBuild a Logo.dev image URL for a crypto symbol.
INPUTS: symbol / token / size / format / theme
get_logo_by_domainREADBuild a Logo.dev image URL for a company domain.
INPUTS: domain / token / size / format / theme
get_logo_by_isinREADBuild a Logo.dev image URL for an ISIN identifier.
INPUTS: isin / token / size / format / theme
get_logo_by_nameREADBuild a Logo.dev image URL for a brand name.
INPUTS: brandName / token / size / format / theme
get_logo_by_tickerREADBuild a Logo.dev image URL for a stock ticker.
INPUTS: ticker / token / size / format / theme
search_brandsREADSearch Logo.dev brands by query text and return candidate brands.
INPUTS: query / strategy
INPUT CONTRACTS
Know what the action needs before it runs.
describe_brand
domainOPTIONAL- The company domain to describe.
get_logo_by_crypto
symbolREQUIRED- The crypto symbol to look up.
tokenREQUIRED- The publishable Logo.dev token used to build the image URL.
sizeOPTIONAL- The requested logo size in pixels.
formatOPTIONAL- The requested output image format.
themeOPTIONAL- The logo theme to request from Logo.dev.
get_logo_by_domain
domainREQUIRED- The company domain to look up, for example openai.com.
tokenREQUIRED- The publishable Logo.dev token used to build the image URL.
sizeOPTIONAL- The requested logo size in pixels.
formatOPTIONAL- The requested output image format.
themeOPTIONAL- The logo theme to request from Logo.dev.
get_logo_by_isin
isinREQUIRED- The ISIN identifier to look up.
tokenREQUIRED- The publishable Logo.dev token used to build the image URL.
sizeOPTIONAL- The requested logo size in pixels.
formatOPTIONAL- The requested output image format.
themeOPTIONAL- The logo theme to request from Logo.dev.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Describe Brand
Fetch structured Logo.dev brand metadata for a domain. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
describe_brandVerify with Get Logo By Crypto
Build a Logo.dev image URL for a crypto symbol. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_logo_by_cryptoSAFETY BOUNDARY
Operate Logo.dev with explicit limits
- Authorize Logo.dev with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Logo.dev data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Logo.dev rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Logo.dev task completed successfully.
CONNECTION MODEL
API key
Logo.dev secret key used for search and describe requests. Create it in the API Keys dashboard and do not use a publishable key: https://www.logo.dev/dashboard/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Logo.dev.