"stylelint" matching MCP tools:

• lint-filesA

  stylelint-mcpA

  Lint CSS files using Stylelint. Supply absolute file paths to check for coding errors and enforce style rules.

  MIT

• get_project_summaryA

  YanceLint MCP ServerA

  Retrieve a project-level summary of code linting violations from P3C, ESLint, Stylelint, and Checkstyle, with total counts per tool.

  Apache 2.0

• get_file_violationsA

  YanceLint MCP ServerA

  Get code violations for a single file by automatically selecting the correct linter (P3C, ESLint, Stylelint, Checkstyle) based on file type, returning severity, message, and line number.

  Apache 2.0

• check_lintingA

  Code GuardianB

  Identifies available linters and executes ESLint to catch code issues during codebase audits.

  MIT

• designesy_guardrailsA

  DesignesyA

  Generate a frozen build-contract bundle for AI coding agents from any design system URL — the product layer. Ingests a site, extracts its :root tokens, and emits 6 outputs: (1) DTCG-format token file, (2) Stylelint config generated from token values, (3) AGENTS.md-format rules with token allowlist, (4) component contract with allowed prop patterns, (5) anti-pattern documentation, (6) DESIGN.md file (Google open spec, google-labs-code/design.md) — YAML front matter + markdown body, the de-facto AI-readable design-context standard. Use this when you need to turn a design system into the file AI agents read and the lint that enforces it. When NOT to use: for design-contract scoring, use designesy_score; for token-file validation, use designesy_tokens_score; for drift detection, use designesy_drift_score. Executable — fetches the URL, extracts CSS + :root custom properties, generates the bundle. No browser needed. Returns JSON: { ok, url, score (0-100, emission completeness), grade, pass, warn, fail, total, tokensExtracted, bundle: { tokens, lintConfig, agentRules, componentContract, antiPatterns, designMd }, checks[{id, item, category, status, detail}] }. Results cached ~24h per URL.

  ConnectorNo auth