Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
Krusch Frontend 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
Canonical UI templates, WCAG color palettes, Tailwind CSS conversion, and responsive design MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user krusch-frontend-mcp '--' npx -y krusch-frontend-mcp
# 2 — ask your agent for something these tools do
# generate_color_palette, css_to_tailwind, ingest_figma_tokens and 9 more
Krusch Frontend 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. This one runs on your machine: your client starts Krusch Frontend as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user krusch-frontend-mcp '--' npx -y krusch-frontend-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Generates a cohesive color palette (complementary, analogous, triadic) and contrast scores from a base hex code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseHex | string | yes | The base color in #RRGGBB format |
Translates standard CSS properties into Tailwind utility classes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cssString | string | yes | Raw CSS rules (e.g. 'display: flex; padding: 1rem;') |
Parses Figma JSON token exports, converts them to CSS variables/Tailwind configs, and indexes them into the RAG database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokensJsonStr | string | yes | — |
Parses Figma JSON token exports and returns a CSS string with a :root block defining CSS custom properties (variables) for each token. Use this to generate actual CSS rather than ingesting into the RAG.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokensJsonStr | string | yes | — |
Semantic RAG search over specific design guidelines, CSS architecture, and accessibility standards.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queryStr | string | yes | — |
| paradigm | string | no | Optional aesthetic paradigm to filter by (e.g. 'universal', 'refactoring-ui', 'vercel', 'apple-hig', 'material-design') |
Accepts an HTML structure and returns the optimal CSS layout approach (Flexbox vs Grid) and the necessary CSS.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| htmlString | string | yes | — |
Given a component description (e.g. 'glassmorphism card with hover lift'), generates CSS custom properties and classes. Enriches output with RAG-retrieved design rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Natural language description of the component aesthetic |
| paradigm | string | no | Optional aesthetic paradigm to filter RAG rules by (e.g. 'refactoring-ui', 'universal', 'vercel') |
Generates standard CSS media queries for responsive breakpoints (e.g. sm, md, lg) with optional custom width overrides.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customBreakpoints | object | no | Optional overrides for breakpoints. e.g. { '3xl': '1920px' } |
Company Brain Substrate (SQLite): Interrogate why a piece of context or design rule exists by tracing its version history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | The ID of the frontend RAG item to trace. |
Company Brain Substrate (SQLite): Graph Traversal. Traverses parent/child memory lineage for frontend design rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | The ID of the frontend RAG item to traverse from. |
| direction | string | no | Default is 'all'. |
| depth | number | no | Default is 3. |
Returns the authoritative bit-for-bit HTML/SVG component template or @krusch/toolkit & krusch_toolkit Lego starter brick for krusch.dev and homelab projects.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateKey | string | yes | The canonical template or Lego starter brick key to retrieve. |
Lists all available canonical HTML/SVG design templates and @krusch/toolkit & krusch_toolkit Lego starter bricks for homelab projects.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Krusch Frontend 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| generate_color_palette | no tags | |
| css_to_tailwind | no tags | |
| ingest_figma_tokens | state-write | state-write: declares readOnlyHint: false |
| generate_css_variables_from_figma | no tags | |
| query_design_rules | no tags | |
| analyze_layout_structure | no tags | |
| generate_component_styles | no tags | |
| generate_responsive_breakpoints | no tags | |
| frontend_get_provenance | no tags | |
| frontend_traverse_graph | no tags | |
| get_canonical_template | no tags | |
| list_canonical_templates | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.1. Pin a release below and the command asks for exactly that one.
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 Krusch Frontend 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.