OpenBrand
Pull logos, colors, backdrop images, and brand names from any site URL so landing pages and prototypes match real-world branding fast.
Overview
io.github.ethanjyx/openbrand is an MCP server for the Validate phase that extracts brand assets from any website URL through the OpenBrand API.
What is this MCP server?
- Extract logos, colors, backdrop images, and brand name from a website URL
- OpenBrand MCP npm openbrand-mcp v0.1.2 with stdio transport
- Requires OPENBRAND_API_KEY from openbrand.sh dashboard
- GitHub ethanjyx/openbrand mcp subfolder
- Speeds competitive or partner-brand reference for solo landing builds
- Version 0.1.2
- npm package openbrand-mcp
What problem does it solve?
You need accurate logos and colors from an existing site for a landing prototype but hate digging through devtools and asset folders.
Who is it for?
Indie builders cloning reference aesthetics for validation landers or white-label mocks with agent assistance.
Skip if: Teams needing full trademark clearance, custom illustration systems, or offline brand books without web sources.
What do I get? / Deliverables
Your agent returns structured brand elements from a URL so prototypes and early UI pick up real palette and logo cues quickly.
- Extracted logos, colors, backdrop images, and brand name metadata
- Agent-ready brand references for prototype UI
- Faster visual parity on validation landers
Recommended MCP Servers
Journey fit
How it compares
Brand-asset extraction MCP API, not a Figma plugin or generic screenshot skill.
Common Questions / FAQ
Who is openbrand for?
Solo developers and marketers using MCP agents who prototype sites and want automated brand kit extraction from URLs.
When should I use openbrand?
Use it during Validate when building landing or hero prototypes that should mirror a reference company’s look and feel.
How do I add openbrand to my agent?
Configure stdio MCP for npm openbrand-mcp 0.1.2 and set the OPENBRAND_API_KEY environment variable from https://openbrand.sh/dashboard.