How to Make Game Assets With Claude Code, Cursor and Codex

What do you need to make game assets with a coding agent?

A coding agent already reads your project, writes code and runs commands. To make art it needs a tool that generates art. That is what an asset MCP server adds. If you also give it your engine's MCP server, it can place what it made in a scene and wire it up.

How do you connect Claude Code, Cursor or Codex?

1. 1

   Add the asset server

   One command or one config entry, below. It is a remote server, so nothing is installed and there is no API key.

2. 2

   Add your engine's server (optional)

   Unity, Unreal, Godot, Roblox Studio and Blender all have MCP servers that let the agent place assets and write engine code.

3. 3

   Sign in once

   The first time the agent uses 3D AI Studio, a browser window opens. Sign in and click Authorize. That is the whole setup.

claude mcp add --transport http --scope user 3daistudio https://mcp.3daistudio.com/mcp

codex mcp add 3daistudio --url https://mcp.3daistudio.com/mcp

{
  "mcpServers": {
    "3daistudio": {
      "url": "https://mcp.3daistudio.com/mcp"
    }
  }
}

For the engine side, see our guides for Unity, Unreal, Godot, Roblox and Blender. If you build for the web with Three.js or Babylon.js, you do not need an engine server at all: the agent writes the loader code itself.

What does a full asset session look like?

Here is a realistic session for a small stylized Three.js game, from an empty assets folder to working models with sound. The tool names are the real ones the 3D AI Studio server exposes.

> read docs/art.md. we need the first level: a well, 3 crates, a lantern, a frog NPC. start with a style reference
● 3daistudio · create_project  ("Moss Valley")
● 3daistudio · generate_image_nano_2_1  (style sheet: well, crate, lantern, frog, chunky low poly)
Saved assets/ref/style.png. Does this look right before I make 3D models from it?
> yes, go
● 3daistudio · edit_image_nano_2_1 × 4  (one front view per object, same style as style.png)
● 3daistudio · generate_p2 × 3  (well, crate, lantern · from their front views · quad mesh)
● 3daistudio · generate_prism_3_1  (frog NPC · from its front view)
  └ 4 models ready · assigned to project Moss Valley
● 3daistudio · low_poly_model  (frog, target 12,000 triangles)
● 3daistudio · generate_sound_effect × 2  (wooden crate break, frog croak)
Downloaded 4 GLBs to assets/models/ and 2 sounds to assets/sfx/.
Added src/level1.ts: places the well and lantern, scatters the crates, and plays crate_break.mp3 on hit.
npm run dev is running at localhost:5173. The frog idles by the well.

Three things in that session do most of the work:

• The style reference came first. Every model was generated from the same sheet, so the crate and the frog look like they belong in one game.
• The agent asked before spending. Approving the reference image is cheap; regenerating four models is not. Tell your agent to check with you at that point.
• Budgets were in a file. The agent read docs/art.md, so it knew the triangle targets and folders without being told each time.

## Art direction (read before generating any asset)
- Style: chunky stylized low poly, bright saturated colours, soft shading
- Style reference: assets/ref/style.png (pass it as a reference image)
- 3D project in 3D AI Studio: "Moss Valley"
- Props: P2, under 3,000 triangles, export GLB to assets/models/props/
- Characters: Prism 3.1 from a front-view reference, under 15,000 triangles
- Textures: 1K unless I say otherwise
- Sounds: short, dry, no music, save to assets/sfx/

Which AI model should make which asset?

You can let the agent decide, and it usually picks well. When you want control, this is the breakdown we use:

Below are real results: concept image in, game asset out. Drag a model around, or switch to clay to judge the mesh without its texture.

Choose a concept

How do you keep AI game assets in one consistent style?

This is where most AI-made games fall down: every asset is fine and none of them match. A few habits fix it.

• Make one style sheet image with several objects on it and get it right before any 3D. Reference it in every later request.
• Use one 3D model per asset type. Mixing models for props gives you mixed topology and texture styles.
• Write the rules down (style words, budgets, folders) in the file your agent reads at the start of each session.
• Keep a 3D AI Studio project per game. The agent can list what is already in it before making a near-duplicate.
• Generate in batches of the same kind: all the crates and barrels in one go, all the trees in another.

How do you get the assets into each engine?

Which MCP server is best for game assets?

Several companies now offer asset servers for coding agents. We make one of them, so read this with that in mind, but the facts below come from each project's own documentation.

Where 3D AI Studio is the better pick

Breadth and setup. One remote URL gives you several 3D models, including Meshy 7.1 itself, plus images, materials and audio, and it works the same in Claude Code, Cursor, Codex and the chat apps. There is no key to keep out of your repo, and everything lands in one dashboard.

Where others are ahead

• Rigging and animation inside the agent: Meshy's MCP server can rig humanoid characters and apply preset animations. Our connector does not do that yet.
• Editable part hierarchies: Thrixel builds models out of named parts, which is useful when a door or a wheel has to move on its own.
• 2D sprite games: gamedev.sh focuses on sprites and ships a catalog of ready icons.

Frequently asked questions