Pare Lint
Run ESLint, Prettier, Biome, and Oxlint through MCP so your agent fixes lint and format issues with structured JSON feedback.
Overview
Pare Lint is a MCP server for the Ship phase that runs ESLint, Prettier, Biome, and Oxlint and returns typed JSON lint and format results for agent-driven code review.
What is this MCP server?
- Unified typed JSON across ESLint, Prettier, Biome, and Oxlint (4 toolchain families)
- npm @paretools/lint v0.8.1 with stdio MCP transport
- Structured diagnostics agents can map to file edits
- Pare monorepo on GitHub (Dave-London/Pare)
- Reduces opaque terminal lint output in agent loops
- Server version 0.8.1
- 4 named tool families: ESLint, Prettier, Biome, Oxlint
- npm identifier @paretools/lint, stdio transport
Community signal: 128 GitHub stars.
What problem does it solve?
Lint and format output in the terminal is noisy for LLMs, so agents miss rules or apply fixes to the wrong files.
Who is it for?
TypeScript and JavaScript solo builders who want one MCP entry for multiple linters during pre-ship review with Claude Code or Cursor.
Skip if: Polyglot repos with no JS toolchain, or teams that rely solely on hosted CI without local ESLint/Prettier/Biome/Oxlint installed.
What do I get? / Deliverables
Once configured, your agent receives parseable lint diagnostics and can drive formatter runs without guessing from raw CLI text.
- Typed JSON lint and format results from supported tools
- Agent-actionable file and rule references
- Local stdio MCP server wired for review workflows
Recommended MCP Servers
Journey fit
Linting gates quality right before you ship and during review passes, so ship is the canonical phase even if you run it continuously in build. Review is where automated style and rule violations are interpreted and resolved before merge or release.
How it compares
MCP lint bridge, not a hosted code-quality platform or custom rule authoring skill.
Common Questions / FAQ
Who is pare-lint for?
Developers using MCP agents on JS/TS codebases who want structured lint and format output from ESLint, Prettier, Biome, or Oxlint.
When should I use pare-lint?
Use it before shipping or during review when you want the agent to fix style and rule violations with clear JSON diagnostics.
How do I add pare-lint to my agent?
Add @paretools/lint as a stdio MCP server in your agent config, ensure project-local ESLint/Prettier/Biome/Oxlint are installed, then invoke tools from the session.