GameCrew AIEarly access
Sign in
Contributor

Build a Godot 4 game with Claude Code or Cursor over MCP

Connect Claude Code or Cursor over MCP, fork a Godot 4 game, and your assistant writes GDScript while GameCrew AI compiles, tests and builds it. No install.

What you’ll have at the endA Godot 4 game of your own that your coding assistant changes in GDScript, that GameCrew AI compiles, tests and builds for the browser, and whose code you can download.

What you need

  • Claude Code, Cursor or another MCP client.
  • A Google account to sign in with.
  • No Godot install: GameCrew AI runs Godot 4.

Steps

  1. Claude Code: add the server

    Add GameCrew AI over HTTP, then run /mcp and choose to sign in. Your browser opens GameCrew’s page: sign in with Google and press Connect.

    claude mcp add --transport http gamecrew https://play.gamecrew.ai/mcp
  2. Cursor: let it sign you up

    Tell Cursor (or any assistant that can run commands) the line below. It starts a sign-up and shows you a link and a code: open the link, sign in, check the code matches and press Connect. It gets a token and the MCP settings to add. Restart the session so the tools load. Already have an account? On the studio’s Usage page, Connect a coding assistant, Make a token (Games and assets) gives the settings to paste, shown once.

    Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md
  3. Start from a Godot game

    list_showcase shows each game’s engine. fork_game makes a game of your own; create_branch makes a branch instead, to change the game and offer the change back.

  4. Read the project

    project_map gives the scripts, scenes, tuning and tests at a glance; read_file reads CLAUDE.md and README.md. A Godot game’s code is GDScript with its scenes and resources as text (.gd, .tscn, .tres, .gdshader) in Assets/Game/.

  5. Get the API right

    engine_api gives exact offline Godot 4 signatures, and search_techniques finds engine-specific guides (linked below).

    engine_api: CharacterBody3D.move_and_slide
  6. Edit

    edit_file changes part of a file; write_file writes a whole one.

  7. Compile, test and play

    run_unity runs the game’s own engine, Godot here: compile, scene, test, capture, or play for a private browser build of unsaved work. Godot steps take seconds.

  8. Save a version

    save_version with a message written like a commit subject. On a fork it runs the full checks; on a branch it is a quick save, not checked until it is merged.

  9. Play it and take the code

    get_game has the play link. In the studio, a version on Versions has Download the game’s code (zip): the Godot project, to open in Godot 4.

What a contributor has

2 games of your own, 30 engine minutes a day and one engine run at a time. Free in early access.

Connect your assistant now

Add this address as a connector, or tell a coding assistant “Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md”.

https://play.gamecrew.ai/mcp
Join as a contributor