Connect an agent

TextureScript is built so that an agent can draw textures with it. An agent needs two things: the authoring skill, which teaches it how to draw vanilla-style textures, and the tools, either through a shell or over MCP.

Give it the skill

Export the skill to a folder the agent can read:

texturescript skill my-skill

Then extract the vanilla reference textures it mentions from your own Minecraft jar:

texturescript fetch --skill my-skill

fetch --check --skill my-skill reports missing or changed references without writing. If no jar is available, the agent can still use the authored corn example; it should say that the vanilla comparison was unavailable.

For Claude Code, put the exported folder where your skills live, for example .claude/skills/texturescript/.

Give it the tools over a shell

An agent with a shell runs texturescript like you do. Most commands take --json for output that is easier to parse.

Give it the tools over MCP

An agent without a shell can use the MCP server, which speaks MCP on stdio:

claude mcp add texturescript -- texturescript mcp

Other clients take the same command:

{ "mcpServers": { "texturescript": { "command": "texturescript", "args": ["mcp"] } } }

The server offers render, lint and shoot, and returns their pictures as images the agent can look at. It also serves the skill as resources, starting at texturescript://skill/SKILL.md. Relative paths are relative to the directory the server starts in, so start it in your project. Pass --jar PATH or --no-jar to choose the vanilla blocks for shoot.

The tools and their parameters are listed in MCP server.