Install as a tool

Give any agent native Texel tools: a portable Agent Skill and an MCP server (with an interactive 3D viewer for MCP Apps hosts). The quickest route is the prompt on the developer page: paste it into your agent and it installs the skill itself.

Agent Skill

The minecraft-skin-design skill follows the open Agent Skills format (a SKILL.md with name and description frontmatter). It teaches the protocol and works with either the MCP tools or the CLI. Save it in your agent's skills directory; for Claude Code:

bash
mkdir -p ~/.claude/skills/minecraft-skin-design
curl -o ~/.claude/skills/minecraft-skin-design/SKILL.md https://www.texel.dev.br/skills/minecraft-skin-design/SKILL.md

Agents without skill support can read /agent.md instead: the protocol, spec reference and art guide in one file.

MCP server

texel-mcp.mjs is a single file with no install step: the compiler, docs, examples, schemas and the 3D viewer are embedded. Requires Node 18+.

bash
curl -O https://www.texel.dev.br/texel-mcp.mjs

Claude Code

bash
claude mcp add texel --scope user -- node /absolute/path/texel-mcp.mjs

Files are written to the directory the server runs in. Pin it with --env TEXEL_WORKSPACE=/path/to/skins or the --workspace <dir> flag.

Claude Desktop, Cursor, VS Code and other clients

json
{
  "mcpServers": {
    "texel": {
      "command": "node",
      "args": ["/absolute/path/texel-mcp.mjs", "--workspace", "/absolute/path/skins"]
    }
  }
}

What the server provides

KindNamePurpose
tooltexel_renderCompile + review; returns the review sheet image. Opens the 3D viewer in MCP Apps hosts.
tooltexel_patchApply a spec patch (change layers by id) and render the result like texel_render.
tooltexel_liveStart a live session: returns a studio URL where the person watches every texel_render.
tooltexel_shareShort share link (/s/<id>) for a spec.
tooltexel_pullThe spec behind a share link, to keep developing an existing skin.
tooltexel_validateFast error check, no images.
tooltexel_saveWrite the texture's files (.png, block parts, animation .png.mcmeta, _eyes), .skin.json and an optional sheet to the workspace.
tooltexel_render_familyExpand a family; lineup image + per-member scores.
tooltexel_save_familyWrite every member plus lineup.png.
tooltexel_import_pngTurn an existing PNG into an editable spec; with pixelize, any picture (concept art, an HD skin) first.
tooltexel_packBuild a resource pack (.zip or folder) from specs, families and folders, with pack.mcmeta, .mcmeta files and, on request, models.
tooltexel_check_packCheck any resource pack: format and versions, names, PNGs, animations, GUI scaling, entity texture sizes, broken references, unused textures.
tooltexel_diffWhich faces a change touched, with a pixel mask.
tooltexel_get_example, texel_read_docsOffline examples and docs.
resourcetexel://docs/{page}, texel://examples/{id}, texel://schema/{name}Same content as resources.
resourceui://texel/viewerMCP App: interactive 3D preview with a feedback box that posts back to the chat.
promptdesign_skin, design_texture, continue_skin, design_family, critique_skinProtocol runbooks with arguments.

All write tools are confined to the workspace directory; paths outside it are rejected.

Updates

Downloaded copies don't update themselves. Once a day the CLI and the MCP server fetch /version.json (the current release and where its files live) and compare it with their own version. When a newer release is out, the CLI prints the update steps on stderr and the MCP server adds them to the next tool result, with the release notes, so the agent can download the new texel.mjs, texel-mcp.mjs and SKILL.md over the old ones before its next command. The run that printed the notice completed normally. The check waits at most 1.5 s, is cached in ~/.texel/, stays silent offline, and is skipped when CI or TEXEL_NO_UPDATE_CHECK=1 is set. node texel.mjs --version and node texel-mcp.mjs --version print the installed version; the skill carries it in metadata.version.