Your brand, in every AI assistant: MCP, Claude skills, and a one-click design-system export

Your brand book has always been the source of truth. Starting today, it's also a live data source for your AI tools.

We're shipping three things:

an MCP server, so Claude, ChatGPT, and any MCP-capable assistant can read your brand data,
a Claude plugin with three skills that teach assistants to use that data well, and
a design-system export — one zip built for Claude Design, Figma, and your codebase.

Everything is read-only and available now.

The problem: AI tools don't know your brand

Ask an assistant for "a revenue chart in our brand colors" and you'll get a guess — a blue that's almost yours, a font that isn't. The brand book that would fix this is a website the assistant has never read, or a PDF buried in a drive.

Meanwhile your brand book on Orchestra Sites already has everything an AI needs: exact hex values with tint/shade ramps, font files, logo variants for every background, and voice guidelines written as explicit do/don't rules.

The MCP server

MCP is the open standard assistants use to connect to outside data. Orchestra Sites now speaks it natively, with two endpoints:

For you and your team — an OAuth connection (sign in with your Orchestra account, no API keys) that can read all your brands, including unpublished drafts.
For everyone else — a public, no-sign-in endpoint that serves any published brand. Journalists, agencies, and partners can pull your published brand book into their own assistant the same way they'd visit your microsite.

The tools are deliberately shaped for how assistants work: get_brand_colors, get_brand_typography, get_brand_logos, get_brand_voice, get_press_kit, get_team, get_media_assets, plus get_design_system and list_my_brands.

Three skills, one install

The orchestra-sites plugin bundles the connector with three skills:

orchestra-brand — precise brand data Q&A. "What's our primary color in CMYK?" gets the stored value, not a guess.
on-brand-design — the big one. Whenever you ask for anything visual — a chart, a slide deck, an infographic, a landing page, an app screen — Claude fetches your palette and typography first and applies them exactly: your primary leads, shade ramps drive chart scales, headings use your heading font. It composes with your other connectors too: numbers from your analytics MCP, design system from us.
press-kit-pr — press releases that end with your boilerplate verbatim, coverage summaries, team bios at three lengths, and paste-able journalist asset replies.

/plugin marketplace add orchestra-code/orchestra-sites-skills
/plugin install orchestra-sites@orchestra-sites-skills

Try this

Once connected, ask Claude:

"Pull last quarter's signups from our analytics and chart them in acme.com's brand — exact colors, our fonts, logo top-left."

Claude calls get_brand_colors and get_brand_typography, grabs the right logo variant for the background, and builds the chart with your actual hex values. No "close enough."

One zip for Claude Design, Figma, and your codebase

Every published brand book now has a "Download design system (.zip)" button (it's in the app for drafts, too). Inside:

tokens/design-tokens.json — W3C DTCG design tokens, the industry-standard format. Import into Figma with any DTCG plugin (e.g. Tokens Studio) and your palette and type become Figma variables.
brand-guide.md — your identity, voice do/don'ts, and usage notes, readable by humans and AI alike.
css/brand.css — ready-to-use custom properties and @font-face rules.
logos/ and fonts/ — every file, organized.

Drop the unzipped folder into Claude Design's design-system setup and every project it generates uses your brand from the first frame.

Get started

Docs: Connect your AI assistant, the skills, and the export.
Have a brand on Orchestra Sites? Add the connector and ask for something on-brand.
Don't have one yet? Create your brand book — it takes an afternoon, and now it works everywhere your AI does.