Master CSS MCP
OfficialRelated Servers
Alternatives to Master CSS MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides VSCode context and filesystem operations for AI assistants.9MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).12 npm3Apache 2.0
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for @imqueue — lets AI coding agents (Claude Code, Cursor and others) search the docs, scaffold typed services & clients and use @imqueue/cli live.1461 npm1GPL 3.0
- AlicenseCqualityDmaintenanceMCP protocol server for managing multi-project Markdown documents, supporting project isolation and LLM tool integration.2925 npm4MIT
- FlicenseNot gradedqualityBmaintenanceModel Context Protocol server for MCPGRAM that enables MCP clients to interact with connectors like GitHub, Slack, and Notion through stdio or Streamable HTTP transports.-
- AlicenseNot gradedqualityDmaintenanceEnables creating MCP (Model Context Protocol) servers with zero boilerplate, full TypeScript support, and multiple transports (stdio and HTTP).4 npm1MIT
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.