MCP Server
The agent-native way into Thrixel, for Claude Code, Codex, and Cursor.
Thrixel is built agent-first. thrixel-mcp gives coding agents a native way to
create, edit, and work with 3D assets, in Claude Code, Codex, Cursor, and any
other MCP-compatible client.
It exposes Thrixel as tools an agent can discover and use as part of a larger build, and it runs on the same REST API documented here.
What the server adds is the lifecycle. It holds the operation open while the work runs, turns HTTP errors into a next action, writes the GLB to disk, and hands back a thumbnail. An agent can generate an asset, see what it made, modify it, bring it into a scene, and keep building, all in one pass.
Install
Nothing to clone or build. uvx fetches the
published package on each launch, so @latest keeps itself current.
That prints a link and a short code. Open it, confirm the code matches, approve.
The key lands in ~/.thrixel/credentials.json. Sign-up happens on that page too
if you do not have an account yet, so this works from a cold start.
Then register the server with your agent:
Use --scope user
claude mcp add defaults to --scope local, which registers the server for
the current directory only. Every new project then starts with no Thrixel
tools. User scope registers it once for the whole machine.
An MCP client loads its servers once, at session start. Register before you open the agent, or restart the session afterwards.
What it exposes
21 tools, all backed by endpoints on this site. They are intent-level rather
than endpoint-level, which is the one place the shapes differ: an agent asking
to cut a triangle count does not know that a detailed mesh has to go through
remesh while everything else goes through decimate, so thrixel_reduce_triangles
reads the parent's phase and routes for it.
| Doing | Tools |
|---|---|
| Generate | thrixel_create_model, thrixel_sculpt_model |
| Refine | thrixel_autofix_model, thrixel_edit_model, thrixel_detail_model, thrixel_retexture_model, thrixel_reduce_triangles, thrixel_group_parts |
| Inspect | thrixel_inspect_model, thrixel_job_status, thrixel_list_assets |
| Organize | thrixel_start_project, thrixel_list_projects, thrixel_add_project_source, thrixel_list_project_sources |
| Export | thrixel_download |
| Account | thrixel_account_status, thrixel_pricing, thrixel_buy_cubes, thrixel_upgrade_plan, thrixel_billing_portal |
Waiting uses SSE with polling as a fallback, so a long detail pass reports progress instead of going silent.
Using the API directly
The MCP server is the agent-native path, not a gate. Every capability is a plain HTTP call: see Getting Started for authentication and a quickstart, and Job Status for the polling and streaming contracts the server implements internally.