Skip to main content
Glama
ryo-manba

stylelint-mcp

by ryo-manba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

stylelint-mcp

A Model Context Protocol (MCP) server for Stylelint that enables AI models to interact with Stylelint directly.

Installation

npm -D install stylelint-mcp

Note: You must have stylelint installed either globally or locally in your project.

Related MCP server: MCP Python Linter

Usage

The server is started automatically by your editor’s MCP client, but you can run it manually for testing:

npx stylelint-mcp

Editor setup examples

VS Code

Add .vscode/mcp.json:

{
  "servers": {
    "Stylelint": {
      "type": "stdio",
      "command": "npx",
      "args": ["stylelint-mcp@latest"]
    }
  }
}

Cursor

Add .cursor/mcp.json:

{
  "mcpServers": {
    "stylelint": {
      "command": "npx",
      "args": ["stylelint-mcp@latest"],
      "env": {}
    }
  }
}

Example prompts

Run Stylelint on the current file and explain the warnings

Lint #file:index.css and fix

License

MIT

Available Tools

1 tool
lint-filesA

Lint files using Stylelint. You must provide a list of absolute file paths to the CSS files you want to lint. The absolute file paths should be in the correct format for your operating system.

ParametersJSON Schema
NameRequiredDescriptionDefault
filePathsYes

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must reveal behavioral traits. It explains that the tool uses Stylelint and requires absolute paths, but it does not disclose error handling, return format, or behavior with non-existent files. For a linting tool, this is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The first sentence states the core action, and the second gives the critical input requirement. It is front-loaded and efficiently conveys the necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description is fairly complete. It covers the tool's purpose and the sole input requirement. It could mention the output (lint results) but is not essential for basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides no description for the 'filePaths' parameter (0% coverage). The description compensates by specifying that paths must be absolute, refer to CSS files, and be in the correct OS format. This adds valuable meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lints files using Stylelint, specifically CSS files. The verb 'lint' and resource 'files' are specific, and the tool name reinforces this. With no sibling tools provided, the distinction is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs the user to provide absolute file paths in the correct OS format, which is essential for proper usage. No exclusions or alternatives are mentioned, but given no siblings, this is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.1
    • First observedlint-files
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity between tools. The tool's purpose is clearly defined.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The name 'lint-files' follows a clear verb_noun pattern.

Tool Count3/5

A single tool feels thin for a linter server; additional tools like fixing or configuration would be expected. However, it may suffice for a minimal integration.

Completeness4/5

The core linting operation is covered. Missing features like fixing or config management are minor gaps, but the tool fulfills its stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • markdownlint-mcp

    ernestgwilsonii
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides AI assistants with the ability to lint, validate, and auto-fix Markdown files to ensure compliance with established Markdown standards and best practices.
    6
    MIT

  • MCP Python Linter

    shelardipak
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables Python code linting by integrating the Model Context Protocol with tools like pylint and the OpenAI API. It allows for dynamic tool discovery and uses LLMs to orchestrate tool selection and provide refined analysis of linting results.
    -

  • Farofino MCP Server

    italoag
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables smart contract security auditing using Slither, Aderyn, and custom pattern analysis through the Model Context Protocol, allowing AI assistants to run static analysis and vulnerability checks on Solidity and Vyper contracts.
    1
    Apache 2.0

  • Spotlight MCP

    api-commons
    A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to lint API artifacts (OpenAPI, AsyncAPI, Arazzo) and manage rulesets conversationally via the Model Context Protocol.
    4
    Apache 2.0