texel vs Summer Engine
texel is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
texel is a plugin bundle for AI coding tools published by Bruno Veronez. No marketplace we read lists it any more. Summer Engine is an MCP server published by SummerEngine. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Summer Engine | |
|---|---|---|
| Community marketplace brunovncs/texel-mcp | Removed on 2026-10-15 Version: 0.9.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.3.0 Forks (GitHub): 6 Stars (GitHub): 79 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 2.5.1 Forks (GitHub): 6 Stars (GitHub): 79 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 | texelno longer listed · | Summer Engine |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 79 |
| Forks (GitHub) (differs) | 0 | 6 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | 2 | 83 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/brunovncs/texel-mcp | github.com/summerengine/summer |
| Changes in the last 7 days (differs) | 4 | 5 |
| First seen (differs) | 2026-10-13 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of texel
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
mc-asset — Minecraft Pixel Asset Engine
Deterministic Minecraft pixel-art engine: textures, animation sheets, and pack validation.
-
MCP server that lets AI agents build, check, preview and export game assets in Blender
-
Create and edit on-brand images and videos with reusable character and product references.
-
Draw pixel-art tiles and tilesets for 2D games, with PNG+metadata export for Unity.
-
texel-mcp io.github.Brunovncs/texel-mcp
Minecraft skins and textures as code: JSON specs compiled to PNG, with a review an agent can act on.
-
Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.
What each says it does
texel
Minecraft skin and texture tools: MCP server with a 3D viewer and the minecraft-skin-design skill.
Summer Engine
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
How to run each
texel
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Summer Engine As a remote MCP server
claude mcp add --transport http summer https://mcp.summerengine.com/mcpCommands 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 Summer Engine publish no settings it asks for, so we do not compare settings.
What it can do: texel · What it can do: Summer Engine · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.