CSS Crème MCP for coding agents

Give your agent a design system, not a guess.

Connect your coding agent to 52 design systems it can search, read and install. It studies real tokens before it builds, so the output follows a system instead of inventing one.

Free, ungated, no account and no API key. The nearest equivalent requires a paid plan.

claude mcp add --transport http csscreme https://csscreme.com/mcp

Any client that speaks remote MCP can use it. Endpoint: https://csscreme.com/mcp

Works with

Claude CodeCursorv0CodexLovable Windsurf any remote-MCP client

Five tools

The endpoint answers tools/list itself, so this is a description rather than a specification. Ask your agent to call them; you should not need to.

search_themes

Describe what you are building ("calm fintech dashboard") and get matching design systems back.

list_themes

Browse the whole catalogue when the user wants options rather than one answer.

get_design_md

Pull the full DESIGN.md: roles, tokens, typography, measured contrast, and the rules to follow.

get_theme_tokens

Fetch the shadcn registry item and paste-ready CSS when it is time to write globals.css.

how_to_use

Ask where the file belongs for a given editor, since every tool expects it somewhere different.

What changes

Your agent stops guessing

Without a design system an agent falls back on the average of everything it has read: an invented palette, several corner radii, a second font nobody asked for. With one it works from your tokens, and you can check the output against them.

Every number is measured

Each DESIGN.md carries real WCAG contrast ratios computed from the tokens themselves. When a pair fails AA the file says so instead of shipping it quietly. Nothing in it is an adjective the agent has to interpret.

Not limited to a fixed library

A curated catalogue can only answer for the sites somebody added in advance. Point our decoder or extractor at any live page and it produces a DESIGN.md for that page, then hands your agent the same contract shape.

It installs for real

Every theme is also a shadcn/ui registry item. After the agent writes the components, one command writes the tokens into globals.css. The loop closes instead of stopping at a suggestion.

Installing it

1

Claude Code

claude mcp add --transport http csscreme https://csscreme.com/mcp
2

Everything else

Add https://csscreme.com/mcp as a remote MCP server (HTTP transport) in your client's config. There is no token to paste, because there is nothing to authenticate.

3

Then just ask

“Build a settings page for a calm fintech dashboard.” The agent searches, reads the DESIGN.md, and follows its rules. You do not have to name the tools.

What it does not do

It does not make an agent a designer. It removes one specific failure: inventing a visual system because nobody supplied one. Layout, hierarchy, information design and whether the screen is any good remain yours.

The server is stateless and reads static build-time data, which is why it needs no key and cannot lose your work: it has nothing of yours to lose. If you want a design system from a page that is not in the catalogue, use the decoder or the extractor and hand your agent the resulting file.

Full format spec: what a DESIGN.md holds and why.