Lint, curate & prepare computer-vision datasets from your AI assistant — MCP server, 67 tools
Lint, curate, and prepare computer-vision datasets — right from your AI assistant.
PixLint is an MCP server that gives AI assistants — Claude, Cursor, VS Code, and any MCP client — direct, conversational access to a complete computer-vision dataset toolkit: analyze quality, find duplicates and label errors, clean and curate, split, augment, convert formats, and export to every major training framework.
It runs locally over stdio, or self-hosted on the internet over authenticated HTTP.
Most dataset tooling is either a paid SaaS or a heavy GUI app. PixLint is a single, open-source, self-hostable server an AI agent can drive end to end — and it does things others keep behind paid tiers:
103 operations — 67 tools, 23 resources, 13 prompts.
| Category | What you get |
|---|---|
| Load | COCO · VOC · YOLO · KITTI · folder, plus cloud (S3 / GCS / Azure) |
| Analyze | Duplicates · quality (blur/exposure/noise/contrast) · integrity · class distribution · embeddings · semantic search · outliers · health score |
| Data intelligence | Dataset Doctor readiness report · label-error detection · natural-language query · weak-slice / bias discovery |
| Curate | Filter to a subset · clean (corrupt / out-of-bounds / degenerate / duplicates) · remap classes — each produces a new dataset |
| Augment & transform | YOLO/classification/segmentation pipelines · resize · normalize · format conversion |
| Split | Stratified / random / temporal / grouped · k-fold · data-leakage detection |
| Auto-label | Pretrained COCO-80 detector → pre-annotated dataset |
| Export & publish | PyTorch · TensorFlow · Ultralytics · HDF5 · WebDataset · FiftyOne · CVAT · LabelMe · Hugging Face Hub |
| Pipelines | Compose multi-step workflows and reuse pre-built templates |
pip install pixlint
Optional extras add heavier capabilities:
pip install "pixlint[torch]" # embeddings, auto-labeling, label-error detection
pip install "pixlint[huggingface]" # Hugging Face export + publishing
pip install "pixlint[all]" # everything
Claude Desktop — claude_desktop_config.json:
{
"mcpServers": {
"pixlint": {
"command": "pixlint",
"env": { "CV_DATA_DIR": "/path/to/your/datasets" }
}
}
}
Cursor / VS Code — .cursor/mcp.json or .vscode/mcp.json:
{
"mcpServers": {
"pixlint": {
"command": "pixlint",
"env": { "CV_DATA_DIR": "/path/to/your/datasets" }
}
}
}
CV_DATA_DIR is the directory PixLint is allowed to read datasets from.
"Load my dataset at
/data/coco_person, give it a readiness report, then clean it and export for YOLO."
Your assistant calls the right PixLint tools in sequence — diagnose, clean, split, export — and hands back a training-ready dataset.
PixLint touches the filesystem and can be exposed to a network, so protections run on every tool call:
See the Security Guide for the full threat model and the recommended production checklist.
| Guide | Description |
|---|---|
| Getting Started | Installation, configuration, first steps |
| MCP Client Setup | Claude, Cursor, VS Code, and remote/HTTP hosting |
| API Reference | All 67 tools with parameters |
| Security Guide | Threat model, configuration, hosting |
| Pipeline Templates | Pre-built and custom pipelines |
Runnable scripts live in examples/. See CHANGELOG.md for release notes.
PixLint is source-available under the PolyForm Strict License 1.0.0 — see LICENSE. You may use it for permitted (noncommercial) purposes; commercial use, redistribution, or modification requires a separate license from the copyright holder. Contributions are welcome via pull request.
mcp-name: io.github.amitsingh-24/pixlint
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx pixlintMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-amitsingh-24-pixlint": {
"command": "uvx",
"args": [
"pixlint"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.amitsingh-24/pixlint works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.