Stylesafe MCP server
MCP server and CLI that catches CSS cascade conflicts and Tailwind utility clashes before they ship.
0 stars31 downloads/wk
Reviews
Write oneNobody has reviewed Stylesafe yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Stylesafe tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_style_integrityAnalyzes CSS/SCSS files and Tailwind-related markup for cascade conflicts, duplicate declarations, specificity issues, and conflicting utilities.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 78 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Stylesafe compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 31
- more than 19% of 12,191 servers with a package
What its tools let an agent do: 1 read
Install Stylesafe in Claude Code, Cursor or VS Code
Runs npx -y @patrizzos/stylesafe on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add stylesafe -- npx -y @patrizzos/stylesafe
What the publisher says
From the Stylesafe repository's README, as published. We do not edit it. Read it on GitHub
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
npm install -g stylesafe
stylesafe src/components/Button.jsx
stylesafe --changed --fail-on-issues
stylesafe --projectRoot src
stylesafe --watch srcAs an MCP server
{
"mcpServers": {
"stylesafe": {
"command": "node",
"args": ["/absolute/path/to/server.js"]
}
}
}Example output
stylesafe examples/tailwind-conflict.jsxReturns a structured report:
{
"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 — analyze a single file
- stylesafe — analyze a directory recursively
- stylesafe --projectRoot — 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:
{
"ignore": ["dist", "*.min.css"],
"failOn": ["error", "warning"]
}GitHub Actions
Add to .github/workflows/style-check.yml:
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-issuesNothing above is checked by us. What we check is on the safety report.
Stylesafe: common questions
- Is Stylesafe MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Stylesafe safety report
- How do I install Stylesafe?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Stylesafe need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Stylesafe maintained?
- The last commit was 118 days ago (2026-07-09). The latest release is v0.1.9.
- How does Stylesafe compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.