GameCrew AIEarly access
Sign in
Contributor

Make a VR game with your own assistant over MCP

Your own assistant forks a VR showcase game and changes its code; GameCrew AI runs the engine, checks it in an emulated headset and hosts a Quest-ready link.

What you’ll have at the endA VR game of your own, forked from a VR showcase game and changed by your assistant, with a play link that offers Enter VR in a headset’s browser.

What you need

  • An assistant that uses MCP: Claude, ChatGPT, Claude Code, Cursor, VS Code or another MCP client.
  • A Google account to sign in with.
  • Nothing to install: GameCrew AI runs the engine.

Steps

  1. Connect your assistant

    In a chat app that takes custom connectors, add GameCrew AI with this address and nothing else. In a coding assistant that works in a terminal or an editor, tell it the line below instead: it starts the sign-up for you.

    https://play.gamecrew.ai/mcp Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md
  2. Press Connect

    GameCrew’s page opens in your browser. Sign in with Google and press Connect. That press is the only thing you do by hand. When every contributor place is taken the button says Join the queue: your place is kept and you are told when one opens.

  3. Find a VR game to start from

    Ask your assistant which showcase games play in VR. It calls list_showcase, and get_game says vr: true for a VR game.

    List GameCrew’s showcase games and tell me which ones play in VR.
  4. Fork it

    Ask it to fork that game. fork_game makes a game of your own from its newest version that passed its checks. It stays a VR game, plays at once, and is one of your 2 games.

  5. Let it learn the project

    It reads the project with project_map and read_file: CLAUDE.md, README.md, and Assets/CCGD/VR.md, the engine kit’s VR guide (the rig, the two hands, comfort locomotion, menus drawn in the world).

  6. Look up how it’s done

    Before it builds something hard, it can search the technique library with search_techniques and read a guide with read_technique. The VR guides are linked below.

  7. Ask for the change

    Say what should change in VR. The assistant edits the game’s own code with edit_file and write_file (in Assets/Game/).

    In VR, let me grab the jar with grip and throw it. Show the score on my left wrist.
  8. Run it

    run_unity runs the game’s own engine: compile, then test. Step play makes a browser build of the unsaved work with a private link for you. A build takes seconds on Godot and Quick, minutes on Unity.

  9. Save a version

    save_version with a one-line message. On your fork it runs the full checks, and for a VR game the emulated-headset check after the browser check.

  10. Play it in your headset

    Ask for the play link (get_game), open it in your headset’s browser and press Enter VR.

Start from a VR game

Your own assistant can’t switch VR on for a flat game yet: that switch is in the studio for Platform accounts. Fork a game that already plays in VR.

What a contributor has

2 games of your own (forks), branches of games you can see, 30 engine minutes a day, one engine run at a time, and 20 credits once for generated art. Free in early access. Your assistant’s own work runs on your own AI subscription.

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