MCP for game development: give Claude Code or Cursor a real 3D asset pipeline

Coding agents were already able to write the gameplay code. What they could not do was produce the things the code needs: a character, its sword, the arena floor texture, the hit VFX. They would write // TODO: add character model here and move on. The Model Context Protocol (MCP) closes that gap.

What MCP is, in one paragraph

MCP is an open protocol from Anthropic, adopted by Claude Code, Cursor, Windsurf, VS Code and others, that lets an AI agent discover and call tools exposed by a server. Each tool has a name, a typed input schema and a description. The agent picks a tool, fills the inputs, gets a structured result, and decides what to do next. It is function calling with a standard transport, which is what makes one server usable from every client.

For a game developer, the practical consequence is that "generate a low-poly orc with a cleaver, animate it and put it in Assets/Characters/" becomes a sequence the agent can execute, check and fix, rather than a request it can only answer with text.

What a game-asset server should look like

The first instinct is to expose one tool, make_character(prompt). It is the wrong shape. When the result is bad, the agent has no way to know which part failed and no way to fix only that part.

The shape that works is a chain of small tools, each returning something the agent can inspect:

1. gripforge_generate_character produces a concept image and a mesh, and reports whether the concept passed the riggability check.
2. gripforge_rest_pose straightens the mesh; gripforge_hand_rig builds articulated fingers when the character will hold something.
3. gripforge_generate_weapon makes the weapon as a separate asset.
4. gripforge_attach places the weapon in the hand and returns the socket transform.
5. gripforge_animate adds idle, walk, run, attack, hit and death clips.
6. gripforge_library_pull writes the GLB into the project.

With this shape, a rejected concept costs one retry of step 1, not a whole regeneration. It also lets the agent do things the tool author never scripted, such as generating three variants and keeping the one whose hitbox (gripforge_hitbox) fits the level.

Beyond characters, the same server exposes terrain and map generation, tileable textures, VFX, HUD elements, and complete game kits (a playable FPS, brawler or racing template wired to the generated assets). The agent composes them.

Connecting GripForge to Claude Code

One command, with the API key from your account page:

claude mcp add --transport http gripforge https://gripforge.ai/mcp \
  --header "x-api-key: gf_your_key" -s local

Then, in the project:

Generate a low-poly dwarf blacksmith with empty hands, around 8k triangles,
generate a two-handed hammer, attach it, add idle/walk/attack clips,
and pull the GLB into Assets/Characters/Blacksmith/.

Claude Code will run the chain, show each result, and ask before anything destructive. The full tool list is in the MCP documentation.

Cursor, Windsurf and other clients

Every MCP client that supports HTTP transport uses the same endpoint. In Cursor, add the server in the MCP settings with the URL https://gripforge.ai/mcp and the x-api-key header. The tools appear in the agent's tool list under the gripforge_ prefix.

Unity and Godot in the loop

Pulling a GLB into a folder is enough for Godot, which imports it on the next focus. For Unity, the editor bridge (a small package you install from the docs) lets the agent trigger an import and place the prefab in a scene, so the loop closes without alt-tabbing. Unreal reads the GLB through its glTF importer.

Scope and safety

An MCP server acts with the key it is given. GripForge keys are scoped to a workspace: the agent can generate, read and delete assets there, and cannot see other workspaces, billing or account settings. Tools that delete or stop something are flagged as destructive, so clients that support confirmation will ask first. The server receives the prompt and parameters of each call, and does not read the agent's conversation, memory, or files it was not given.

FAQ

What is MCP in game development?

MCP, the Model Context Protocol, is an open standard that lets AI coding agents such as Claude Code or Cursor call external tools. In game development it gives an agent the ability to generate, rig, animate and export 3D assets, textures, VFX and levels, and to place them in the project, instead of only writing the code that uses them.

Does GripForge work with Cursor?

Yes. Cursor supports MCP servers over HTTP. Add https://gripforge.ai/mcp with an x-api-key header in Cursor's MCP settings, and the GripForge tools become available to the agent.

Can an MCP server generate Unity assets directly?

It generates engine-ready GLB files that Unity imports natively, and GripForge's Unity editor bridge lets the agent trigger the import and place the prefab in a scene. The same GLB works in Unreal Engine and Godot.

Is it safe to give an AI agent an API key?

Use a key scoped to one workspace. The agent can then only create, read and delete assets inside that workspace. Revoking the key in your account page cuts its access immediately.