Use MCP for an AI-assisted 3D workflow

MCP connects an AI application to tools it can use. In Bake3D, those tools can start a generation, inspect a project, describe animation and export the result. The assistant can coordinate the steps while you remain in the conversation about what you want to create.

Connect the service

Create a Bake3D API key in your account. Keys require a Pro or Studio plan. Configure an MCP-compatible client with the Streamable HTTP endpoint:

https://bake3d.ai/api/v1/mcp

The client sends the key in an Authorization: Bearer … header. Use the client’s credential configuration rather than pasting the key into an ordinary prompt. The integration reference includes a concrete configuration example and supported protocol versions.

Give the assistant a complete task

Describe the object, motion and destination. For example:

Generate a four-legged creature from this image. When the rig is ready, give it a slow head turn and relaxed tail wag. Export a four-second loop in place, then import it into my Blender test scene.

A good sequence is to start the generation, keep the returned project and job IDs, poll the job until it finishes, inspect the project, create the motion, then request an export. Ask the assistant to inspect failures instead of repeatedly submitting the same generation.

Generation with a rig uses 35 credits, and described motion uses 5. Reading progress and exporting an existing result do not add a generation charge. Check your balance before starting several jobs.

Understand where editor control comes from

Bake3D MCP creates and returns the asset. Placing it into an open Blender, Unity or Unreal scene also requires a compatible editor integration or bridge with access to that scene. The MCP connection alone does not grant desktop control.

The Bake3D Blender add-on and Unity editor tool provide supported entry points described in the editor reference. Other clients can download the GLB and invoke their editor’s import workflow. Validate the resulting skeleton, materials and animation before replacing a production asset.

Keep the workflow reviewable

Use project IDs when returning to an existing character. Keep a useful rig before trying another version. Download signed export links while they are valid; request a new link if one expires. Give editor instructions that identify the destination scene and whether root travel should be retained.

The MCP introduction explains the protocol’s role. For Bake3D’s exact request and response fields, use the API reference.