Reclaimer Kit · Lesson 11 of 11

Work the Kit with an AI assistant

Let an assistant on your computer, such as Claude Code, work the Kit's window: open a map, place objects and AI, compile and playtest, while you watch every edit arrive as one you can undo.

Level
Intermediate
Before you start
The Reclaimer Kit, and an assistant that speaks the Model Context Protocol (MCP) on the same computer: Claude Code, Claude's desktop app or any other MCP client. Complete the AI lesson first, so you know what the assistant is doing for you.
You will make
A saved scenario with two teams of AI spawners that an assistant placed, set up and playtested, and a compiled package of it.

Shortcuts use Ctrl; Cmd also works on macOS, and Alt is Option. Keep the pointer over the viewport for editing shortcuts. Save before switching projects.

Know what an assistant can reach

The Kit can answer an assistant's requests through the same commands its menus, outliner, object browser and AI tab use. An assistant can open maps, list and place objects, set an object's and an AI spawner's settings, build squads, zones and objectives, read tags, run HaloScript in the console, save, compile, playtest and take pictures of the window.

  • It is off until you turn it on, and answers this computer alone, only requests that carry the Kit's token. A web page can't reach it.
  • Its edits are yours. Each is an undo step, a report in the status bar and a row of the Info Log. What the Kit refuses you, it refuses the assistant in the same words.
  • Installed maps are never changed, as with your own edits.

Turn the server on

  1. Open PreferencesChoose Edit → Preferences… and find Assistants (MCP).
  2. Let assistants inTick Let assistants use the kit. Leave the Port at 47610 unless another program uses it.
  3. Check that it listensThe section now says Listening at with the address, http://127.0.0.1:47610/mcp.

The setting is kept for the next start. To turn it on for one run only, start the Kit with --kit-mcp.

Connect your assistant

  1. Copy the commandFor Claude Code, choose Copy Claude Code command. It copies a claude mcp add --transport http reclaimer-kit ... line with the Kit's address and token in it.
  2. Run it oncePaste the line in a terminal and run it. Claude Code now lists reclaimer-kit among its servers.
  3. Another clientFor any other MCP client, choose Copy address and token and put the address and its Authorization header in that client's settings.

The token is a key to the Kit's window. Keep it to yourself, and choose New token if it has gone anywhere it shouldn't: assistants set up with the old one are refused until you give them the new one.

Ask for one small change

  1. Open the Info LogChoose View → Info Log, so you can see each request arrive.
  2. AskTell the assistant, in your own words: open Guardian in the Reclaimer Kit, put a Warthog beside the first spawn point, and take a picture of it.
  3. Watch it workThe map opens, the Warthog appears in the viewport and the outliner, and each request is a row of the Info Log, such as assistant: kit_add_object.
  4. Undo it yourselfPress Ctrl+Z with the pointer over the viewport: the Warthog goes, as if you had placed it.

Observable result: the assistant reports what it did and shows you the picture it took, and your undo takes its edit back.

Have it stage a battle

An assistant is quickest at repetitive work: many objects, each with the same settings. Ask for something like this:

  1. Describe the battleOn a multiplayer map, place ten AI spawners of Marines on the Red team on one side of the middle and ten of Brutes on the Blue team on the other, drop them to the ground, give each a range of 60 and a respawn of 10 seconds, then save the scenario as guardian_battle.
  2. Use another game's AI if you have itWith Halo: Reach installed, the assistant can tick Halo: Reach's objects for you, and the map loads again with Reach's spawners, such as Spartan (Reach) and Elite (Reach), offered. Ask it to leave their weapon on Its own.
  3. PlaytestAsk it to play the map and take a picture, or press F5 yourself. While the level is played, the assistant can read, use the console and take pictures, but its edits wait until you return to the Kit.
  4. CompileAsk it to compile the map, or press Ctrl+B.

The assistant can also build squads in the AI tab: fire teams with characters of other maps and games, vehicles, zones, objectives with goal areas, and firing positions placed many at once on a grid, each put on the ground or a set height over it for flying vehicles.

Check and keep the result

  • Look over the outliner: every spawner the assistant placed is there, and the Object tab shows its settings as you would have set them.
  • Play the compiled package in a game, as in the sharing lesson. What you check there is what players get.
  • Read the Info Log for anything refused. An assistant can't yet write tag fields, task scripts, conditions, hints or patrol routes, import files, or finish a dialog a command opens: do those yourself in the window.
  • A request the window can't take up within 20 seconds, such as one sent while the Kit is minimized, comes back saying so.

Turn it off

Untick Let assistants use the kit in Preferences. The server stops at once and closes its connections; the Kit answers nothing until you tick it again. A new token or a new port also closes the old connections.

Next step

Return to the tutorial library, or look up everything an assistant can do in the Kit reference.