Working with an AI assistant

GoMMO Studio can be driven by an AI assistant that supports MCP (the Model Context Protocol), such as Claude Desktop, Claude Code, LM Studio or Cursor, including one running a model on your own computer. You describe what you want and the assistant does it in the window while you watch, using the same tools you would.

What you can ask

• "Put a ring of wolf spawns around the lake."
• "Move every lantern on this street up by 20."
• "Show me every wolf, walking, from the side."
• "Dress the warrior in the best armour and export it for Blender."
• "Make this armour's red parts blue and save it."
• "Find every map with a Queen Crook on it."

The assistant opens clients, worlds, projects and maps; searches monsters and models; adds, moves and changes objects, arranges them, scatters props, copies and pastes and places prefabs; reads the problems list; exports spawn tables; runs a world's exporters, builds terrain and walkable grids; opens models, plays animations and spells, dresses characters and saves captures; browses and extracts from archives; recolours textures; and takes screenshots of the window to check its own work.

Connecting it

Add GoMMO Studio to your assistant as a local (stdio) MCP server whose command is gommostudio.exe with the argument -mcp. In Claude Desktop that is an entry in claude_desktop_config.json, with the path you unzipped Studio to:

{
  "mcpServers": {
    "gommo-studio": {
      "command": "D:\\Tools\\GoMMO Studio\\gommostudio.exe",
      "args": ["-mcp"]
    }
  }
}

In Claude Code it is one command:

claude mcp add gommo-studio -- "<install folder>\gommostudio.exe" -mcp

If Studio is already open, the assistant works in that window; otherwise it opens one.

The tools it sees

The tools are grouped by name, so an assistant can tell them apart:

studio_status says what the window has open and is the first thing an assistant should call; map_status, model_status and server_status go into detail on their part. Every argument a tool takes is described to the assistant, a call with a wrong or misspelt argument is refused before anything changes, and a call that cannot run yet says which tool to use first.

What stays in your hands

Every change the assistant makes to a map is an ordinary edit: it shows up in the undo history, and nothing reaches your client until the map is saved and installed. Install, Restore and stopping a server are marked as tools that change things outside Studio, so an assistant that supports it asks you before running them, and an install made by an assistant is backed up exactly like yours.

When you have signed in to Studio with your oldschoolops.com account, the assistant can report a bug about Studio to us with studio_report_bug, under your name and marked as written by your assistant. It cannot sign in for you. See Signing in and reporting bugs.

Studio only accepts an assistant from your own computer: it listens on a local address, with a key it writes into %APPDATA%\GoMMO Studio\mcp\ while it is open.