Blender MCP: Who Won? Claude Opus 4.8 vs Codex GPT 5.5 AI Test and Tutorial

Añadido: 2026-06-01

[00:00:00]Who can create the best blender scenes?

[00:00:01]GPT 5.5 or Claude Opus 4.8? In this video, we will have them start by creating a Pokéball, then we'll increase the difficulty by creating the Starship rocket from SpaceX, and last but not least, the final boss, the dragon. To get this to work, we first need to connect the Blender MCP. First, you need to run brew install UV in your terminal.

[00:00:20]After you do that, you go to the Blender MCP GitHub repo and you download the add-on file. Then you open up Blender and click on edit. Then you have to click on preferences and after that, you have to click on add-ons. Click on install from disk, select the add-on file, and enable it. Then press N in the 3D viewport to open the side panel. Find Blender MCP and hit start MCP server.

[00:00:39]Once you do that, Blender is ready for your AI agent to connect. For Claude code, you're working in the desktop app.

[00:00:45]Go to settings, then developer, then edit config, and you'll see the Claude desktop config JSON file. You add a Blender entry under MCP servers with the command set to UVX and the argument Blender MCP. Save that, restart Claude, the Blender tools are loaded and ready.

[00:00:59]For Codex, you navigate to settings, then click on the MCP servers. Click on add server, and this is what your configuration should look like. Click on save and reset the Codex app. Once it's configured, Codex picks up the Blender tools automatically when you start a session. Round one, the Pokéball. A simple shape, but every detail matters.

[00:01:17]The proportions, the gloss, and that crisp red and white split. Claude running Opus 4.8 goes first. Watch Opus work. It blocks out the sphere, separates the shells, then adds the black band and the center button. Start to finish, this build took about 7 and 1/2 minutes. And here is Opus's Pokéball. The proportions are spot on, the button and chrome ring are clean, and the black band sits right where it should. Next to the reference, it is a strong match. The red skews a little coral and reads very glossy, almost candy-like, where the original is a flatter, brighter red. Opus actually flagged that itself, noting the red looked desaturated and pushing for a punchier tone. Overall, a faithful and polished first attempt. Now it is GPT 5.5's turn running through Codex. Same reference image, same task. Let's see how it stacks up. Codex takes a more deliberate path, building separate beveled shells, a recessed satin band, even procedural scuffs, and a full turntable animation. This one took about 12 and 1/2 minutes, noticeably slower than Opus. And the payoff is a clean, polished Pokéball sitting on a display plinth. The red is more muted and realistic, and the button has a subtle cyan glow. Against the reference, Codex nails the proportions, and that matte finish actually reads closer to the real toy. Two strong Pokéballs. Opus glossier and punchier, Codex more refined and restrained. The Pokéball is in the books. Time to raise the stakes with the Starship. Round two cranks up the difficulty. SpaceX's Starship on the launch tower. This one is all about scale, the lattice tower, the booster, and the venting plumes. Opus takes the first shot. Opus blocks out the tower and stacks the booster, but watch the chat. Renders timeout, and the connection keeps dropping. It fights through to a full model, though lighting trouble leaves its final shot dark. All in, this build dragged on to nearly 26 minutes. Here is what Opus put together before it gave out. The full tower and rocket are roughed in, but it errored before the render could resolve, so the whole shot stays dark and murky. By the way, this video was edited using Video Edit MCP, which is the only video editing platform built for the use of AI agents. The setup is simple. You just go to videoeditmcp.com, click on this curl command, and paste it into your terminal. Once it's done installing, the videoeditmcp app will open. Click your email, and click on connect AI agent. Then click connect.

[00:03:25]The connection will show it's ready.

[00:03:26]Once you open the AI agent, the app will finalize the connection. And that's it.

[00:03:30]Your AI agent now has full video editing capabilities. Now, Codex steps up to the Starship. Same reference, same brutal complexity. Codex is methodical here.

[00:03:39]The tower, the booster, the venting, even the Gateway to Mars text on the pad. And it just runs clean, finishing in about 10 minutes flat. Still, look at this result next to the reference. The proportions, the launch tower, the smoke, it's genuinely impressive. On Starship, Codex clearly pulls ahead.

[00:03:54]Side-by-side, the silhouette and the venting really sell the shot. It's not flawless, the tower is simplified, but it captures the scene far better than Opus Manage. For the dragon, I went ahead and switched to Claude Code in the terminal. If you want to connect your Blender MCP to the Claude Code running on the terminal, you actually have to configure it separately from the desktop app. I've created this super terminal command to make it easier to connect it to Blender. I'll link it down below if you need it. You just copy and paste this entire command in the terminal, run Claude, and you're connected. Now, let's run this bad boy on the new Ultra Code.

[00:04:26]Two builds down, one to go, and the dragon is the toughest test yet. Round three, the final boss. A fully detailed dragon, wings, horns, scales, and glowing accents, the works. And with Ultra Code driving Claude, I already know this is going to be good. Opus goes huge here, sculpting the body, extruding the neck and tail, then building out those massive membrane wings. And if you are enjoying this showdown, take a second to like and subscribe. It really does help. And this is Opus's dragon.

[00:04:52]The glowing blue horns and spine accents are gorgeous, the wings are detailed, and the pose has real character. Against the reference, Opus captures the vibe beautifully. The icy glow, the membrane wings, the armored body. It is a little stylized and stockier than the sleek original, but seriously impressive. The catch? This was by far the slowest build of the day, clocking in at a massive 43 minutes. Opus even set up a turntable and studio lighting to show the dragon off from every angle. For the most ambitious build of the day, it's a fitting finale. Opus set an incredibly high bar, now all the pressure is on Codex. It works fast, blocking out the body, the long neck, the tail, and a big bat wing, all in about 12 and 1/2 minutes, less than a third of Opus's time. Here is the Codex dragon. I have to admit, I don't know what Codex was going for here. Put the images side-by-side, and I guess if you squint hard enough, they kind of look the same.

[00:05:41]It's not good, but it's not horrible.

[00:05:43]So, who do you guys think did better?

[00:05:45]Comment your answer down below, and don't forget to like and subscribe.