Texel MCP

What texel-mcp MCP server does

The texel-mcp MCP server provides an MCP interface to the Texel format and toolchain. Texel represents a Minecraft texture as JSON containing a palette and ordered drawing layers. Those layers target named model parts and faces, such as a head front or an arm overlay, and compile deterministically into the PNG files used by the game.

The format supports player skins in classic and slim models, plus layouts for mobs, armor, capes, items, blocks, plants, GUI sprites, particles, paintings, and other Java Edition 1.21 textures. Specs can include animation and emissive content. A review reports JSON paths, fix hints, an art score, and pixel-art guidance alongside rendered images where applicable.

How it works

Rendering accepts a spec inline or a workspace file. The result can include a review sheet, the compiled texture, and optional close-up images. Patches address layers by ID, allowing an agent to change selected operations without resending the entire spec when a workspace file is being edited. Validation returns errors and warnings without producing images.

The texel-mcp MCP server also handles workflows around existing images and collections. texel_import_png converts a texture PNG into an editable spec, while its pixelize option can convert another picture into a texture matching a supported layout. Palette extraction produces main colors, a legend, and a role for each color. Family tools expand a base spec into variants and return or save a lineup. Diffing identifies changed faces and pixels and provides a mask image.

Live sessions serve a page on 127.0.0.1 that updates as renders occur. Specs can be stored on texel.dev.br and loaded again through share links; offline sharing falls back to a self-contained long link. Resource-pack tools assemble specs, families, and folders into a ZIP or directory and check pack issues with file, JSON path, and fix-hint details.

Setup and configuration

The server requires Node.js 20 or later. It is available as the texel-mcp npm package and can be started with npx -y texel-mcp. A bundled plugin/server/texel-mcp.mjs file can instead run directly with Node and does not require npm install.

Register it with an MCP client using the usual mcpServers configuration. The server can receive --workspace followed by an absolute directory. All writes are confined to one workspace: the command-line option takes precedence, followed by TEXEL_WORKSPACE, followed by the directory where the server starts. Paths resolving outside that workspace are refused. Without an explicit workspace, files go to the server's starting directory.

The repository also provides a Claude Code plugin, which adds the minecraft-skin-design skill and writes files to the project directory. The plugin marketplace commands are documented in the repository, and a local build can be started by pointing the client at its generated server file.

Tools and capabilities

Available MCP tools include:

• Render, review, validate, patch, and save individual specs.
• Start live rendering sessions and share or pull specs through links.
• Render and save texture families with lineup images and member scores.
• Import PNGs, pixelize images, extract palettes, and retrieve bundled examples or documentation.
• Build and check resource packs, including animation metadata and related generated files.
• Compare two specs by face and pixel, with a difference mask.

texel_save can write in-game texture files, source JSON, and optionally a review sheet. Pack checking accepts an existing resource pack and reports issues with locations and suggested fixes.

Limitations and notes

The texel-mcp MCP server is open source under the MIT license and was listed at version 0.9.0. The repository describes it as in development and beta software. Although the format is versioned, minor releases may still change it, so specs and integrations may need updates.

The server is intended for Java Edition 1.21 layouts described by the project. It does not establish support for arbitrary Minecraft editions or texture layouts beyond those covered by Texel. Share operations use texel.dev.br when storing a spec; offline behavior is a long self-contained link rather than remote storage.