Stylesafe

io.github.PatrizzosPublished by GitHub account Patrizzosv0.1.9Updated Oct 27, 2026

MCP server and CLI that catches CSS cascade conflicts and Tailwind utility clashes before they ship.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Local MCP server and CLI that detects CSS cascade conflicts and conflicting Tailwind utilities in a project's styles before they ship.

What you can do
  • Analyze stylesheets and component files for duplicate CSS declarations, dead rules from specificity conflicts, and silent style overrides
  • Find conflicting Tailwind utilities such as padding, margin, background, shadow, opacity, border and ring
  • Understand cn(), clsx() and twMerge() call expressions, not just plain className strings
  • Return structured reports with confidence, riskScore, nextStep and pass/clean flags
  • Run as a CLI over a single file, a directory, git-changed files, or in watch mode
When to use it
Useful when an assistant edits JSX or CSS and you want style bugs caught before changes are committed, when gating pull requests on cascade or utility clashes, or when auditing an existing project for style issues.
Requirements
Runs as a local process over stdio, installed from the npm package (Node.js required). No authentication, environment variables or headers are declared. Optional project config via a .styleintegrityrc file in the project root.
Before you install
It reads project source files to analyze them; the ignore list in .styleintegrityrc controls which paths are skipped. Reports are advisory, with confidence levels and a requiresUserConfirmation flag, so flagged conflicts may need human review rather than automatic fixes.

Installation

In SourceWeft

  1. Open Stylesafe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

StyleSafe - MCP and CLI

An MCP server and CLI that catches CSS cascade conflicts and Tailwind utility clashes before they ship — built for AI coding agents and CI workflows.

What it does

  • Detects duplicate CSS declarations and dead rules from specificity conflicts
  • Flags silent style overrides that may be accidental
  • Finds conflicting Tailwind utilities (padding, margin, background, shadow, opacity, border, ring, etc.)
  • Understands cn(), clsx(), and twMerge() call expressions, not just plain className strings
  • Returns structured agent-friendly reports with confidence, riskScore, and nextStep

Quick start

As a CLI tool

bash
npm install -g stylesafestylesafe src/components/Button.jsxstylesafe --changed --fail-on-issuesstylesafe --projectRoot srcstylesafe --watch src

As an MCP server

json
{  "mcpServers": {    "stylesafe": {      "command": "node",      "args": ["/absolute/path/to/server.js"]    }  }}

Example output

bash
stylesafe examples/tailwind-conflict.jsx

Returns a structured report:

json
{  "totalIssues": 5,  "riskScore": 275,  "averageRiskScore": 55,  "riskLevel": "medium",  "passed": true,  "clean": false,  "files": [    {      "filename": "examples/tailwind-conflict.jsx",      "issues": [        {          "type": "tailwind-conflict",          "category": "padding",          "classes": ["p-4", "px-8"],          "confidence": "medium",          "riskScore": 55,          "nextStep": "Choose one utility from the conflicting set or split the classes by scope.",          "requiresUserConfirmation": true        }      ]    }  ]}

passed: true means no hard errors. clean: true means zero issues of any kind.

Use cases

  • AI code generation: Catch style bugs before the agent commits changes
  • PR gate: Block merged changes that introduce cascade conflicts or utility clashes
  • Agent workflows: Integrate as a confirmation step in multi-turn coding tasks
  • Style audits: Run across a project to find existing issues

CLI options

  • stylesafe <file> — analyze a single file
  • stylesafe <dir> — analyze a directory recursively
  • stylesafe --projectRoot <dir> — same as above
  • stylesafe --changed — analyze git-changed files (for PR/CI)
  • stylesafe --changed --fail-on-issues — exit with code 1 if any issues found
  • stylesafe --watch src — re-run on every file change
  • npm test — run regression tests

Config

Place a .styleintegrityrc file in your project root:

json
{  "ignore": ["dist", "*.min.css"],  "failOn": ["error", "warning"]}

GitHub Actions

Add to .github/workflows/style-check.yml:

yaml
name: stylesafe
on:  pull_request:  push:    branches: [main]
jobs:  stylesafe:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: actions/setup-node@v4        with:          node-version: 20      - run: npm install      - run: node server.js --changed --fail-on-issues

Source: README.md at commit 8d5978c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.9LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts