Skip to content
ESLint MCP Server

ESLint MCP Server

v0.3.10
Apache-2.0
eslintlintingjavascripttypescriptcode-quality

Summary

The official ESLint MCP server, shipped inside the ESLint CLI - lets an editor agent lint files, read rule violations and apply fixes using your project's own configuration.

Features

  • Lint files using the project's real ESLint configuration
  • Report which rules are violated and where
  • Apply ESLint autofixes from an agent prompt
  • Also runnable from the ESLint CLI with eslint --mcp
  • Documented setup for VS Code Copilot and Cursor

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "ESLint MCP Server" tools will be available.
{
  "mcpServers": {
    "eslint-mcp": {
      "command": "npx",
      "args": [
        "@eslint/mcp@latest"
      ]
    }
  }
}

Description

ESLint ships an MCP server as part of its CLI, so an AI agent can lint with exactly the configuration your project already uses rather than guessing at style from context.

Running it

Two equivalent commands:

npx @eslint/mcp

or straight from the CLI you already depend on:

npx eslint --mcp

The server is designed for IDE-based MCP clients. ESLint documents setup for VS Code with Copilot Chat (a .vscode/mcp.json file with a stdio server, or MCP: Add Server from the Command Palette) and for Cursor (.cursor/mcp.json). Registering it in User Settings rather than Workspace Settings makes it available across every project.

What it is good for

Once the server is registered and its tools are toggled on in agent mode, prompts like "check this file for linting errors", "fix all ESLint issues in the current file" and "show me what ESLint rules are being violated" are handled by ESLint itself - the same rules, plugins and overrides that run in CI, not an approximation of them.

Notes

ESLint must be installed in the project or globally for the server to have a configuration to work from. If tools do not appear, MCP: List Servers followed by Show Output surfaces the server log. Apache-2.0 licensed; the package lives in the eslint/rewrite monorepo and the setup guide is part of the main ESLint documentation.

Related MCP Servers

New

Microsoft's official MCP server for Azure DevOps - work items, repos, pipelines, wikis, test plans and iterations, reachable from any MCP client in plain language.

Developer Tools

MCP: Serena

by Oraios AI

New

Semantic code toolkit for coding agents — symbol-level search, editing and refactoring backed by language servers or the JetBrains platform.

Developer Tools

MCP: Hugging Face

by Hugging Face

New

Official Hugging Face MCP server: search models, datasets, Spaces and papers on the Hub, read repository files, and call Gradio apps as agent tools.

Developer ToolsWeb & Search
New

GitLab's own MCP server — issues, merge requests, CI/CD pipelines, job logs, wikis and semantic code search over an OAuth-authorised HTTP endpoint.

Developer Tools
Browse all MCP servers →