oxlint-mcp
# oxlint-mcp
MCP server for Oxlint.
Similar to `@eslint/mcp`, but with `oxlint`!
## MCP Setup
This package is meant to be configured as an MCP server in your editor/agent client.
### VS Code
Create `.vscode/mcp.json` in your project:
```json
{
"servers": {
"Oxlint": {
"type": "stdio",
"command": "npx",
"args": ["oxlint-mcp@latest"]
}
}
}
```
### Cursor
Create `.cursor/mcp.json` in your project:
```json
{
"mcpServers": {
"oxlint": {
"command": "npx",
"args": ["oxlint-mcp@latest"],
"env": {}
}
}
}
```
Optional global configuration: `~/.cursor/mcp.json`
### Windsurf
Add this to `~/.codeium/windsurf/mcp_config.json`:
```json
{
"mcpServers": {
"oxlint": {
"command": "npx",
"args": ["oxlint-mcp@latest"],
"env": {}
}
}
}
```
## Troubleshooting
- In VS Code, run `MCP: List Servers` and check server logs with `Show Output`.
- Run `npx oxlint-mcp@latest` directly in terminal to confirm the server can start.
- Ensure Node.js and `npx` are available in the same environment as your MCP client.
## License
Apache-2.0
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.