Texel MCP server

Read from the package source without running it. The installed server may list more.

• texel_check_pack

  Check a resource pack (a folder or a .zip in the workspace, …), not only ones Texel made: pack.mcmeta and the versions its format covers, file and namespace names, PNGs, .mcmeta animations and GUI scaling, entity texture sizes against Texel's layouts, models, block states, item definitions and particles that point at missing files, and unused textures. Each issue has the file, a JSON path and a fi

• texel_diff

  Compare two specs pixel by pixel and report which faces changed. Use it to confirm a patch touched only what you intended. Returns the changed-pixel mask over the texture map (magenta = changed).

• texel_get_example

  Return a complete, working example spec to learn from or fork. Skins: …. Family: guild.

• texel_import_png

  Convert an existing PNG in the workspace into an editable spec, one layer per painted face, palette keys c01\u2026cNN. A player skin (64\xD764 or legacy 64\xD732) by default; pass layout for a mob, armor, cape, item or block texture. With pixelize, any picture becomes a texture of the layout's size first (concept art or a render on a white background \u2192 a 16\xD716 item; an HD 128\xD7128 skin \

• texel_live

  Start (or reuse) a live session and return a studio URL for the user. While it runs, every texel_render result appears in their open browser tab immediately, so they can watch the skin evolve and give feedback mid-way. Call it before the first render and share the URL with the user.

• texel_pack

  Build a Minecraft resource pack from spec files, family files and folders of them in the workspace (…): every texture at its "asset" path (or its layout's default: vanilla paths for mobs, item/<name> for items\u2026), with .png.mcmeta, _eyes files, particle definitions, pack.mcmeta for the Minecraft version, and with models: true also the models, block states and item definitions items and blocks

• texel_palette

  Read a reference PNG in the workspace (concept art, a photo of a figure, another skin) and return its main colors, most common first, each with a role (shadow, midtone, highlight, neutral, accent), as a ready spec "palette" and "legend". Use it to match a reference instead of guessing hex values; derive the other tones with "~" steps.

• texel_patchwrite action

  Apply a patch to a spec (update, replace, add or remove layers by id; change palette, legend or meta) and render the result like texel_render. Layers without an id first get "<op>-<index>" and keep it, so the next patch can use the same ids. Entries that cannot apply are skipped and reported. With "spec", returns the patched spec, the review and the sheet. With "file", writes the patched spec back

• texel_pull

  Load the spec behind a Texel share link (…/s/<id>, a bare id, or a long studio link with #z= / #spec=) so you can keep developing an existing skin. Returns the spec JSON.

• texel_read_docs

  Read a documentation page as markdown. Pages: ${DOC_PAGES.map((p) =>

• texel_render

  Compile a skin spec and review it. Returns a review sheet image (front | back | right | left views + raw texture), the review (score, issues with JSON paths and fix hints, art checks, craft advice, suggested next steps) and, on request, the texture (64\xD764 for a player skin), a text render and a close-up of some parts. Deterministic; never modifies files.

• texel_render_family

  Expand a family (base spec + variants and/or a matrix of axes) and review every member. Returns a lineup image (front and back of each member, in order) and a per-member score table.

• texel_save

  Compile a spec and write <path>.png (the texture), <path>.skin.json (the source) and optionally <path>.sheet.png into the workspace (…). Also writes every other file the texture is in game: a block's <path>_top.png / _side.png\u2026, an animation's strip with <path>.png.mcmeta, a particle's <path>_0.png\u2026, the glowing pixels as <path>_eyes.png. Refuses specs with errors.

• texel_save_family

  Expand a family and write <directory>/<member-id>.png and .skin.json for every member, plus <directory>/lineup.png, into the workspace (…). Refuses families with errors.

• texel_share

  Store the spec on … and return a short link (…/s/<id>) that opens the exact skin in the studio. Falls back to a long self-contained link when offline.

• texel_validate

  Check a spec for errors and warnings without rendering images. Cheap; use it after every edit.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 8 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 4,460 AI and agents servers

Tools

16

the typical AI and agents server has 6

Tools that change things

6%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

100

more than 64% of 1,538 AI and agents servers with a package

Texel: common questions

Is Texel MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Texel safety report

How do I install Texel?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Texel need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Texel maintained?

The last commit was 29 days ago (2026-10-06). The latest release is v0.9.2.

What can I use instead of Texel?

Servers from other publishers that do the same job: OpenWorkProof MCP server and Maple MCP server.

How does Texel compare with other AI and agents MCP servers?

safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 16 (the typical AI and agents server has 6); tools that change things 6% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.