Godot vs Unity vs Blender MCP (2026)
Three different jobs in one MCP-shaped neighbourhood. Godot MCP wraps the open-source Godot 4 engine for GDScript and scene scaffolding. Unity MCP wraps Unity for scene management, C# scripts, and console builds. Blender MCP wraps Blender for Python-driven 3D asset creation. You’ll likely use two of them together — the engine for the game, and Blender for the art that goes inside.
On this page · 10 sections▾
TL;DR + decision tree
- Want to ship an indie 2D or 3D game with zero royalties and full source access? Godot MCP. MIT-licensed engine, GDScript is the most-trafficked gaming skill on this directory, scenes scaffold cleanly from a single prompt.
- Targeting console + mobile + PC at production scale, with hireable team members and a real asset store? Unity MCP. The industry-standard runtime; the CoplayDev/unity-mcp community project is the most-active engine MCP today.
- Need custom 3D models and don’t have an artist? Blender MCP. Not a game engine — a 3D content tool. Pair it with Godot or Unity for the game runtime; export GLTF/FBX in between.
- Building a pixel-art 2D platformer? Godot is leaner. Building a cinematic 3D action game? Unity (or Unreal, when its MCP lands). Building game art only, no runtime? Blender alone.
The honest framing: most teams will compose two of these. Godot or Unity for the game, Blender for the art. The rest of this post covers each individually — install, what it does best, a runnable recipe, and when to skip it.
What game engine MCPs do
A game-engine MCP server exposes the engine’s editor APIs as MCP tools an agent can call. Instead of hand-writing GDScript or C#, the agent invokes things like “create scene”, “attach script”, “configure node” via JSON-RPC, and the engine writes the resulting project files. Blender’s MCP is the same idea against Blender’s bpy Python API — the agent calls mesh-creation, material, and export operators instead of clicking through the UI.
The differences come down to four axes:
- What the tool produces. Godot MCP produces
.tscn(scene) and.gd(script) files. Unity MCP produces.unityscenes and.csscripts. Blender MCP produces.blendfiles plus exported.gltf/.fbx/.objmeshes — input for the engines. - Scripting language. Godot speaks GDScript (Python-like) and C#. Unity speaks C# only. Blender speaks Python via
bpy. The scripting surface drives how much agent training data the model can lean on. - Runtime vs content. Godot and Unity ship a runtime — your game runs on the engine. Blender does not. You can render cutscenes from Blender, but a player’s device runs Godot or Unity, never Blender.
- Skill pairing. Each MCP composes with a SKILL.md cognitive guide on this directory: /skills/godot shifts the agent toward Godot 4 idioms; the same pattern applies for Unity and Blender skills as the catalog fills out.
If you’re new to the protocol underneath, our What is MCP primer covers the JSON-RPC wire format these servers run on. The rest of this post assumes you know that already.
Side-by-side matrix
Every cell is sourced from each tool’s repo, README, or package metadata. Live values checked 2026-05-08 against MCP.Directory’s indexed catalog at /servers.
| Field | Godot | Unity | Blender |
|---|---|---|---|
| Type | Open-source 2D + 3D game engine | Commercial 2D + 3D game engine | 3D content creation tool (not engine) |
| License | MIT | Proprietary (Unity License) | GNU GPLv3 |
| Scripting | GDScript + C# | C# | Python (via MCP) |
| 2D support | ✓ first-class | ✓ via Sprite Renderer | — |
| 3D support | ✓ | ✓ | ✓ first-class |
| Mobile builds | ✓ | ✓ (most mature) | — (export only) |
| MCP server slug | /servers/godot | /servers/unity | /servers/blender |
| Best for | Indie 2D/3D, small teams | Production 3D, console ship | Asset creation pipeline |
Three things to read out of this matrix. Godot is the only fully MIT-licensed runtime — full source access matters when an engine bug bites a shipping game. Unity is the only one with deep console support (PlayStation, Xbox, Switch), which is the moat for studios shipping outside mobile + desktop. Blender is fundamentally a different shape — pair it with one of the other two; never pick “Blender vs Unity” as if they did the same job.
Godot — install + recipe
What it does best
Godot is the only fully open-source engine of the three. The godot skill on this directory is the highest-trafficked gaming skill — “godot skills” alone lands 381 monthly impressions at 16% CTR. The MCP server pairs the engine with scene scaffolding so Claude can write GDScript, build.tscn files, and configure project settings. Indie game dev’s strongest path; large enough community that GDScript fluency is well-represented in the model’s training data.
Pick this if you...
- Ship a 2D or 3D game on a tight budget — Godot is MIT-licensed, no royalties.
- Want to ship to mobile + web + desktop from one engine.
- Prefer GDScript (Python-like) but want C# as an option for performance-critical code.
- Need to read or modify the engine source if a bug bites your project.
Recipe: build a top-down RPG starter
Drop this into Claude Code with the Godot MCP installed:
Build a top-down 2D RPG starter kit in Godot 4. Include a Player
scene with grid-based movement (snap-to-tile), a Dialog scene that
reads from a JSON questline, an Inventory scene with drag-and-drop,
and a Save/Load system using Godot's built-in JSON saver. Output
every .tscn and .gd file.The agent will scaffold the directory structure, write Player.gd with a tile-based move() function, generate Dialog.gd that parses a questline.json, build an Inventory.tscn with InventorySlot drag handlers, and write SaveSystem.gd using Godot’s FileAccess.open() with JSON serialization. Without the godot skill, agents tend to write Unity-shaped GDScript with class-based inheritance everywhere — the skill nudges them back to Godot 4 idioms.
Skip it if...
You’re shipping a AAA-quality 3D game — Unity and Unreal still win on cinematic tooling. Also skip if your team already has Unity or Unreal expertise; switching costs outweigh Godot’s licensing wins for established studios.
Unity — install + recipe
What it does best
Unity is the industry-standard commercial engine. Its MCP server exposes scene management, asset import, and C# scripting. Larger asset store than Godot; mature mobile build pipeline; team hireability is the strongest of the three — finding production Unity devs is far easier than Godot devs. TheCoplayDev/unity-mcp project is the most-active community MCP; Unity itself is closed-source but broadly stable.
Pick this if you...
- Target mobile + console + PC at production scale.
- Need an asset store with thousands of paid + free assets out of the box.
- Team is already on Unity and switching costs are real.
- Ship to PlayStation, Xbox, or Switch (Unity’s console support is the most mature of the three).
Recipe: generate a third-person controller
Drop this into your agent with Unity MCP installed:
In a Unity 6 URP project, generate a third-person controller with
Cinemachine camera, root motion animation, double-jump + dash, and
a simple state machine controlling Idle/Walk/Run/Jump/Dash. Include
the C# scripts and a description of the Animator state graph.The agent generates PlayerController.cs (CharacterController + Cinemachine virtual camera follow), PlayerStateMachine.cs (enum-based state with transitions), and a written description of the Animator: Idle → Walk (speed > 0.1) → Run (speed > 5) → Jump (jumpPressed) → Dash (dashPressed). Output is C# scripts the agent can drop into Assets/Scripts/.
Skip it if...
Budget is zero — Unity’s pricing tier shifted in 2024 and exact terms vary; verify the current Personal/Plus/Pro split before committing. Also skip for a 2D pixel-art platformer (Godot is leaner here, with first-class 2D nodes instead of Unity’s Sprite Renderer adapter pattern).
Blender — install + recipe
What it does best
Blender is not a game engine — it’s a 3D content tool. The Blender MCP server lets Claude drive Blender via Python: model meshes, set up materials, render scenes, export to GLTF/FBX for downstream engines. The blender skill on this directory pairs with the MCP for asset-pipeline work. Best when the game needs custom 3D assets and the team doesn’t have a dedicated artist; the connector guide at /blog/claude-blender-connector-guide is one of the most-trafficked deep-dives on the directory.
Pick this if you...
- Need custom 3D models without an artist on the team.
- Want to drive Blender from Claude Code as part of an automated asset pipeline.
- Need to export to Unity / Godot / Unreal in standard formats (GLTF, FBX, OBJ).
- Render cinematics or pre-rendered backgrounds for 2D game cutscenes.
Recipe: generate a stylized low-poly tree
Drop this into your agent with the Blender MCP installed:
Use the Blender MCP to (1) generate a low-poly tree mesh with 5
leaf clusters around a central trunk, (2) apply a 2-color
toon-shaded material with the trunk in brown and leaves in green,
(3) export to GLTF with embedded textures, (4) save the .blend file
as tree.blend. Print the Python script Claude executed.The MCP exposes Blender’s bpy API to Claude. The agent calls bpy.ops.mesh.primitive_cylinder_add() for the trunk, bpy.ops.mesh.primitive_ico_sphere_add() × 5 for leaf clusters, applies a Principled BSDF with a toon-shading workaround, and uses bpy.ops.export_scene.gltf(). Final output is the GLTF + .blend file ready for Unity/Godot import.
Skip it if...
You actually need a game runtime — Blender doesn’t ship one (pair it with Godot or Unity for that). Also skip if the team already has 3D artists with their own pipeline; the MCP is for filling a missing-artist gap, not for replacing artist judgment.
Common pitfalls (regardless of which one you pick)
Treating Blender as a Unity/Godot replacement
Blender renders, models, and animates — it does not run a shipped game on a player’s device. Pair it with an engine; never frame the choice as “Blender or Unity.”
Stacking Godot + Unity in the same workspace
Both engines expose dozens of overlapping editor tools. With both MCPs loaded, agents pick the wrong server on roughly half of ambiguous prompts. Pick one engine per project; run separate MCP configs per workspace if you genuinely need both.
Skipping the SKILL.md pairing
The MCP server gives the agent tool calls; the skill at /skills/godot gives it cognitive guardrails — “use FileAccess not File”, “don’t reach for class inheritance in GDScript”. Without the skill, generated GDScript reads like Unity C# in a Python costume.
Asking Unity MCP to do art
Unity MCP can scaffold scenes and write C#, but it has no opinion on how a model looks. Generate placeholder assets in Blender (or pull free assets off Unity’s asset store), then pipe them into Unity. Agents that try to “design” inside Unity end up describing primitives.
Forgetting to verify Unity’s current pricing
Unity’s tiered pricing changed in 2024. The Personal tier is still free under a revenue threshold, but the threshold and Plus/Pro pricing have shifted. Confirm the current numbers on unity.com/pricing before committing — don’t trust last-year blog posts.
Community signal
The three MCPs occupy distinct niches in community discussion. Godot’s MCP and skill ride a steady wave of indie-dev enthusiasm — “ship without royalties” is the persistent theme, and the godot skill’s real-world search demand (381 monthly impressions on “godot skills” alone, 16% CTR) reflects that. Unity’s MCP discussion centers on the CoplayDev/unity-mcp project; most threads are about scene-management workflows and C# script generation, with the occasional thread about pricing-tier confusion. Blender’s MCP attracts a different audience — solo devs and small teams using Claude as a stand-in artist, plus a long tail of tutorial creators showing “Claude built me an asset” demos.
We’re deliberately not posting verbatim Reddit/HN quotes here because the “MCP is great” cluster runs hot enough that we’d rather under-claim than misattribute. Read each project’s GitHub issues for the real complaints, the indie-dev subreddits for sentiment, and the YouTube channels of Brackeys-tier educators for proof-of-concept walkthroughs. The cookbook posts at /blog/claude-godot-skill-guide and /blog/claude-blender-connector-guide cover the per-tool day-one workflows in more depth.
Want a deeper Godot walkthrough?
The Claude Godot skill cookbook covers ten use cases for the godot skill in detail — grid movement, dialog systems, save files, and more.
Setting up Blender + Claude end-to-end?
The Claude Blender connector guide walks through the bpy bridge install, the first asset round-trip, and the GLTF export pipeline.
Frequently asked questions
What's the difference between Godot, Unity, and Blender MCP?
Godot and Unity are game engines (the runtime your game ships on). Blender is a 3D content tool (the meshes and animations you import into a runtime). Don't pick "Blender vs Unity" — pick "Blender for assets + Unity (or Godot) for the game." Godot's MCP wraps the engine for scene scaffolding and GDScript. Unity's MCP wraps Unity for scene management and C# scripting. Blender's MCP wraps Blender for Python-driven mesh and material work.
Is Blender a game engine?
No. Blender is a 3D modeling, animation, and rendering tool. It does not ship a game runtime — there's no Blender executable that runs your game on a player's device. Use Blender to create assets (.gltf, .fbx, .blend files); use Godot or Unity to package those assets into a shippable game.
Godot skill vs Godot MCP server — what's the difference?
The skill (in data/skills.json at /skills/godot) is a SKILL.md cognitive guide — it shifts the agent's writing toward GDScript conventions and Godot 4 patterns. The MCP server (at /servers/godot) is a tool surface — it lets the agent actually create and edit Godot project files via API calls. They compose: install both for the strongest Godot workflow.
Can Unity MCP build a real shippable game?
Yes — the MCP gives Claude access to Unity's Editor APIs, so the agent can scaffold scenes, write C# scripts, configure build settings, and trigger builds. The bottleneck is asset creation (which is where Blender MCP fits in) and game design (which is where the human stays). For a pure-code multiplayer game with placeholder art, Unity MCP can carry most of the load.
What about Unreal MCP?
As of May 2026, Unreal Engine doesn't have a first-party MCP server in this directory. The community is working on one. If you ship Unreal today, your fallback is to expose Unreal's Python API as a custom MCP wrapper, or use Unreal's MCP via the Code Plugins marketplace if a community option exists. We track new servers — check /servers/category/coding for Unreal updates.
Can I use Godot's skill with Cursor or Codex?
Yes — the godot skill follows Anthropic's SKILL.md spec, which Cursor reads natively via its plugin system, and Codex CLI supports via an adapter. Activation triggers (when the agent decides to follow the skill) are most reliable in Claude Code; in Cursor or Codex you may need to explicitly say "use the godot skill" in your prompt.
Do these engine MCPs cost money?
The MCP servers themselves are free + open source. The underlying tools have different cost models: Godot is free with no royalties; Unity has a Personal tier (free below revenue threshold) plus Plus/Pro paid tiers; Blender is free + GPLv3. Verify Unity's current pricing before committing — it changed in 2024.
Best for indie game dev: Godot or Unity?
Godot if you value zero royalties, full source access, and 2D-first tooling. Unity if you value the asset store, hireable Unity devs, and proven console-ship workflows. The honest tiebreaker: try Godot first for prototyping (faster to start, no licensing friction); switch to Unity later only if you hit a feature ceiling that Godot can't clear.
Sources
Godot
- godotengine.org — engine homepage, MIT license, Godot 4 release notes
- docs.godotengine.org — GDScript reference, scene/node model, FileAccess API
- /skills/godot — the godot SKILL.md as published in this directory
Unity
- unity.com — engine homepage; Personal/Plus/Pro pricing reference
- github.com/CoplayDev/unity-mcp — most-active community Unity MCP server
- docs.unity3d.com — Editor APIs, Cinemachine, URP, Animator state docs
Blender
- blender.org — project homepage, GPLv3 license
- docs.blender.org/api — bpy Python API reference (mesh ops, materials, export)
- /blog/claude-blender-connector-guide — connector setup walkthrough on this directory
Internal links
- /servers/godot
- /servers/unity
- /servers/blender
- /skills/godot
- /blog/claude-godot-skill-guide — godot cookbook
- /blog/claude-blender-connector-guide — Blender connector guide
- /blog/best-language-skills-for-claude-code-2026 — sibling D-1 (just shipped)
- /blog/what-is-mcp — protocol primer
- /best-mcp-servers — curated roundup
Related comparisons
- Best Language Skills for Claude Code (2026) — sibling D-1 covering the language-skill side of the agentic toolbox.
- Drawio vs Excalidraw vs Mermaid vs Penpot Skills (2026) — same matrix format, applied to diagram tooling.
- Claude skills vs MCP vs subagents vs CLI (2026) — broader framing for when to reach for a skill, an MCP, or both.