# moodspec

> A workspace for your design decisions — fonts, colours, logos, references and voice — served to Claude Code, Cursor, Codex, Lovable and Replit over MCP.

moodspec is a workspace for design decisions — typefaces, colour with usage rules,
logos, saved references, customer personas and tone of voice. It serves them to coding
agents over the Model Context Protocol, so generated UI comes out on-brand instead of
defaulting to a purple gradient.

Key facts:

- Free tier: one canvas, stored in the browser, no account required.
- Pro ($10/mo): unlimited canvases, cloud backup, a private MCP endpoint per canvas.
- Business ($24/editor/mo, 3 minimum): shared workspace, roles, locked canvas, approvals.
- MCP endpoint: https://mcp.moodspec.app/c/{canvas-slug}, Streamable HTTP, bearer token auth.
- Agents can read a canvas and propose changes; they can never write to one directly.
- Operated by SC QWERTYBIT SRL, Romania.

Sitemap: https://moodspec.app/sitemap.xml
Full text: https://moodspec.app/llms-full.txt

## Start here

- [moodspec — the moodboard your coding agent can read](https://moodspec.app): A workspace for your design decisions — fonts, colours, logos, references and voice — served to coding agents over MCP.
- [Pricing](https://moodspec.app/pricing): One canvas free with no account. Pro $10/mo, Business $24 per editor, Enterprise per deployment.
- [Infrequently asked questions](https://moodspec.app/faq): The questions people actually hesitate over before pasting a link.

## Docs

- [Docs — connect a canvas over MCP](https://moodspec.app/docs): Get an endpoint, add one block of config, and prompt normally.
- [Rolling out to a team](https://moodspec.app/docs/team-rollout): One canvas, a token per repo, and the review habits that keep a shared canvas worth reading.
- [Tools and resources](https://moodspec.app/docs/tools): Every tool an agent can call over MCP, with arguments and the response shape.
- [Tokens and limits](https://moodspec.app/docs/tokens): Scopes, rate limits and the three errors an agent can get back.

## Integrations

- [Integrations](https://moodspec.app/integrations): Claude Code, Cursor, Codex, Lovable, Replit and Claude design.
- [Claude Code + moodspec](https://moodspec.app/integrations/claude-code): Add moodspec as an MCP server and Claude reads your canvas before it writes a line of UI.
- [Cursor + moodspec](https://moodspec.app/integrations/cursor): Project-level MCP config so every teammate opening the repo inherits the same taste.
- [Codex + moodspec](https://moodspec.app/integrations/codex): Register moodspec in your Codex config so CLI and cloud runs share one source of taste.
- [Lovable + moodspec](https://moodspec.app/integrations/lovable): Point Lovable at your canvas so generated apps arrive already on-brand.
- [Replit + moodspec](https://moodspec.app/integrations/replit): Give Replit Agent the same design context your local tools have: fonts, palette, marks and voice, read from one canvas.
- [Claude design + moodspec](https://moodspec.app/integrations/claude-design): Bring designs you made with Claude straight onto a canvas — fonts, palette and components extracted.

## Who it's for

- [For solo devs](https://moodspec.app/for-solo-devs): One taste across every side project.
- [For product teams](https://moodspec.app/for-product-teams): One canvas every repo and teammate reads.
- [For enterprise](https://moodspec.app/for-enterprise): A locked brand canvas only owners can change, with SSO, SCIM and an audit log.

## Blog

- [The moodspec blog](https://moodspec.app/blog): Notes on design taste, and how to hand it to a machine.
- [Where design rules belong: AGENTS.md, .cursorrules, or MCP](https://moodspec.app/blog/agents-md-design-rules): Rules files load into every session, in full, and are versioned with one repo. Design decisions are the opposite shape. Here is the division of labour that keeps both small.
- [How to teach a coding agent your design taste](https://moodspec.app/blog/teach-taste): Agents do not lack skill — they lack a source of truth about what you find beautiful. Here is how to write one down.
- [Why every vibe-coded app looks the same](https://moodspec.app/blog/same-app): The sameness is not a model limitation. It is what happens when nobody supplies a point of view.
- [Choosing type pairings for product UI](https://moodspec.app/blog/type-pairing): A practical way to pick two typefaces that hold up across a landing page, an app and an email.
- [Building a colour palette you can defend](https://moodspec.app/blog/palette): Neutrals do the work, one accent does the pointing, and every colour needs a job description.
- [Write your UI copy for one named customer](https://moodspec.app/blog/copy-for-one): The fastest way to stop sounding like every other SaaS is to stop writing for "users".
- [MCP for designers: what it actually is](https://moodspec.app/blog/mcp-for-designers): A plain explanation of the protocol that lets your agent read your tools — and why design context belongs in it.

## Guides

- [Design handoff guides for coding agents](https://moodspec.app/guides): Getting a design out of Figma, Claude Design, Canva, Photoshop, Adobe XD or Sketch and into a coding agent.
- [Adobe XD to a coding agent: getting out of a frozen tool](https://moodspec.app/guides/adobe-xd-to-coding-agent): XD has not been sold since 2023 and has had no new features since. This is not a handoff guide. It is about extracting what matters while the file still opens.
- [Canva to a coding agent: the export path, not the MCP server](https://moodspec.app/guides/canva-to-coding-agent): Canva has an MCP server and it is not the one you want. The route that works runs through the Connect API's HTML export — and produces something an agent has to be told how to read.
- [Claude Design to Claude Code: the handoff bundle explained](https://moodspec.app/guides/claude-design-to-claude-code): The tightest design-to-code path shipping today, because both ends are the same model. That closeness solves the translation problem and leaves a different one untouched.
- [Which coding agent handles design context best](https://moodspec.app/guides/design-context-coding-agents-compared): Claude Code, Cursor, Codex, Replit and Lovable take design context through different mechanisms, in different files, with different lifetimes. A comparison of what each one can actually reach.
- [Figma to a coding agent: what the MCP server actually sends](https://moodspec.app/guides/figma-to-coding-agent): The Dev Mode MCP server hands your agent a component tree, variables and Code Connect mappings. Here is how to wire it up per agent, and why the output still comes back off-system.
- [Photoshop to a coding agent: reading a PSD without Adobe](https://moodspec.app/guides/photoshop-psd-to-coding-agent): A PSD is a document of pixels with a layer tree bolted on. Parsers can read that tree without Adobe running — and knowing exactly what survives the parse is what keeps the route useful.
- [Sketch to a coding agent: an MCP server inside the app](https://moodspec.app/guides/sketch-to-coding-agent): Sketch ships an MCP server in the Mac app that lets an agent read the layer tree, pull assets and run code against the open document. That last capability is unusual, and it changes what you can ask for.

## Company

- [About moodspec](https://moodspec.app/about): Why coding agents have no taste, and what to do about it.
- [Contact](https://moodspec.app/contact): A person reads every message and replies within a working day.
- [Privacy policy](https://moodspec.app/privacy): What we collect, what we never do with it, and your rights under the GDPR.
- [Terms & conditions](https://moodspec.app/terms): Accounts, plans and billing, your content, acceptable use and liability.