@eslint/mcp
MCP ServerFreeMCP server for ESLint
Capabilities8 decomposed
mcp-native eslint rule execution and linting
Medium confidenceExposes ESLint's core linting engine as an MCP resource/tool, allowing Claude and other MCP clients to invoke ESLint rules against code without spawning separate processes. Implements ESLint's plugin architecture through MCP's tool-calling interface, enabling dynamic rule configuration and multi-file linting workflows within a single MCP session.
First MCP server to expose ESLint as a native tool-calling interface, eliminating subprocess spawning and enabling stateful linting sessions within MCP's request-response model. Leverages ESLint's plugin architecture directly rather than wrapping CLI output.
Faster and more composable than invoking ESLint CLI via subprocess calls because it keeps the linting engine resident in the MCP process and integrates with Claude's native tool-calling, avoiding serialization overhead and enabling multi-step linting workflows.
dynamic eslint configuration discovery and application
Medium confidenceAutomatically discovers and loads ESLint configuration files (.eslintrc.js, .eslintrc.json, .eslintrc.yml, eslintrc.config.js) from the project hierarchy, parses them, and applies rule sets and parser options to linting operations. Supports ESLint's cascading configuration model where nested .eslintrc files override parent configs, and handles environment-specific overrides (browser, node, es6, etc.).
Implements ESLint's full cascading configuration resolution algorithm within the MCP server, allowing it to respect project-specific rule sets without requiring users to re-specify configs. Handles extends chains and environment overrides automatically.
More intelligent than naive CLI wrapping because it understands ESLint's configuration inheritance model and can apply the correct rule set to any file in the project without user intervention, matching the behavior of ESLint's native config resolution.
multi-file batch linting with parallel execution
Medium confidenceAccepts a list of file paths or glob patterns and lints them in parallel using Node.js worker threads or async I/O, returning aggregated results with per-file diagnostics. Implements ESLint's caching layer to avoid re-linting unchanged files, and supports filtering results by severity (error, warning) or rule name.
Implements parallel linting using Node.js async I/O within the MCP server's event loop, avoiding the overhead of spawning separate ESLint CLI processes. Integrates ESLint's built-in caching to skip re-analysis of unchanged files.
Faster than running ESLint CLI multiple times because it keeps the linting engine warm in memory and parallelizes file processing, while still respecting ESLint's cache invalidation logic.
automated fix application and suggestion generation
Medium confidenceInvokes ESLint's built-in --fix mechanism to automatically correct violations that have fix implementations (e.g., semicolon insertion, whitespace normalization). For violations without automatic fixes, generates structured suggestions with before/after code snippets and rule documentation links, enabling Claude to propose manual fixes or ask for user confirmation.
Exposes ESLint's fix engine through MCP's tool interface, allowing Claude to apply fixes as part of a multi-turn conversation. Generates structured fix suggestions for non-auto-fixable rules by parsing rule metadata and documentation.
More interactive than running ESLint --fix from the CLI because it allows Claude to preview fixes, ask for confirmation, and apply them selectively, enabling a collaborative code improvement workflow.
rule metadata and documentation retrieval
Medium confidenceExposes metadata for all loaded ESLint rules (name, description, category, fixable, deprecated status) and provides links to official documentation. Allows filtering rules by category (best-practices, errors, style, etc.) and searching by name or keyword, enabling Claude to explain rules to users and recommend relevant rules for specific code patterns.
Indexes ESLint's rule definitions at server startup and exposes them as searchable MCP resources, allowing Claude to provide in-context rule explanations without external API calls. Includes deprecated rule detection and migration guidance.
More efficient than having Claude search ESLint's documentation website because rule metadata is pre-indexed and available instantly, and Claude can provide contextual explanations tailored to the user's code.
custom rule plugin loading and execution
Medium confidenceDynamically loads ESLint plugins (e.g., eslint-plugin-react, eslint-plugin-vue) from node_modules and registers their rules with the linting engine. Supports plugin configuration options and namespace-prefixed rules (e.g., react/jsx-uses-react). Validates plugin compatibility with the current ESLint version before loading.
Implements ESLint's plugin loading mechanism within the MCP server, allowing plugins to be discovered and loaded from the project's node_modules without CLI invocation. Includes version compatibility checking.
More flexible than static ESLint CLI because it allows plugins to be loaded dynamically based on project configuration, and Claude can work with framework-specific rules (React, Vue, etc.) without separate tool invocations.
parser selection and language support
Medium confidenceSupports multiple ESLint parsers (default Espree, @babel/eslint-parser, @typescript-eslint/parser, vue-eslint-parser, etc.) and automatically selects the appropriate parser based on file extension and ESLint configuration. Handles parser options (ecmaVersion, sourceType, parserOptions) and validates parser compatibility with the target file type.
Implements ESLint's parser resolution algorithm within the MCP server, automatically selecting the correct parser for each file type based on configuration. Supports all major ESLint parsers (Espree, Babel, TypeScript, Vue, etc.).
More intelligent than a generic linter because it understands ESLint's parser ecosystem and can lint TypeScript, JSX, Vue, and other non-standard JavaScript variants without user configuration, matching the behavior of ESLint CLI.
severity filtering and result aggregation
Medium confidenceFilters linting results by severity level (error, warning, off) and aggregates statistics across multiple files. Supports custom severity mappings (e.g., treat warnings as errors) and generates summary reports with violation counts, most-violated rules, and files with the most issues. Enables Claude to provide targeted feedback based on severity thresholds.
Implements multi-dimensional filtering and aggregation on linting results, allowing Claude to provide context-aware feedback based on severity, rule category, and file impact. Supports custom severity mappings for organizational standards.
More flexible than ESLint's built-in --max-warnings flag because it allows real-time filtering and aggregation, enabling Claude to tailor feedback to the user's priorities (e.g., show only errors for a quick review, or show all violations for a detailed audit).
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with @eslint/mcp, ranked by overlap. Discovered automatically through the match graph.
@eslint/mcp
MCP server for ESLint
mcp-tool-lint
Static linter for MCP tool definitions — catch quality defects before deployment
clj-kondo-MCP
** - Clojure linter
mcp-schema-lint
CLI linter for MCP tool/resource schemas
@toolspec/core
MCP tool schema linting and quality scoring engine
nx-mcp
A Model Context Protocol server implementation for Nx
Best For
- ✓AI-assisted code quality workflows using Claude or other MCP-compatible LLMs
- ✓Teams building agentic coding assistants that need deterministic linting feedback
- ✓Developers integrating ESLint into MCP-based development tools
- ✓Teams with existing ESLint configurations who want to reuse them in AI-assisted workflows
- ✓Monorepos with per-package ESLint configs
- ✓Projects using custom ESLint plugins (e.g., eslint-plugin-react, eslint-plugin-vue)
- ✓CI/CD pipelines that need fast, parallel linting feedback
- ✓Large codebases (100+ files) where sequential linting is too slow
Known Limitations
- ⚠Requires ESLint configuration files (.eslintrc.js, .eslintrc.json, etc.) to be present in the project root or specified path
- ⚠No built-in caching of lint results — each invocation re-parses and re-analyzes the target file
- ⚠Limited to ESLint's rule set; custom rules must be installed as npm packages and discoverable by the MCP server
- ⚠Performance degrades on very large codebases (1000+ files) without explicit file filtering
- ⚠Does not support ESLint v9+ flat config format (eslint.config.js) — only legacy .eslintrc formats
- ⚠Custom parser plugins must be installed as npm dependencies; cannot load parsers from arbitrary URLs
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Package Details
About
MCP server for ESLint
Categories
Alternatives to @eslint/mcp
Are you the builder of @eslint/mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →