Master CSS MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --root | No | Absolute path to the project root, passed to @master/css-mcp (e.g. --root /absolute/path/to/project). |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mastercss_suggest_classesB | Suggest project-aware classes for an isolated CSS declaration block. Preserves the complete block when conversion needs review. Checks declaration output, not surrounding cascade or browser rendering. Does not write files. |
| mastercss_workspace_infoA | Report workspace roots, resolved Master CSS packages, and project manifest status. |
| mastercss_setup_auditA | Audit package, entry stylesheet, manifest, integration, and package-resolution setup for a workspace. |
| mastercss_inspect_classB | Inspect one Master CSS class and return semantic parts, generated rules, variables, and CSS text. |
| mastercss_trace_classB | Trace one class from project extraction through generated CSS, missing CSS classification, and engine inspection. |
| mastercss_extract_classesC | Extract class positions and validation summaries from project files or an in-memory source buffer. |
| mastercss_inspect_directivesC | Inspect CSS-first directives from a stylesheet entry or in-memory CSS content and report manifest/CSS effects. |
| mastercss_render_cssC | Generate CSS from an HTML fragment or a whitespace-separated class list. |
| mastercss_scan_projectB | Scan source files and stylesheet entries. Set includeSnapshot to capture a resolved project state for later impact comparison. Pass designSystem to inspect stylesheet token references and design policies; add routeStylesheets globs for stylesheets imported from JavaScript. |
| mastercss_manifest_queryB | Query active manifest tokens, utilities, mixins, custom media, custom containers, and token families. |
| mastercss_css_compareB | Compare class lists or source buffers under one manifest, or pass beforeSnapshot and afterSnapshot to compare resolved projects, including changed definitions and known consumers. Does not verify browser rendering. |
| mastercss_lint_projectC | Run Master CSS class-list diagnostics and return fix proposals without writing files. |
| mastercss_lint_contentB | Run Master CSS class-list diagnostics on an in-memory source buffer without writing files. |
| mastercss_suggest_syntaxC | Return language-service completions and hover context for a document position. |
| mastercss_preview_fixesB | Create a diff preview for lint fixes or generated CSS output and return a confirmation token. |
| mastercss_preview_directive_formatB | Create a safe preview for formatting Master CSS directives, or format in-memory content without writing files. |
| mastercss_apply_previewB | Apply a previously generated preview token after validating hashes and workspace containment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug-missing-css | Guide an assistant through debugging classes that are not producing CSS. |
| review-mastercss-classes | Review class lists for invalid, conflicting, non-canonical, or unsorted classes. |
| migrate-to-mastercss | Plan a conversion from an external styling system to current Master CSS. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mastercss-workspace-manifest | Loaded Master CSS project manifest status and entries. |
| mastercss-workspace-entries | Discovered Master CSS manifest entry files. |
| mastercss-workspace-packages | Resolved Master CSS package locations for this workspace. |
TDQS
Scored across 17 tools
Most tools target clearly distinct phases such as scanning, extracting, linting, inspecting, tracing, rendering, and previewing. There is some potential confusion between paired tools like lint_content vs lint_project, suggest_syntax vs suggest_classes, inspect_class vs trace_class, and scan_project vs extract_classes, but the descriptions generally clarify scope and input type.
All tools share the mastercss_ prefix and use snake_case names with predictable verb-oriented phrasing such as lint_content, scan_project, inspect_class, render_css, and apply_preview. The pattern is consistent enough that an agent can infer naming conventions for related operations.
At 17 tools the surface is slightly heavy, but the domain is broad CSS tooling covering setup, scanning, linting, inspection, tracing, rendering, manifests, comparison, and preview application. Each tool appears to earn its place rather than being redundant filler.
The set covers the full workflow from workspace setup audit and project scanning through extraction, linting, suggestions, class inspection, tracing, manifest queries, CSS rendering, comparison, and preview/apply safety. There are no obvious lifecycle dead ends for a Master CSS analysis and language-service server.