What can @eslint/mcp do?

mcp-based eslint rule execution and linting orchestration, eslint rule metadata and documentation retrieval, automatic eslint fix application and suggestion generation, multi-file batch linting with aggregated results, eslint configuration discovery and validation, language-specific linting with parser and plugin support

@eslint/mcp

MCP ServerFree

MCP server for ESLint

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

mcp-based eslint rule execution and linting orchestration

Medium confidence

Exposes ESLint's linting engine as an MCP server, allowing remote clients (Claude, other LLM agents, or tools) to invoke ESLint rule checking and code analysis over the MCP protocol. The server wraps ESLint's core linting API and translates rule violations into structured MCP resource/tool responses, enabling stateless, request-response linting without direct filesystem access from the client.

Solves for

I want Claude or an AI agent to lint my code without running ESLint locally in my IDEI need to integrate ESLint checks into an MCP-aware development tool or agent workflowI want to expose ESLint as a remote service that multiple clients can query for linting resultsI need to run ESLint rules as part of an AI-assisted code review or refactoring pipeline

Best for

AI agent developers building code-aware workflows with Claude or other LLM clients

Teams using MCP-compatible tools (Claude Desktop, custom MCP clients) who want centralized linting

Developers building multi-tool development environments where ESLint must be accessible over MCP

Requires

Node.js 18+ (ESLint 9.x requirement)

ESLint 9.x installed in the MCP server environment

@eslint/mcp npm package

Limitations

Requires a running MCP server process — adds deployment complexity vs. direct ESLint npm module usage

Network latency between MCP client and server adds overhead compared to in-process linting

Configuration must be accessible to the server process; client cannot dynamically inject ESLint configs

What makes it unique

Bridges ESLint (a mature, widely-adopted linting tool) into the MCP ecosystem, enabling AI agents and remote tools to invoke linting without direct filesystem access or subprocess spawning. Uses MCP's resource/tool abstraction to expose ESLint's linting API as a standardized remote service.

vs alternatives

Provides centralized, MCP-native linting for AI agents (vs. agents spawning ESLint subprocesses or calling ESLint via REST APIs), with full access to ESLint's rule ecosystem and configuration system.

eslint rule metadata and documentation retrieval

Medium confidence

Exposes ESLint rule definitions, descriptions, and documentation links as MCP resources or tools, allowing clients to query rule metadata without parsing ESLint's internal rule registry. The server introspects the loaded ESLint ruleset and surfaces rule names, descriptions, categories, and documentation URLs for use in AI-assisted code review or rule recommendation workflows.

Solves for

I want to show Claude the available ESLint rules and their purposes before asking it to fix violationsI need to look up what a specific ESLint rule does and why it was triggeredI want an AI agent to understand the intent behind ESLint rules to provide better explanations to developers

Best for

AI agents providing code review explanations or rule-based refactoring guidance

Interactive tools that need to display ESLint rule documentation to users

Developers building custom linting workflows that require rule context

Requires

Node.js 18+

ESLint 9.x with rule definitions loaded

@eslint/mcp npm package

Limitations

Metadata is static per server startup — changes to ESLint rules require server restart

Only exposes rules loaded in the server's ESLint environment; custom rules must be installed server-side

No filtering or search capability — client must handle rule discovery logic

What makes it unique

Exposes ESLint's internal rule registry as queryable MCP resources, allowing clients to introspect rule definitions without parsing ESLint source code or documentation. Integrates with ESLint 9.x's flat config system to surface rule metadata dynamically.

vs alternatives

Provides programmatic access to rule metadata via MCP (vs. hardcoding rule descriptions or scraping ESLint docs), ensuring metadata stays in sync with the actual ESLint version running in the server.

automatic eslint fix application and suggestion generation

Medium confidence

Invokes ESLint's built-in auto-fix mechanism to automatically correct code violations where rules provide fix implementations. The server applies fixes to code strings or files, returns the corrected code, and optionally provides structured fix suggestions (before/after diffs, rule applied, confidence level) for client-side review or approval workflows.

Solves for

I want Claude to automatically fix ESLint violations in my code and show me what changedI need to apply ESLint fixes as part of an AI-assisted code refactoring pipelineI want to preview what ESLint fixes would do before applying them to my codebase

Best for

AI agents performing automated code cleanup or style normalization

Interactive code editors integrating ESLint fixes into LLM-assisted workflows

CI/CD pipelines using AI agents to auto-fix linting issues before commit

Requires

Node.js 18+

ESLint 9.x with rules that support auto-fix

@eslint/mcp npm package

Limitations

Only rules with fix implementations can be auto-fixed; many rules only report violations without fixes

Fixes are applied in a single pass — some violations may require multiple passes to fully resolve

No rollback mechanism — if a fix introduces new violations, client must handle recovery

What makes it unique

Wraps ESLint's fix API in an MCP-accessible interface, allowing remote clients to request and apply fixes without spawning ESLint processes. Integrates with ESLint 9.x's rule fix system and provides structured fix metadata for client-side approval workflows.

vs alternatives

Enables AI agents to apply ESLint fixes as part of a larger workflow (vs. agents manually rewriting code or calling ESLint CLI), with full access to ESLint's fix implementations and the ability to preview fixes before applying them.

multi-file batch linting with aggregated results

Medium confidence

Accepts multiple code files or file paths in a single MCP request and returns aggregated linting results across all files. The server batches ESLint invocations, deduplicates configuration loading, and returns structured results grouped by file, enabling efficient bulk code analysis for large codebases or multi-file refactoring workflows.

Solves for

I want to lint an entire directory or project and get a summary of all violationsI need to check multiple files for linting issues as part of an AI-assisted code reviewI want to identify which files have the most linting violations to prioritize fixes

Best for

AI agents analyzing or refactoring multiple files in a single workflow

Batch code quality assessment tools or dashboards

CI/CD pipelines checking multiple files for linting compliance

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Batch size is limited by MCP message size and server memory — very large batches may timeout or fail

Results are not cached — re-linting the same files requires re-running the full analysis

No incremental linting — all files are re-linted even if only one changed

What makes it unique

Batches ESLint invocations to analyze multiple files in a single MCP request, reducing overhead vs. individual file requests. Aggregates results with file-level grouping and summary statistics for efficient bulk analysis.

vs alternatives

More efficient than making separate MCP requests per file (reduces network round-trips and server startup overhead), while providing structured aggregation suitable for dashboards or bulk refactoring workflows.

eslint configuration discovery and validation

Medium confidence

Automatically discovers and loads ESLint configuration files (.eslintrc.js, eslint.config.js, or package.json eslintConfig) from the server's working directory and validates the configuration for syntax errors or invalid rule options. The server exposes the loaded configuration as MCP resources, allowing clients to query which rules are enabled, their severity levels, and any configuration errors.

Solves for

I want to know which ESLint rules are active in my project before lintingI need to verify that my ESLint configuration is valid and won't cause linting failuresI want to understand the rule severity levels (error vs. warning) in my project

Best for

Developers debugging ESLint configuration issues

AI agents that need to understand the active rule set before providing recommendations

Tools that display ESLint configuration to users for validation or modification

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Configuration is loaded at server startup — changes to config files require server restart

Only discovers config files in the server's working directory; cannot load configs from arbitrary paths

Validation is limited to ESLint's built-in checks; custom config validators are not supported

What makes it unique

Exposes ESLint's configuration discovery and validation as MCP resources, allowing clients to introspect the active rule set without parsing config files manually. Integrates with ESLint 9.x's flat config system and legacy config support.

vs alternatives

Provides programmatic access to ESLint configuration via MCP (vs. clients parsing config files themselves or calling ESLint CLI with --print-config), ensuring config state is consistent with the server's linting behavior.

language-specific linting with parser and plugin support

Medium confidence

Supports linting of multiple languages (JavaScript, TypeScript, JSX, TSX) by leveraging ESLint's parser and plugin system. The server loads configured parsers (e.g., @typescript-eslint/parser) and plugins (e.g., @typescript-eslint/eslint-plugin) from the server environment, enabling language-specific rule checking and type-aware linting for TypeScript code.

Solves for

I want to lint TypeScript code with type-aware ESLint rulesI need to check JSX/TSX syntax and React-specific linting rulesI want to use custom parsers or language-specific ESLint plugins in my linting workflow

Best for

TypeScript projects using type-aware ESLint rules (@typescript-eslint)

React/JSX projects with React-specific linting rules

Polyglot projects with multiple language linting requirements

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Parsers and plugins must be installed in the server's environment — clients cannot dynamically inject them

Type-aware linting requires TypeScript project setup (tsconfig.json) — adds configuration complexity

Parser performance varies by language; TypeScript parsing is slower than JavaScript

What makes it unique

Leverages ESLint 9.x's flat config system and plugin architecture to support multiple languages and type-aware linting. Integrates with @typescript-eslint and other language-specific plugins without requiring client-side parser installation.

vs alternatives

Provides type-aware linting for TypeScript via MCP (vs. clients running separate TypeScript linters or ESLint CLI with complex config), with full access to the @typescript-eslint rule ecosystem.

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.

MCP Server35

@eslint/mcp

MCP server for ESLint

mcp-native eslint rule execution and lintingdynamic eslint configuration discovery and applicationautomated fix application and suggestion generationrule metadata and documentation retrieval

4 shared capabilities

MCP Server28

@toolspec/core

MCP tool schema linting and quality scoring engine

configurable linting rule engine with custom rule supportmcp tool schema validation and linting

2 shared capabilities

Extension43

ESLint

Real-time ESLint integration with auto-fix.

automatic code correction on file savereal-time inline linting with rule-based pattern matching

2 shared capabilities

MCP Server40

nx-mcp

A Model Context Protocol server implementation for Nx

lint and code quality rule exposure for ai-assisted fixes

1 shared capability

MCP Server44

nx-mcp

A Model Context Protocol server implementation for Nx

lint and code quality rule execution via mcp

1 shared capability

MCP Server23

elisp-dev-mcp

** - elisp (Emacs Lisp) development support tools, running in Emacs.

elisp-syntax-checking-and-error-detection

1 shared capability

Best For

✓AI agent developers building code-aware workflows with Claude or other LLM clients
✓Teams using MCP-compatible tools (Claude Desktop, custom MCP clients) who want centralized linting
✓Developers building multi-tool development environments where ESLint must be accessible over MCP
✓AI agents providing code review explanations or rule-based refactoring guidance
✓Interactive tools that need to display ESLint rule documentation to users
✓Developers building custom linting workflows that require rule context
✓AI agents performing automated code cleanup or style normalization
✓Interactive code editors integrating ESLint fixes into LLM-assisted workflows

Known Limitations

⚠Requires a running MCP server process — adds deployment complexity vs. direct ESLint npm module usage
⚠Network latency between MCP client and server adds overhead compared to in-process linting
⚠Configuration must be accessible to the server process; client cannot dynamically inject ESLint configs
⚠No built-in caching of lint results — each request re-runs the full linting pass
⚠Limited to ESLint's rule set; custom rules must be installed in the server's environment
⚠Metadata is static per server startup — changes to ESLint rules require server restart

Requirements

Node.js 18+ (ESLint 9.x requirement)ESLint 9.x installed in the MCP server environment@eslint/mcp npm packageMCP-compatible client (Claude Desktop, custom MCP client library, or agent framework with MCP support)Valid ESLint configuration file (.eslintrc.js, eslint.config.js, or package.json eslintConfig) in the server's working directoryNode.js 18+ESLint 9.x with rule definitions loadedESLint 9.x with rules that support auto-fix

Input / Output

Accepts: code (JavaScript, TypeScript, JSX, TSX as strings or file paths), ESLint configuration (via .eslintrc or eslint.config.js), rule options and severity levels, rule name (string), optional filter criteria (category, severity), code (JavaScript, TypeScript, JSX, TSX as strings), ESLint configuration specifying which rules to apply, array of code files (strings or file paths), ESLint configuration, optional: specific config file path or config object, language hint or file extension

Produces: structured linting results (violations, warnings, errors with line/column positions), rule metadata (rule name, description, documentation URL), fix suggestions (when ESLint rules provide auto-fix capabilities), rule metadata (name, description, category, documentation URL), rule configuration options (schema, defaults), fix availability flag, fixed code (string), fix summary (rules applied, number of fixes, before/after diffs), remaining violations (if any rules cannot be auto-fixed), aggregated linting results (violations grouped by file), summary statistics (total violations, files with errors, etc.), per-file violation counts and severity breakdown, loaded configuration (rules, severity levels, plugins, parser options), configuration validation results (errors, warnings), active rule list with severity levels, language-specific linting results (violations with language-aware context), type information (for type-aware rules), parser errors (if code is syntactically invalid)

UnfragileRank

Adoption55%(30% weight)

Quality14%(25% weight)

Ecosystem46%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit @eslint/mcp→

Repository Details

Package Details

npm

Registry

0.3.4

Version

29,358

Weekly Downloads

About

MCP server for ESLint

Alternatives to @eslint/mcp

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

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.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

npm

Looking for something else?

Search →

Capabilities6 decomposed

mcp-based eslint rule execution and linting orchestration

Medium confidence

Solves for

Best for

AI agent developers building code-aware workflows with Claude or other LLM clients

Teams using MCP-compatible tools (Claude Desktop, custom MCP clients) who want centralized linting

Developers building multi-tool development environments where ESLint must be accessible over MCP

Requires

Node.js 18+ (ESLint 9.x requirement)

ESLint 9.x installed in the MCP server environment

@eslint/mcp npm package

Limitations

Requires a running MCP server process — adds deployment complexity vs. direct ESLint npm module usage

Network latency between MCP client and server adds overhead compared to in-process linting

Configuration must be accessible to the server process; client cannot dynamically inject ESLint configs

What makes it unique

vs alternatives

Provides centralized, MCP-native linting for AI agents (vs. agents spawning ESLint subprocesses or calling ESLint via REST APIs), with full access to ESLint's rule ecosystem and configuration system.

eslint rule metadata and documentation retrieval

Medium confidence

Solves for

Best for

AI agents providing code review explanations or rule-based refactoring guidance

Interactive tools that need to display ESLint rule documentation to users

Developers building custom linting workflows that require rule context

Requires

Node.js 18+

ESLint 9.x with rule definitions loaded

@eslint/mcp npm package

Limitations

Metadata is static per server startup — changes to ESLint rules require server restart

Only exposes rules loaded in the server's ESLint environment; custom rules must be installed server-side

No filtering or search capability — client must handle rule discovery logic

What makes it unique

vs alternatives

Provides programmatic access to rule metadata via MCP (vs. hardcoding rule descriptions or scraping ESLint docs), ensuring metadata stays in sync with the actual ESLint version running in the server.

automatic eslint fix application and suggestion generation

Medium confidence

Solves for

Best for

AI agents performing automated code cleanup or style normalization

Interactive code editors integrating ESLint fixes into LLM-assisted workflows

CI/CD pipelines using AI agents to auto-fix linting issues before commit

Requires

Node.js 18+

ESLint 9.x with rules that support auto-fix

@eslint/mcp npm package

Limitations

Only rules with fix implementations can be auto-fixed; many rules only report violations without fixes

Fixes are applied in a single pass — some violations may require multiple passes to fully resolve

No rollback mechanism — if a fix introduces new violations, client must handle recovery

What makes it unique

vs alternatives

multi-file batch linting with aggregated results

Medium confidence

Solves for

Best for

AI agents analyzing or refactoring multiple files in a single workflow

Batch code quality assessment tools or dashboards

CI/CD pipelines checking multiple files for linting compliance

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Batch size is limited by MCP message size and server memory — very large batches may timeout or fail

Results are not cached — re-linting the same files requires re-running the full analysis

No incremental linting — all files are re-linted even if only one changed

What makes it unique

vs alternatives

eslint configuration discovery and validation

Medium confidence

Solves for

Best for

Developers debugging ESLint configuration issues

AI agents that need to understand the active rule set before providing recommendations

Tools that display ESLint configuration to users for validation or modification

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Configuration is loaded at server startup — changes to config files require server restart

Only discovers config files in the server's working directory; cannot load configs from arbitrary paths

Validation is limited to ESLint's built-in checks; custom config validators are not supported

What makes it unique

vs alternatives

language-specific linting with parser and plugin support

Medium confidence

Solves for

Best for

TypeScript projects using type-aware ESLint rules (@typescript-eslint)

React/JSX projects with React-specific linting rules

Polyglot projects with multiple language linting requirements

Requires

Node.js 18+

ESLint 9.x

@eslint/mcp npm package

Limitations

Parsers and plugins must be installed in the server's environment — clients cannot dynamically inject them

Type-aware linting requires TypeScript project setup (tsconfig.json) — adds configuration complexity

Parser performance varies by language; TypeScript parsing is slower than JavaScript

What makes it unique

vs alternatives

Provides type-aware linting for TypeScript via MCP (vs. clients running separate TypeScript linters or ESLint CLI with complex config), with full access to the @typescript-eslint rule ecosystem.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @eslint/mcp

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@eslint/mcp

Capabilities6 decomposed

mcp-based eslint rule execution and linting orchestration

eslint rule metadata and documentation retrieval

automatic eslint fix application and suggestion generation

multi-file batch linting with aggregated results

eslint configuration discovery and validation

language-specific linting with parser and plugin support

Related Artifactssharing capabilities

@eslint/mcp

@toolspec/core

ESLint

nx-mcp

nx-mcp

elisp-dev-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @eslint/mcp

Are you the builder of @eslint/mcp?

Get the weekly brief

Data Sources

@eslint/mcp

Capabilities6 decomposed

mcp-based eslint rule execution and linting orchestration

eslint rule metadata and documentation retrieval

automatic eslint fix application and suggestion generation

multi-file batch linting with aggregated results

eslint configuration discovery and validation

language-specific linting with parser and plugin support

Related Artifactssharing capabilities

@eslint/mcp

@toolspec/core

ESLint

nx-mcp

nx-mcp

elisp-dev-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @eslint/mcp

Are you the builder of @eslint/mcp?

Get the weekly brief

Data Sources