Blender and AI: project policy, connectors and asset rights

When a client asks whether Blender uses AI, establish what they mean: built-in features, an add-on connected to a model or generated content imported into a scene.

Each case raises different questions about behaviour, permissions and rights.

What the Blender Foundation announced

In May 2026, the Foundation said it would receive Anthropic's contribution as a one-off donation instead of Development Fund membership. It did not announce returning the money.

The statement said no generative AI functionality was then integrated or planned for integration into Blender. This is a dated product position, not a promise that policy can never change or that every add-on follows it.

What connecting an agent involves

Blender Lab presents an experimental MCP server connecting external systems to Blender. Before using any connector, check its available operations and execution permissions.

Generated scripts can alter or delete data within their reach. Test on copies, restrict sensitive information and inspect results before including them in a delivery.

The practical question is what the connector can do in your installation. Local connectivity does not replace reviewing the commands it receives.

CC0 still needs a provenance check

CC0 facilitates use of a work, including commercial use. Creative Commons explains that it does not affect potentially relevant trademark, patent, privacy or publicity rights, nor independently certify provenance.

Avoid describing a CC0 asset as carrying no possible rights issues. Keep its source and check that the contributor can offer it under those terms.

The same principle applies to generated meshes: Blender opening a file says nothing about the originating tool's licence.

Three separate studio decisions

This makes it possible to explain what contributed to a production without attributing an external provider's decisions to Blender.

To plan an integration, tell us which task you want to automate and which files it needs.