oxlint-mcp
Related Servers
Alternatives to oxlint-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server that provides 37+ intelligent development tools across JavaScript/TypeScript, Rust, and Python with security-first design and high-performance features.24 npm1MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.4018 npm3MIT
- AlicenseAqualityCmaintenanceAn MCP server that exposes Pyright language server functionality for Python, providing tools for type checking, code completions, and finding definitions. It enables AI models to perform static analysis and code formatting through the Model Context Protocol.7MIT
- AlicenseCqualityCmaintenanceDeterministic MCP server for semantic analysis of JavaScript/TypeScript codebases, including frameworks like Vue, Angular, React, and Node. It provides tools for type checking, code metrics, framework-specific analysis, and quality heuristics via static parsing.1001MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for advanced code analysis and editing with semantic search capabilities, enabling AI assistants to perform complex code operations through a standardized interface.151-
- AlicenseBqualityDmaintenanceAn MCP server that integrates Ruff linting, formatting, and code analysis tools with advanced logging and configuration options for AI coding assistants.41MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'lint-files' has a clear, distinct purpose focused on linting files using Oxlint.
The naming convention is consistent by default since there is only one tool. The name 'lint-files' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency.
A single tool is too few for a server's purpose, as it limits functionality and scope. While the tool is specific to linting, a typical server would benefit from additional tools for tasks like configuration or result analysis, making this feel thin and under-scoped.
The tool provides a basic linting operation, but there are notable gaps in the surface. For a linting domain, expected features like configuring rules, ignoring files, or formatting results are missing, which could hinder agent workflows and cause workarounds.