Skip to main content
Glama
521,191 tools. Updated 2026-09-06 10:36

"ESLint" matching MCP tools:

  • Identify and fix code quality issues in JavaScript and TypeScript files using configurable lint rules.
    Apache 2.0
  • Retrieve TypeScript errors and ESLint warnings for a file. Sort results by severity and limit to the top 50 by default.
    Apache 2.0
  • Run local ESLint on project files to detect and persist code diagnostics, tracking run success or failure.
    Apache 2.0
  • Automatically fix ESLint errors in JavaScript/TypeScript code by running npx eslint --fix on specified directories to enforce coding standards.
    -

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Enables AI coding assistants like Claude Code to perform real-time code linting and get violation summaries from tools such as ESLint, Stylelint, P3C, and Checkstyle via a local server.
    3
    20
    Apache 2.0
  • Add framework-specific ESLint plugins to a project. Provide the project directory to configure linting rules and improve code quality for the target framework.
    MIT
  • Generate standardized workspace settings and recommended extensions for TypeScript, ESLint, Tailwind CSS, and MCP development to establish consistent team configurations across VS Code and Cursor.
    MIT
  • Create a draft GitHub pull request applying atomic accessibility patches from UX audit suggestions. Prevents conflicts and invalid code, can output patch locally.
    MIT
  • Automatically fix lint errors in code files by applying VS Code source.fixAll or falling back to eslint, biome, or ruff.
    MIT
    Destructive
  • Summarize large lint, test, or CI logs grouped by file with error counts, using a local model to prevent clutter in Claude's context.
    MIT
  • Execute predefined development tool presets like test runners and linters for JavaScript, Python, Rust, and Go projects to automate code quality checks.
    -
  • Scaffold a production-ready Express.js + TypeScript backend project with your choice of ORM, Zod validation, Swagger docs, Docker, ESLint, Vitest, and more.
    MIT
  • Run TypeScript type checking and ESLint linting to detect code issues, then parse results into structured diagnostics with file, line, column, severity, rule, and message.
    MIT
  • Get TypeScript and ESLint errors and warnings for all files to assess project health after changes. Results are sorted by severity and capped at 50 by default.
    Apache 2.0
  • Parses raw CI logs or JUnit/Surefire XML to produce structured failure signals with test name, class, message, stack trace, and stable signature. Uses real parsers for accurate diagnosis.
    MIT
  • Run allowlisted verification commands like tests and linters for a task, recording results as review evidence.
    MIT
  • 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