- Home
- Skills
- Game Development
- Customuse MCP: Images, Video, 3D Meshes & Rigs
Works with the AI Agents you already use
Customuse MCP: Images, Video, 3D Meshes & Rigs
Turn your agent into a careful Customuse operator for images, video, 3D meshes, PBR textures, auto-rigging and Roblox-ready assets.
Free
Customuse MCP: Images, Video, 3D Meshes & Rigs
Example session with this skill installed
I need a rigged NPC for my game: a salvage-ship deckhand in a weathered oilskin coat, respirator hanging at the neck, heavy boots. Make it on Customuse, textured and rigged, and keep the cost reasonable.
- Read your context and instructions
- Compiled the customuse mcp
Figures from a measured run of this pipeline on the live Customuse API (2026-09-20).
Your deckhand is done: textured and rigged, in one workflow, for 113 credits total in about 6.5 minutes.
Before starting I checked your balance and confirmed the plan: concept (4) → A-pose cleanup (6) → textured mesh (70) → biped rig (33), about 113 credits. I didn't use autorun, because its budget is a soft cap and tends to overshoot.
What I built
| Step | Node | Credits | Time | Result |
|---|---|---|---|---|
| 1. Concept art | character | 4 | ~20 s | Full-body 3/4 view, transparent background |
| 2. Prep for 3D | imageOptimize (A-pose, white bg, centered) | 6 | ~10 s | Pass-through to the mesher |
| 3. Textured mesh | modelTextureGeneration (2K PBR) | 70 | ~5.6 min | 18,986 tris · 24,455 verts · 4 embedded textures · GLB 8.3 MB |
| 4. Rig | autoRigging (biped) | 33 | ~25 s | 58 joints, skin weights (JOINTS_0 / WEIGHTS_0) |
| Total | 113 | ~6.5 min |
Steps 2–4 ran as one cascade from a single graph edit, so the agent didn't make three separate paid calls.
Your files
Textured mesh (GLB, 8.3 MB): use this for materials. The albedo, normal and ORM maps are also available as separate URLs.
- Rigged mesh (GLB, 1.5 MB): use this for the skeleton and animation.
- Canvas:
customuse.com/workflow/<id>. Open it to tweak any node and re-run only that step.
I opened the mesh's thumbnail render before writing this. It shows the full figure in coat, respirator and boots, with nothing cropped. A render doesn't tell me about topology or weight quality, so check those in your engine.
One thing to know
The rigged GLB has no textures. Customuse's auto-rigger strips them: the rig output has 0 embedded images, against 4 on the textured mesh. In your engine, apply the material from the textured mesh to the rigged one, or I can add a textureBaking step after the rig for 2 credits.
Also, I asked for a 30,000-face budget and the node capped it at 20,000. You got 18,986 triangles, which is fine for an NPC. If you need fewer for LODs, a meshDecimation pass costs 2 credits.
Next steps
- Want a lower-poly LOD? Add
meshDecimationon the textured mesh (2 credits, reuses what we have). - Want a second outfit? Run
nanoBanana2Editon the concept, then re-mesh (~16 + 70 + 33). - Should I save both GLBs to
./customuse/deckhand/in your project?
Connects securely to your tools. The creator never sees your data.
About this skill
Turn your agent into a careful Customuse operator for images, video, 3D meshes, PBR textures, auto-rigging and Roblox-ready assets.
This skill drives the Customuse MCP server, and every number and gotcha in it was measured against the live API: all 16 tools and 46 of 47 node types were run, and about 1,400 credits were spent collecting the evidence.
Why you want it
Customuse's MCP server is easy to call and easy to waste credits with. The expensive traps don't show up in the tool schemas:
- A node that ends in
errornever re-runs.run_nodesreportsstartedand silently does nothing. run_nodesreturnsstatus: "noop"(not an error) for unknown ids, so a naive agent polls forever.- The autorun
budgetCreditsis a soft cap: a budget of 10 spent 44. assetExtractorturnscompleteafter about 5 s while its real output is still generating on a child node.- Preset image nodes rewrite your prompt. Hi3D rejects
faceLimitbelow 100,000. Rigging strips textures.
The skill turns all of that into rules your agent follows.
What it does
- Picks the right node from ordered defaults: text→image, edit, image→textured mesh, mesher comparison, mesh post-processing, video, Roblox.
- Builds multi-node graphs in one transaction with cascade runs, instead of chaining separate paid calls.
- Polls correctly with backoff, watches fan-out children, and checks run receipts before waiting.
- Protects your balance. It never resubmits a paid job, reuses existing nodes before regenerating anything, asks before the first video/3D/cascade charge, and quotes autorun overshoot up front.
- Reports the real cost from
chargedCredits, with fallbacks where the field is missing. - Delivers properly. You get the asset URL plus the canvas link, the exact credit cost and one concrete limitation. It opens renders before describing them and saves files only when you ask.
What's inside
| File | Contents |
|---|---|
SKILL.md | Routing, money rules, poll loop, node selection, delivery (128 lines) |
references/tools.md | All 16 tools: parameters, real response shapes, error → recovery |
references/node-types.md | 47-type catalog snapshot with measured preconditions and a mesher comparison |
references/recipes.md | 12 copy-paste pipelines with measured costs and timings |
references/prompting.md | Prompt patterns for generate / edit / video / 3D-bound images |
README.md | MCP setup for Claude Code, Codex CLI and JSON-config clients |
Measured pipelines (2026-09-20)
| Goal | Chain | Credits | Time |
|---|---|---|---|
| Textured prop | gameAsset → modelTextureGeneration | ~74 | ~4 min |
| Accurate from all sides | imageToMultiview → tripoV31Mesh3d | ~134 | ~3.5 min |
| Rigged character | character → imageOptimize → modelTextureGeneration → autoRigging | 113 | ~6.5 min |
Where it stops
- It needs the Customuse MCP server connected with your own API key. The skill contains no keys and spends nothing by itself; every generation is billed to your Customuse account.
- Prices are a dated baseline. Customuse versions its pricing, so the agent reads the real cost from each run.
- Customuse ends at the asset URL. Local mesh editing (Blender) and engine import (Unity/Unreal/Roblox Studio) are out of scope.
- Interactive editor nodes (clothing fitting, Mesh Edit, Texture Paint) can be created but must be finished in the browser.
Not affiliated with Customuse. MIT licensed, source on GitHub.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
Needs the Customuse MCP server connected with your own API key and credits; every generation is billed by Customuse. Prices in the skill were measured on 2026-09-20 and Customuse versions its pricing, so the agent reports real chargedCredits per run. Stops at the asset URL: no local Blender/ffmpeg editing or engine import. Interactive editor nodes (clothing fitting, Mesh Edit, Texture Paint) must be finished in the browser. The rigged GLB from autoRigging has no textures; the skill hands over the textured mesh alongside it.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 20 days ago
- Free with an Agensi account
- Accounts
- Customuse API key and credits
- Software
Customuse MCP serverRemote MCP
Node.js
Permissions
Allowed Hosts
File Scopes
Network: calls the Customuse MCP server and opens result/preview URLs to check outputs before describing them. Read files: reads a reference image the user points to, to upload it. Write files: saves generated assets only when the user asks, to ./customuse/<workflow>/, never overwriting. The skill ships no scripts and no credentials; the API key stays in the user's MCP client config.