@eslint/mcp
MCP server for ESLint
No outside reports on file
Use this tool only on code you trust and in isolated projects, since it can read files and run ESLint plugins that execute code.
Based on public adoption and transparency signals as of Oct 26, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourcenpm (@eslint/mcp)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y @eslint/mcpEverything known
We found nothing about this project in the sources we read (last checked 2026-10-31). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-31
Popularity grade: D (from public signals such as stars and downloads, not a code review). Graded 2026-10-26.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-31.
About @eslint/mcp
This is a Model Context Protocol (MCP) server that connects ESLint (a code quality checker) to AI assistants like Claude. It lets the AI analyze JavaScript code for bugs and style problems, then get detailed feedback about what needs fixing.
Who it’s for
Developers who use Claude Desktop or other MCP-compatible AI tools and want the AI to help find and fix code quality issues in JavaScript projects.
Alternatives
- ESLint CLI with manual review: Run ESLint directly and read output yourself (more control, less AI). - Prettier MCP server: If you only need code formatting, not linting feedback. - Native code analysis in Claude: Ask Claude to review code without an MCP connector (slower, no real-time linting).
Setup
Check these steps against the project’s own instructions before running anything.
Follow the project's README for installation and configuration instructions specific to your setup.
Why this grade
Signal-based grade (1/7 points): no public source code found. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- Weekly npm downloads
- 44.6k
- Listing last refreshed
- 2026-10-30
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- File system access: The server can read and analyze any JavaScript files the AI asks it to check, potentially exposing source code or secrets left in comments. - ESLint plugin execution: ESLint can run custom plugins that may execute arbitrary code during linting. - AI misdirection: A prompt injection attack in code comments could trick the AI into requesting analysis of sensitive files or misinterpreting results. - Dependency chain: The server depends on ESLint and its ecosystem; compromised dependencies could inject malicious code. - Configuration exposure: ESLint config files might contain sensitive information like API keys or internal paths.
How to lower the risk
Least-privilege permissions
- Run only in projects where you've reviewed the ESLint configuration.
- Limit which directories the AI can analyze.
Network isolation
- Keep the MCP server offline from external networks if possible.
- Disable any ESLint plugins you don't recognize.
Monitoring
- Log which files the AI requests to analyze.
- Watch for unusual ESLint plugin installations.
Red flags to watch for
- Unexpected new ESLint plugins in your config files.
- Requests to analyze files outside your current project.
- Strange or suspicious code comments before using this tool.
Questions
How do I install @eslint/mcp?
Run npx -y @eslint/mcp in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/eslint/rewrite.
Are there security reports about @eslint/mcp?
No reports found for this package in our research (last checked 2026-10-31). @eslint/mcp currently holds Grade D (High risk signals) based on public adoption and transparency signals. Key risk areas to watch include file system access.
Is @eslint/mcp actively maintained?
@eslint/mcp has 44.6k weekly npm downloads, with its latest repository commit pushed on 2026-10-23. Our directory data was last refreshed on 2026-10-30. Check recent commit activity, release tags, and open issues at github.com/eslint/rewrite before pinning it in production.
What are alternatives to @eslint/mcp?
Notable alternatives to @eslint/mcp include ESLint CLI with manual review (Run ESLint directly and read output yourself (more control, less AI). - **Prettier MCP server**: If you only need code formatting, not linting feedback. - **Native code analysis in Claude**: Ask Claude to review code without an MCP connector (slower, no real-time linting)). You can also compare @eslint/mcp side by side with other MCP servers in the Related tools section on this page.
Key facts
- Type
- App connector
- Publisher
- eslint
- Source code
- github.com/eslint/rewrite
- Install command
- npm install @eslint/mcp
- Est. context load
- ~1k tokens / turn (~6 tool schemas, 0.5% of 200k context)
- Popularity
- 44.6k weekly npm downloads
- Last updated
- 2026-10-30
- Last graded
- 2026-10-26
Community
Discussions for @eslint/mcp
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.