PixelLab Pip vs Aseprite Claude Connector
PixelLab Pip is a plugin bundle for AI coding tools published by Shilo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Aseprite Claude Connector is an MCP server published by UmarMuhammad18. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Aseprite Claude Connector | |
|---|---|---|
| Community marketplace shilo/pixellab-pip | Not seen in the last pass Version: 3.2.5 Forks (GitHub): 1 Stars (GitHub): 46 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PixelLab Pip | Aseprite Claude Connector |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 46 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-08 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (aseprite-claude-connector) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/shilo/pixellab-pip | github.com/umarmuhammad18/aseprite-claude-connector |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen (differs) | 2026-11-05 | 2026-11-12 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PixelLab Pip
Routes PixelLab asset/API requests across MCP, REST v2, website/editor workflows, Aseprite, Pixelorama, and legacy v1.
Aseprite Claude Connector
Let Claude draw in a running Aseprite, and export straight to Godot or Unity
How to run each
PixelLab Pip As a Claude Code plugin
/plugin marketplace add shilo/pixellab-pip
/plugin install pixellab-pip@pixellab-pip-pluginsAseprite Claude Connector As a local MCP server: PyPI package
claude mcp add --transport stdio aseprite-claude-connector -- uvx aseprite-claude-connectorCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of PixelLab Pip publish no settings it asks for, so we do not compare settings.
What it can do: PixelLab Pip · What it can do: Aseprite Claude Connector · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.