texel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEXEL_SITE | No | Points texel.dev.br features (share, pull, live) at another origin. | |
| TEXEL_WORKSPACE | No | The workspace directory for all writes. Can also be set with the --workspace command-line argument or defaults to the directory the server was started in. | |
| TEXEL_NO_UPDATE_CHECK | No | Set to 1 to skip the daily update check. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| texel_renderA | 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×64 for a player skin), a text render and a close-up of some parts. Deterministic; never modifies files. |
| texel_patchA | 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 "-" 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 to that file and returns only the review and the sheet. |
| texel_validateA | Check a spec for errors and warnings without rendering images. Cheap; use it after every edit. |
| texel_saveA | Compile a spec and write .png (the skin), .skin.json (the source) and optionally .sheet.png into the workspace (/app). Refuses specs with errors. |
| texel_liveA | 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_shareA | Store the spec on https://www.texel.dev.br and return a short link (https://www.texel.dev.br/s/) that opens the exact skin in the studio. Falls back to a long self-contained link when offline. |
| texel_pullA | Load the spec behind a Texel share link (https://www.texel.dev.br/s/, a bare id, or a long studio link with #z= / #spec=) so you can keep developing an existing skin. Returns the spec JSON. |
| texel_render_familyA | 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_familyA | Expand a family and write /.png and .skin.json for every member, plus /lineup.png, into the workspace (/app). Refuses families with errors. |
| texel_import_pngA | Convert an existing PNG in the workspace into an editable spec, one layer per painted face, palette keys c01…cNN. A player skin (64×64 or legacy 64×32) by default; pass layout for a mob, armor, cape, item or block texture. Rename palette keys to material names before editing. |
| texel_paletteA | 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_diffA | 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_exampleA | Return a complete, working example spec to learn from or fork. Skins: explorer, knight, robot, astronaut, wizard, cozy, winged-pig, miner-zombie, creeper, mud-pig, bronze-armor, banner-cape, ember-blade. Family: guild. |
| texel_read_docsA | Read a documentation page as markdown. Pages: protocol (Skin Agent Protocol), spec (Skin spec reference), art-guide (Skin art guide), families (Skin families), api (Agent interfaces), install (Install as a tool). Read "spec" before writing your first spec. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design_skin | Run the Skin Agent Protocol for one skin, from brief to saved PNG. |
| continue_skin | Keep developing an existing skin from its share link, changing only what is asked. |
| design_family | Design a coherent set of skins (teams, factions, tiers) as one family document. |
| critique_skin | Review an existing spec against the protocol rubric and propose concrete layer patches. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema-skinspec.v1 | |
| schema-skinfamily.v1 | |
| viewer | Interactive 3D preview for texel_render results (MCP Apps). |
| protocol | Protocol, spec reference, art guide, families and interfaces. |
| spec | Protocol, spec reference, art guide, families and interfaces. |
| art-guide | Protocol, spec reference, art guide, families and interfaces. |
| families | Protocol, spec reference, art guide, families and interfaces. |
| api | Protocol, spec reference, art guide, families and interfaces. |
| install | Protocol, spec reference, art guide, families and interfaces. |
| explorer | Complete skin specs and one family. |
| knight | Complete skin specs and one family. |
| robot | Complete skin specs and one family. |
| astronaut | Complete skin specs and one family. |
| wizard | Complete skin specs and one family. |
| cozy | Complete skin specs and one family. |
| winged-pig | Complete skin specs and one family. |
| miner-zombie | Complete skin specs and one family. |
| creeper | Complete skin specs and one family. |
| mud-pig | Complete skin specs and one family. |
| bronze-armor | Complete skin specs and one family. |
| banner-cape | Complete skin specs and one family. |
| ember-blade | Complete skin specs and one family. |
| guild | Complete skin specs and one family. |
TDQS
Scored across 14 tools
Each tool has a clearly distinct role: patch, validate, render, save, family rendering/saving, live session, share, pull, import, palette, diff, examples, and docs. The closest overlaps (render vs validate, live vs share) are explicitly differentiated by descriptions and do not create misselection risk.
All names use lowercase snake_case with a consistent texel_ prefix, which makes them predictable. The only minor deviation is that some names are verb-only or noun-only (texel_live, texel_palette, texel_diff) rather than following a strict verb_noun pattern throughout.
The 14 tools are well-scoped for a skin-spec design, validation, rendering, family, and sharing workflow. Each tool appears to earn its place, with no obvious filler or missing core action.
The surface covers the full lifecycle: learn from examples/docs, create/import specs, edit via patch, validate, render, diff, save, expand families, share, pull, and use a live session. No critical CRUD or workflow gap is apparent for the stated domain.