sprite-gen vs BlenderLens
sprite-gen is a plugin bundle for AI coding tools published by nakzyu. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). BlenderLens is an MCP server published by pzalutski-pixel. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  sprite-gen |  BlenderLens |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 693e428 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 507 Downloads/week (npm): 444 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 507 Downloads/week (npm): 444 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 | sprite-gen | BlenderLens |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (blenderlens-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 11, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/nakzyu/sprite-gen | github.com/pzalutski-pixel/blenderlens-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
sprite-gen
Generate and manage 2D game sprites using Google Gemini's image generation. This plugin acts as a creative director — it asks about your art style, view angle, and game context before crafting an optimized prompt for Gemini. Supports single sprite generation, anchor-frame based sprite sheets, and sprite management (list, delete, organize). Uses Gemini subscription via browser cookie authentication, no API key needed.
BlenderLens
MCP server that lets AI agents build, check, preview and export game assets in Blender
How to run each
sprite-gen As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sprite-gen@claude-communityBlenderLens As a local MCP server: npm package
claude mcp add --env "BLENDERLENS_TOKEN=<YOUR_BLENDERLENS_TOKEN>" --transport stdio blenderlens -- npx -y blenderlens-mcpRequires: BLENDERLENS_TOKEN (secret)
Commands 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 sprite-gen publish no settings it asks for, so we do not compare settings.
What it can do: sprite-gen · What it can do: BlenderLens · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.