Identify and fix code quality issues in JavaScript and TypeScript files using configurable lint rules.
Apache 2.0
336,187 tools. Last updated 2026-07-29 22:59
"ESLint" matching MCP tools:
- 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.
- Summarizes large lint, test, or CI logs by grouping output per file and counting errors by rule, reading files server-side to keep large content out of Claude's context.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 remove unused import statements to clean up JavaScript/TypeScript code. Detects unused imports safely to reduce bundle size and improve code quality.MIT
Matching MCP Servers
@fictjs/mcpofficial
Alicense-qualityCmaintenanceMCP server for retrieving Fict documentation, running compiler/ESLint/TypeScript diagnostics, and generating shareable Playground links.Last updated12MIT- AlicenseAqualityDmaintenanceEnables 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.Last updated30Apache 2.0
- Automatically fix lint errors in code files by applying VS Code source.fixAll or falling back to eslint, biome, or ruff.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 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
- Retrieve a project-level summary of code linting violations from P3C, ESLint, Stylelint, and Checkstyle, with total counts per tool.Apache 2.0
- Analyze RxJS code snippets for common issues and best practices using regex-based linting. Catches nested subscribes, memory leaks, deprecated patterns without requiring ESLint.MIT
- Retrieve diagnostics (errors and warnings) from linters like TS, ESLint, Pyright, and more. Filter by file path, severity, and limit results for efficient code analysis.MIT
- Invoke selected diagnostic sources and persist their findings to refresh Reef state, returning a per-source summary.Apache 2.0
- Automatically generate AI assistant instruction files from existing project configuration files like .editorconfig, ESLint, and pyproject.toml for Claude, GitHub Copilot, and Cursor.MIT
- Analyzes project coding style and auto-configures ESLint, Prettier, or Ruff to match current conventions.MIT
- Execute whitelisted shell commands for development tasks like npm, git, node, and code quality tools within the AI Development Pipeline workspace.MIT
- Run ESLint on Node.js and TypeScript code to identify and fix linting issues. Supports auto-fix, custom formats, and specific file patterns.Apache 2.0
- Pack primary-file context for SonarQube-style quality-gate preparation, returning related files, suggested test paths, and quality gap cues.