Blender integration through the Model Context Protocol
CSS Crème is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http css-creme-mcp https://csscreme.com/mcp
# 2 — ask your agent for something these tools do
# search_themes, list_themes, get_design_md and 9 more
CSS Crème costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http css-creme-mcp https://csscreme.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find a design system by describing what you are building ("dark developer tool", "calm fintech dashboard", "playful consumer app"). Returns matching themes with their DESIGN.md URL and shadcn install command. Call this first when the user has no design system defined.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text: mood, industry, colour, or use case. |
| kind | string | no | Curated palette theme, full page template, or either. Default any. |
| mode | string | no | Preferred light or dark. Default any. |
| limit | integer | no | Max results, 1-25. Default 8. |
Browse the full catalogue of curated themes and templates. Use when the user wants to see options rather than search for one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
| mode | string | no | — |
Fetch the full DESIGN.md for one theme: semantic colour roles, the complete shadcn token set in light and dark, typography, radius, spacing, MEASURED WCAG contrast ratios, and numbered rules the generated UI must follow. Read this before writing any UI. Save it at the repo root as DESIGN.md so it applies to every session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Theme or template id, e.g. "deep-ocean". Get ids from search_themes or list_themes. |
Get the shadcn/ui registry item (OKLCH tokens, light and dark) plus the paste-ready CSS variables for one theme, and the one-line command that installs it for real. Use after get_design_md when you are ready to write the tokens into globals.css.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Theme or template id. |
| format | string | no | Default both. |
Explains where a DESIGN.md belongs for a given coding agent (Claude Code, Cursor, v0, Codex, Lovable) so the design rules apply to every session rather than one message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | claude-code | cursor | v0 | codex | lovable |
Return the exact npx shadcn@latest add <url> command that installs one theme into a shadcn/ui project, plus the registry URL it reads. Use when the user says "install it" and you already know the id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Theme or template id. |
Return a short standing-instructions block that makes every future session read DESIGN.md before touching UI. Paste it whole into CLAUDE.md, AGENTS.md or .cursor/rules/design.mdc. It points at the DESIGN.md rather than restating it, and carries the token fingerprint so drift is detectable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Theme or template id. |
Fetch a public site's HTML and stylesheets and return what its CSS declares: named custom properties that look like design tokens, the colours it uses most, its font stacks, border radii, spacing values, and the framework it appears to be built with. Also returns a "drop" report: roughly how many words a web-to-markdown reader would carry away from this page, against the design decisions it would
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute public http(s) URL of the page to read. |
| maxAge | integer | no | How old a reused read may be, in seconds. Default 600; 0 reads the site now. A reused read keeps its own fetchedAt and says cache.hit: true. |
| format | string | no | Default json (the measurement). Or one artefact from the same read: md (DESIGN.md), tokens (W3C DTCG tokens.json with the site's declared names by scope), css (globals.css: shadcn variables, Tailwind |
| expect | string | no | Optional brand hex, like #635BFF. The json response then carries expect: the nearest value the site declares (a token when it has any, else a literal), its CIE76 distance, and whether that is within |
| expectSpec | object | no | Optional brand spec to check field by field, for example {"primary":"#635BFF","bg":"#FFFFFF","font":"Inter","heading":"Sohne","radius":"8px","base":"16px","spacing":"4px","darkMode":true,"tokens":{"-- |
Answers two questions about a modern CSS feature with data instead of recall. First, its Baseline status (widely available, newly available, or limited availability), the date, and which core browsers lack it, read from the open web-features dataset at build time. Second, how many of CSS Crème's curated, decoded showcase sites ship it, which ones, how many of them guard it with @supports, and the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | no | A web-features id or a plain name: "container-queries", "has", ":has()", "anchor positioning", "oklch", "subgrid", "@scope". Omit for the whole Ship Gap summary. |
Read the stylesheets of a public site and return a full DESIGN.md: semantic roles with the token each came from, measured WCAG contrast pairs, the tokens the site itself declares (framework internals counted separately), font families, the type scale with the ratio between steps, colour frequency, gradients, corner radii, spacing, an elevation ladder of shadows, breakpoints, the z-index ladder, in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute public http(s) URL of the page to read. |
| maxAge | integer | no | How old a reused read may be, in seconds. Default 600; 0 reads the site now. A reused read keeps its own fetchedAt and says cache.hit: true. |
Read a sample of pages from one site (from its sitemap.xml, or the homepage links when there is no sitemap) and report what is CONSISTENT across them: which declared tokens, colours, font stacks, radii and spacing values appear on every page read, and which appear on only some. One page shows what a page uses; a design system is a claim about consistency, and only a sample can test it. Returns cou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute public http(s) URL anywhere on the site. |
| pages | integer | no | How many pages to read, 2 to 8. Default 5. |
| maxAge | integer | no | How old a reused read may be, in seconds. Default 600; 0 reads the site now. A reused read keeps its own fetchedAt and says cache.hit: true. |
Every DESIGN.md carries a Fingerprint line. Pass the id and that fingerprint; the server answers whether the copy matches the current token set, and if not, returns the current tokens so the agent can update the file instead of following a stale one. Call this at the start of a session when a DESIGN.md is already in the repo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Theme or template id from the DESIGN.md Source line. |
| fingerprint | string | yes | The value from the DESIGN.md Fingerprint line, e.g. "fnv1a-9c2a41d7". |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CSS Crème or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.8.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CSS Crème can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.