moodspec

Now speaking MCP — works in Claude Code, Cursor, Codex, Lovable and Replit

The moodboard your
coding agent can read.

moodspec is a workspace for your design decisions — fonts, colours, logos, references, who you’re writing for, what you’d never ship. It serves them to Claude Code, Cursor, Codex and the rest over MCP, so every screen your agents generate comes out on-brand.

01 — The problem

Taste has to be taught.
Not re-typed every prompt.

An agent starts with no taste at all. You can describe it in chat — but you'll describe it slightly differently every session, and every teammate describes it differently again. Ten repos later nothing matches, and someone rebuilds it by hand.

Taste in the prompt

Drifts

~/acme-landing

mon 09:14

> build the pricing page — minimal, warm

neutrals, tight radius, not violet

wed 22:41 · new session

> redo the dashboard, clean and modern,

serif headings i think? same as the site

fri 11:02 · new session

> the emails too — you know my style

by now▌

  • Lives in a chat log — no version, no history to compare
  • Worded differently every session — so the output drifts
  • Change your mind and you re-type it in every project
  • Starts from zero in the next repo, and the one after

Taste in one workspace

Holds

You write it down once, in one place:

TYPE
Newsreader / Inter
COLOUR
orange on buttons only
FOR
Dana — ops lead, hates jargon
FEEL
radius 9, slow motion, no gradients
VOICE
plain, short, no hype words
MARK
the curves, not the shading
LIKE
linear.app, but warmer
NEVER
violet, gradient heroes, emoji
  • Saved as a document — versioned, restorable, reviewable
  • Worded once — so nothing drifts between sessions
  • Change it in one place, everywhere follows
  • Every repo you connect reads the same one

02 — The canvas

Paste what you like. Get a canvas.

Drop in a site, a font, a logo, a screenshot. We pull it apart and lay the pieces out as cards you can keep, remove or annotate — that's your canvas.

Step 1 · You drop it in

https://linear.app

a font you already love

logo.svg

screenshot, note, article…

No setup, no schema. Anything that carries taste is valid input.

Step 2 · It lands as a canvas

brand-soulfrom linear.app + 2 uploadsMCP live

Typefaces

edit

Newsreader · Inter · body · 400/600

“headlines only, tight tracking”

Palette

edit

#E8511E accent

“orange for actions, never text”

Marks

edit

logo.svg

“love the curves and the shading”

Customer

edit

Dana · ops lead

“40-person logistics firm. Lives in a spreadsheet, hates jargon.”

Motion

edit

320ms · ease-out

“slow, never bouncy”

Reference

edit

Writing for busy operators · linear.app/blog

“this is the voice I want”

03 — The middleware

Everything in. One taste out.

Design happens in four tools and none of them talk to your agent. moodspec sits in the middle: import from wherever you made it, keep the assets and the taste on one canvas, then serve it to every agent through one endpoint.

Where design happens

The middleware

Where it gets built

FigmaStyles, variables, frames
CanvaBrand Kit and exports
Claude designThe exported .html
FramerTokens the site ships
Made in moodspecFonts, logos, notes you upload
moodspecv41

One canvas. Assets and taste, versioned together.

FontsColoursLogosVoicePersonasFiles

mcp.moodspec.app/c/…

Claude CodeReads the canvas before it writes
CursorSame taste, every repo
LovableFirst draft arrives on-brand
Any MCP clientOne endpoint, no plugin
ImportMCP

03B — The payload

What your agent actually sees.

The endpoint is a standard MCP server — Streamable HTTP, one tool call per request. Self-hosting isn’t offered; every plan connects to our hosted server over a token-scoped URL. Only the fields relevant to the request are pulled, and it usually serialises to under two thousand tokens.

  • Token scoped, not account scopedEach endpoint reads one canvas. Rotate or revoke it without touching any other repo.
  • Rate-limited per token600 reads an hour on Pro, 5,000 on Business — enough for an agent's normal working pace, not for scraping.
  • Read-only, alwaysNo tool call can write back to the canvas — a leaked token exposes taste, not write access.

# moodspec.get_canvas("brand-soul")

## Type
Newsreader (display) / Inter (body) — headings only, tight tracking

## Colour
#E8511E accent — buttons only, never text · #101010 ink · #F4F4F1 surface

## For
Dana — ops lead, 40-person logistics firm, hates jargon

## Feel [inspiration]
radius 9, slow motion, no gradients — like linear.app, but warmer

## Never
violet, gradient heroes, emoji

~1,140 tokens · yours = rule, inspiration = reference

04 — Live in every project

One workspace, live in every project.

Paste the endpoint once per repo. From then on your agent reads the current canvas before it writes a line — the same fonts, colours, notes and personas in every project you build.

  1. 01Press Connect agentWe generate a private endpoint for that canvas.
  2. 02Paste it into your toolOne line of config. We show the exact snippet per client.
  3. 03Change your mind wheneverSwap a typeface on the canvas; every connected project picks it up on the next prompt.

ONE-TIME SETUP

$ claude mcp add moodspec brand-soul

✓ connected — reading canvas on every prompt

Every prompt after that

Build the pricing page.

Agent checked your canvas first, then built it:

  • Headings in Newsreader, body in Inter — the fonts you picked
  • Orange only on the buttons, because your note said so
  • Copy written for Dana, the ops lead on your canvas — no jargon
  • Slow transitions, no gradients, radius 9

You typed four words. It applied everything you’d otherwise have to re-explain — and does the same in every repo you connect.

05 — Connections

Works where you already build.

Every integration has a two-minute setup guide. Pick yours.

06 — Many canvases

One per product,
per client, per mood.

  • Brand soul43 assetsMCP live
  • Competitors teardown28 assets
  • Q3 relaunch17 assets
  • + New canvas

Keep a canvas for your product’s soul, one for the competitor teardown, one for the relaunch you haven’t pitched yet. Point a different agent at each. The free plan keeps one canvas locally; Pro backs up unlimited canvases and gives every one of them an MCP endpoint.

See pricing

07 — Who it's for

The same canvas, three ways.

What you keep on a canvas barely changes between a weekend project and a company with a brand team. Who is allowed to change it does.

Stop describing your taste
in every prompt.

Open a canvas, paste three links, connect your agent. Free forever for one canvas — no account needed to start.