# AI Game Developer

> AI Game Developer is an MCP (Model Context Protocol) platform that lets AI agents inspect and drive real game engines. You install one editor plugin — Unity-MCP, Unreal-MCP, or Godot-MCP — into your project, and it exposes that engine's editor operations as AI Tools. Any MCP-compatible AI client (Claude, Cursor, GitHub Copilot, Gemini, Codex, Windsurf, Cline) can then create scenes, spawn objects, edit and compile scripts, manage assets, and capture screenshots directly inside your live editor. The plugin is the bridge, not an AI model: you bring the AI agent, AI Game Developer gives it hands inside the engine. It is free and open source, and connects through the hosted ai-game.dev cloud backend or a self-hosted GameDev-MCP-Server.

## Start here

- [Home](https://ai-game.dev/): What AI Game Developer is and which engines it supports.
- [Download](https://ai-game.dev/download): Get the plugin / installer.
- [Quickstart](https://ai-game.dev/docs/quickstart): Install, authorize, and run your first AI request in minutes.
- [MCP endpoint info](https://ai-game.dev/mcp-endpoint-info): Per-client MCP config (Cloud vs Custom / self-hosted).

## Engines

- [Unity](https://ai-game.dev/engines/unity): Unity-MCP — 190 tools across 27 families (76 core + 114 from extensions); works in Editor and Runtime. Unity 2022.3+.
- [Unreal Engine](https://ai-game.dev/engines/unreal): Unreal-MCP — 62 tools across 8 families incl. Blueprint and C++ authoring/compile. UE 5.5+ (tested on 5.7).
- [Godot](https://ai-game.dev/engines/godot): Godot-MCP — 36 tools across 10 families, C# and GDScript. Godot 4.3–4.5 (mono).

## Best practices

How to make simple, effective AI requests and discover what the agent can do — per engine.

- [Best practices hub](https://ai-game.dev/docs/best-practices): Principles, the anatomy of a good request, and capability-discovery recipes (engine-agnostic).
- [Unity best practices](https://ai-game.dev/docs/best-practices/unity): Example prompts, tool-family map, first-request recipe, and pitfalls for Unity-MCP.
- [Unreal best practices](https://ai-game.dev/docs/best-practices/unreal): Example prompts (incl. Blueprint/C++ compile loop), family map, and pitfalls for Unreal-MCP.
- [Godot best practices](https://ai-game.dev/docs/best-practices/godot): Example prompts (C# + GDScript), family map, and pitfalls for Godot-MCP.

## Docs

- [Tools registry](https://ai-game.dev/docs/tools): Every built-in MCP tool, grouped by engine and family.
- [Extensions catalog](https://ai-game.dev/docs/extensions): Add-on packages that add whole tool families to a base engine plugin, organized by engine. Unity ships 10 unity-ai-* extensions (Animation, Particle System, ProBuilder, Cinemachine, Splines, Terrain, InputSystem, Tilemap, Navigation, Timeline); Unreal/Godot have the mechanism but no published packages yet.
- [Ecosystem & extensions](https://ai-game.dev/docs/ecosystem): The Unity `unity-ai-*` extension family (Animation, ParticleSystem, ProBuilder, Cinemachine, Splines, Terrain, InputSystem, Tilemap, and more).
- [FAQ](https://ai-game.dev/docs/faq): Common questions about setup, connection modes, and capabilities.
- [Blog](https://ai-game.dev/blog): Tutorials and walkthroughs (connect Claude Code to Unity, generate animations with AI, build a game end-to-end).

## Source

- [Unity-MCP](https://github.com/IvanMurzak/Unity-MCP)
- [Unreal-MCP](https://github.com/IvanMurzak/Unreal-MCP)
- [Godot-MCP](https://github.com/IvanMurzak/Godot-MCP)
- [GameDev-MCP-Server (self-hostable server)](https://github.com/IvanMurzak/GameDev-MCP-Server)

## Markdown versions

Every documentation page has a build-time Markdown mirror under `/docs-md/`, generated
from the same content sources as the HTML so it never drifts. These are the form LLMs
and agents parse most reliably — fetch the `.md` instead of the HTML when you can.

- [Documentation hub](https://ai-game.dev/docs-md/docs.md)
- [Quickstart](https://ai-game.dev/docs-md/quickstart.md)
- [Unity plugin setup](https://ai-game.dev/docs-md/unity-plugin-setup.md)
- [Tools catalog](https://ai-game.dev/docs-md/tools.md)
- [Unity tools catalog](https://ai-game.dev/docs-md/tools-unity.md)
- [Unreal tools catalog](https://ai-game.dev/docs-md/tools-unreal.md)
- [Godot tools catalog](https://ai-game.dev/docs-md/tools-godot.md)
- [Ecosystem & extensions](https://ai-game.dev/docs-md/ecosystem.md)
- [Best practices hub](https://ai-game.dev/docs-md/best-practices.md)
- [Unity best practices](https://ai-game.dev/docs-md/best-practices-unity.md)
- [Unreal best practices](https://ai-game.dev/docs-md/best-practices-unreal.md)
- [Godot best practices](https://ai-game.dev/docs-md/best-practices-godot.md)
- [Extensions catalog](https://ai-game.dev/docs-md/extensions.md)
- [Unity extensions](https://ai-game.dev/docs-md/extensions-unity.md)
- [Unreal extensions](https://ai-game.dev/docs-md/extensions-unreal.md)
- [Godot extensions](https://ai-game.dev/docs-md/extensions-godot.md)
- Per-extension detail: each at `https://ai-game.dev/docs-md/extensions-<engine>-<slug>.md` (e.g. extensions-unity-cinemachine.md; see the sitemap for the full set).
- [FAQ](https://ai-game.dev/docs-md/faq.md)
- [MCP endpoint info](https://ai-game.dev/docs-md/mcp-endpoint-info.md)
- [Unity engine page](https://ai-game.dev/docs-md/engines-unity.md)
- [Unreal engine page](https://ai-game.dev/docs-md/engines-unreal.md)
- [Godot engine page](https://ai-game.dev/docs-md/engines-godot.md)
- Blog posts: each post at `https://ai-game.dev/docs-md/blog-<slug>.md` (see the sitemap for the full set).