Best for
- AI coding agents that need reliable, structured lint output
- Developers who want to avoid parsing complex terminal text
- Projects using ESLint, Prettier, Biome, or Oxlint
P
Pare Lint
Community
Structured linting and formatting (ESLint, Prettier, Biome, Oxlint) as typed JSON.
- Category
- Dev Tools #355 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js 20+
- Credentials
- No credential needed
- License
- MIT
- Last commit
40FMRS · D
This is a structured lint server designed for AI agents, providing typed JSON output to reduce token consumption and improve reliability. Suitable for workflows that automatically process lint results.
Strongest · Setup experience 11/20 Weakest · Reliability 6/20
Why each score
- Reliability 6/20
- The supplied evidence is only a well-formed server.schema.json manifest and the README, pointing to an npm stdio package @paretools/lint, so the happy path is plausible. However, no source, tests, or CI results for packages/server-lint were provided, so the MCP init handshake, tool list, outputSchema, and error behavior cannot be verified. Deducted heavily for missing execution evidence and uncertainty.
- Security and permissions 6/20
- No credentials, network endpoints, or irreversible delete/deploy defaults appear in the supplied material, and stdio/local transport reduces exposure. But lint/format tools may rewrite workspace files or execute plugin code, and the evidence shows no confirmation mechanism, scoping controls, or data-flow disclosure. Deducted because source-level security analysis is absent; no red-line risk is affirmatively established.
- Maintenance 9/20
- The repository is not archived, the license is MIT, and the manifest carries semantic version 0.22.0, indicating a release process. However, no recent commits, dependency-update history, issue-response evidence, or security-response channel were supplied; CI/codecov badges come only from the README and are not independent evidence. Deducted for incomplete governance and update-path evidence.
- Documentation 8/20
- The README provides a quickstart, tool-filtering environment variables, a troubleshooting table, and client setup links, making the server usable in principle. But the evidence lacks server-lint-specific tool schemas, parameter descriptions, output examples, and limitation disclosures, and most examples refer to sibling servers. Deducted for missing server-level documentation.
- Setup experience 11/20
- The install path is reasonably clear: an npm stdio package, Node >= 20, and README notes on cross-platform wrappers such as cmd /c npx on Windows. However, no exact client configuration example for this specific server was supplied, and static review without runnable verification caps setup at 15. Deducted because no reproducible end-to-end install evidence was provided.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessReads local filesWrites / deletes local files
Not for
- Scenarios where structured output is not needed, such as simple lint checks for human reading
- Projects that do not use common lint/format tools
Required permissions
- Read project files for linting and formatting
- May write files if auto-fix is enabled
Risks and side effects
- Wrapped tools (e.g., ESLint) may have security vulnerabilities; keep them updated
- Structured output may become inaccurate if tool output formats change
- Requires Node.js >= 20
Setup
Before you start
Runtime：Node.js 20+
Other optional settings (1)
PARE_TOOLS
Universal filter across all Pare servers in server:tool,... format (e.g. lint:eslint), taking precedence over per-server variables.
Install via npm and configure as an MCP server over stdio. For example, in Claude Desktop configuration add:
{
"mcpServers": {
"pare-lint": {
"command": "npx",
"args": ["-y", "@paretools/lint"]
}
}
}Check that it works
After connecting, the pare-lint server's tools should appear in your client's tool list; you can also run npx @paretools/init doctor to validate the setup.
Troubleshooting
- Ensure Node.js version is >= 20
- Run `npx -y @paretools/lint` to cache the package and avoid slow first start
- Check MCP client timeout settings; increase `initTimeout` if needed
Things to try
Once connected, you can ask your AI assistant things like:
- Run ESLint across the project and return the issues as structured JSON.
- Format all files in src/ with Prettier.
- Check the repo for Biome rule violations.
- Run Oxlint and report only error-level issues.
Use cases
Get structured lint results from tools like ESLint for direct use by AI agents
Integrate formatter outputs like Prettier into automated workflows
Reduce token consumption of lint output, improving agent efficiency
Supported clients
Claude Desktop
Listed from the project's documentation, not tested by this site.
Overview
Pare Lint is an MCP server that wraps common linting and formatting tools (such as ESLint, Prettier, Biome, Oxlint) and converts their output into structured, schema-validated JSON. This eliminates the need to parse raw terminal text, allowing AI agents to consume lint results directly and reliably, without brittle string parsing or format changes.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method