Glade Mcp

Most AI coding assistants see a file. GladeKit sees a game. The distinction matters because game bugs live in the space between things — a script that's fine in isolation but breaks because the prefab referencing it lost a component, or a physics collider sized wrong for a scene that gets regenerated at runtime. GladeKit's docs are explicit about the problem it solves: existing AI tools don't integrate with Unity or Godot, so you spend your prompt describing scene context the model can't see, and they can't act in the Editor at all. GladeKit reads your scene hierarchy, scripts, selection, and settings, and then writes scripts, creates GameObjects, components, prefabs, materials, UI, and physics. The way it fits into a real workflow is what makes it useful rather than novel. If you already live in Cursor or Claude Code, you don't have to abandon that — the MCP server is open-source and connects those clients to Unity or Godot with 300+ granular tools, an engine-aware system prompt, game design document project context, script semantic search, and skill calibration. That means your existing AI workflow gets the project context it was missing, instead of you maintaining two separate tools with different mental models. Control over context is handled better than most. You choose how much of the project gets sent, and you switch freely between Agent, Debug, and Ask modes — which maps onto how development actually alternates between doing, fixing, and thinking. The asset pack search is a practical addition: free, commercial-safe packs searched by genre, style, or format and imported straight in, which removes a licensing research chore most indies handle badly. The Meshy AI integration is genuinely time-saving if you model — you connect your own Meshy API key and generate game-ready models inside the app — but it's Unity-only at launch, so Godot developers wait. Where it's weaker: the free Indie tier's 50 interactions disappear fast on a real project, so the realistic entry price is $15/mo Pro. Engine coverage is Unity and Godot only — Unreal is still roadmap, and if your team ships Unreal, this isn't the tool. It's also desktop-first: there's no equivalent web-only path, so the app is part of the deal. Evaluation is your job, not the tool's — GladeKit writes into your scene, and you should review changes and commit often, which the docs themselves support via their 'Reviewing Changes' guide. The honest summary: for solo indies and small Unity or Godot teams, GladeKit removes the most tedious part of the loop — describing your project to an AI that can't see it. That's a real gain, not a demo trick.