Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEBUGNoEnable debug logging.false
LLM_MODELNoOllama model for layout and component style generation.qwen2.5-coder:7b
OLLAMA_URLNoPrimary Ollama instance URL.http://localhost:11434
EMBED_MODELNoOllama model for embeddings.snowflake-arctic-embed2
OLLAMA_NODESNoComma-separated host:port list for fleet routing. Derived from OLLAMA_URL when unset.
EMBED_DIMENSIONNoEmbedding vector dimension.1024

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_color_paletteA

Generates a cohesive color palette (complementary, analogous, triadic) and contrast scores from a base hex code.

css_to_tailwindC

Translates standard CSS properties into Tailwind utility classes.

ingest_figma_tokensB

Parses Figma JSON token exports, converts them to CSS variables/Tailwind configs, and indexes them into the RAG database.

generate_css_variables_from_figmaA

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.

query_design_rulesB

Semantic RAG search over specific design guidelines, CSS architecture, and accessibility standards.

analyze_layout_structureC

Accepts an HTML structure and returns the optimal CSS layout approach (Flexbox vs Grid) and the necessary CSS.

generate_component_stylesB

Given a component description (e.g. 'glassmorphism card with hover lift'), generates CSS custom properties and classes. Enriches output with RAG-retrieved design rules.

generate_responsive_breakpointsA

Generates standard CSS media queries for responsive breakpoints (e.g. sm, md, lg) with optional custom width overrides.

frontend_get_provenanceB

Company Brain Substrate (SQLite): Interrogate why a piece of context or design rule exists by tracing its version history.

frontend_traverse_graphB

Company Brain Substrate (SQLite): Graph Traversal. Traverses parent/child memory lineage for frontend design rules.

get_canonical_templateB

Returns the authoritative bit-for-bit HTML/SVG component template or @krusch/toolkit & krusch_toolkit Lego starter brick for krusch.dev and homelab projects.

list_canonical_templatesA

Lists all available canonical HTML/SVG design templates and @krusch/toolkit & krusch_toolkit Lego starter bricks for homelab projects.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation4/5

Most tools have clearly distinct purposes (palette generation, layout analysis, breakpoints, RAG query, provenance). The one genuinely confusable pair is ingest_figma_tokens vs generate_css_variables_from_figma, which both parse Figma JSON, but the descriptions explicitly differentiate RAG ingestion from CSS output. Minor residual overlap between generate_component_styles and generate_css_variables_from_figma is manageable via descriptions.

Naming Consistency4/5

All names use consistent snake_case with a verb_noun shape (generate_*, query_*, analyze_*, list_*, get_*). The only deviation is the 'frontend_' prefix applied to just two of twelve tools, which slightly breaks the pattern but remains readable and descriptive.

Tool Count5/5

Twelve tools is well within the sweet spot for a design-system/frontend server, with each tool covering a distinct stage (tokens, CSS, layout, components, knowledge retrieval, templates). No obviously redundant or filler tools.

Completeness4/5

The surface covers the full frontend design pipeline: palette, CSS-to-Tailwind, Figma token ingestion and CSS variable emission, layout analysis, component styling, breakpoints, RAG queries, provenance/graph traversal, and canonical template listing/retrieval. Minor gaps exist around theme/dark-mode generation and writing back or updating design rules/tokens, but core workflows are covered end to end.

Maintenance

ActivityMaintained
ResponsivenessOutdated data