Skip to main content
The slowest part of any build is the moment the assistant needs your logo. Brand assets removes it: you drop the files in before the chat, and the assistant finds them with one call.

​
Where

Bevel → MCP Connectors → Brand assets. A drop zone that takes:
  • images: PNG, JPEG, WebP, GIF, SVG (sanitized on import);
  • fonts: WOFF2, WOFF, TTF, OTF.

​
What happens on drop

An image goes into the media library at once. Its tone is read from the pixels: dark artwork becomes the Logo (for light surfaces), white artwork the Light logo (for dark surfaces). A file without “logo” in its name is listed as a Photo. Change the role from the dropdown on the row if the guess is wrong. A font file goes into Bevel Kit’s Custom Fonts as one face of a family. The weight and style are read from the file name (Aeonik-Bold.woff2 is 700, Inter-MediumItalic.woff2 is 500 italic), and the family name from the file name too, unless you type it in the box first. Drop every weight you have; they join the same family. Every file is hashed. Dropping the same file twice returns the same asset, never a duplicate.

​
What the assistant sees

The get_brand_assets tool lists every entry with its role, tone and, for fonts, the weights that ship, plus the current site logo and the installed Custom Fonts. The instructions tell the assistant to call it before ever asking for a file, and how to use each entry:
  • logo and light logo: installed with update_site_logo by attachment id;
  • photos: used by URL in image slots, already local;
  • fonts: named in update_design_system typography.

​
Removing an entry

Remove takes an entry off the list. The media file and the font stay where they are: the list says what to hand the assistant, it is not a second library.

​
For a business that already has a website

Skip the drop zone. fetch_brand reads the current site’s logo candidates, the colours its stylesheets declare and the fonts it names, in one call. See Tools.