English Français العربية

io.github.rog0x/lint

Official registry Developer tools

Style check, naming, complexity analysis for AI agents

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @rog0x/mcp-lint-tools
Claude Code 
claude mcp add lint -- npx -y @rog0x/mcp-lint-tools@1.0.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lint": {
            "command": "npx",
            "args": [
                "-y",
                "@rog0x/mcp-lint-tools@1.0.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @rog0x/mcp-lint-tools
  2. Tools
  3. Installation
  4. Usage with Claude Desktop
  5. Development
  6. License

@rog0x/mcp-lint-tools

Code linting and style checking tools for AI agents, exposed as an MCP (Model Context Protocol) server.

All analysis is performed via regex and text parsing — no AST libraries required.

Tools

check_code_style

Check code style issues with configurable rules:

  • Indentation — tabs vs spaces, configurable indent size
  • Line length — flag lines exceeding a maximum length
  • Trailing whitespace — detect trailing spaces/tabs
  • Final newline — require a newline at end of file
  • Quotes — enforce single or double quote consistency
  • Semicolons — enforce always or never semicolon usage
check_naming_conventions

Analyze identifier naming conventions:

  • Detect camelCase, PascalCase, snake_case, UPPER_CASE
  • Language-aware rules for TypeScript, JavaScript, Python, Go
  • Flag mixed conventions within the same identifier kind
  • Suggest fixes with automatic name conversion
analyze_complexity

Measure code complexity metrics:

  • Cyclomatic complexity per function
  • Lines per function count
  • Nesting depth measurement
  • Configurable thresholds for flagging
find_dead_code

Detect potential dead code:

  • Unused variables — declared but never referenced
  • Unreachable code — statements after return/throw/break
  • Empty catch blocks — silently swallowed errors
  • Commented-out code — blocks of commented code
  • TODO/FIXME/HACK — annotation comments
analyze_imports

Analyze import statements:

  • Unused imports — imported names not referenced in code
  • Import ordering — enforce group ordering (builtin > external > internal > relative)
  • Duplicate imports — same module imported multiple times
  • Circular dependency hints — basic detection of potential cycles

Installation

npm install
npm run build

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "lint-tools": {
      "command": "node",
      "args": ["path/to/mcp-lint-tools/dist/index.js"]
    }
  }
}

Development

npm install
npm run build
npm start

License

MIT

Frequently asked questions

What is io.github.rog0x/lint?

Style check, naming, complexity analysis for AI agents

How do I install io.github.rog0x/lint?

It runs on your machine. In Claude Code: claude mcp add lint -- npx -y @rog0x/mcp-lint-tools@1.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.rog0x/lint need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.rog0x/lint open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.rog0x/lint?

It is published by rog0x. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.