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."
- "Import this Mixamo run onto the warrior and show me a preview."
- "Which items use this texture?"
- "Find every map with a Queen Crook on it."
- "Fill this new map with the monster camps from the first field map, at half the mob count."
- "Double the respawn time of every spawn I have selected."
- "Install everything except the map table change, and show me what clashes."
The assistant opens clients, worlds, projects and maps; searches monsters and models; adds, moves and changes objects, arranges them, moves them between layers, scatters props, copies and pastes and places prefabs; tunes spawns and populates a map from another; reads the problems list; reviews, reverts and installs changes; exports spawn tables; runs a world's exporters, builds terrain and walkable grids; records and replays macros; opens models, plays animations and spells, dresses characters and saves captures; poses bones, edits keys and imports animations; edits meshes and paints on models; browses and extracts from archives; recolors, paints and resizes textures; finds what uses a file; edits scripts, NPC dialogs and game data; 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:
| prefix | what it drives |
|---|---|
studio_ | the window: what is open, showing a panel or tab, screenshots and photos, saving the project under a name, and bug reports to us when you are signed in |
map_ | the map editor |
model_ | the model viewer |
packs_ | the Packs panel |
texture_ | the texture editor: recolor, paint, fill, replace, resize, format, mip levels, PNG export, editing in an image editor, and saving |
asset_ | Where used: what reads a file, a model's files, unused files, and the index's progress |
compare_ | Compare clients: another client folder against the open one, each file's differences, a model beside the other client's, taking files across and the report |
server_ | the Server panel, and Test in game |
project_ | the changes review: everything Install would write, each change's diff, and Revert; project packages; and project_publish, which puts the client changes on the server's launcher updater |
script_ | the server's Lua scripts: list, read, open, write and check |
dialog_ | NPC dialogs: pages, answers, buttons and links, undo and checks |
gamedata_ | game data tables: rows, checks, column math, CSV and saving into the project |
macro_ | macros: record, list, show, edit, replay and delete |
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, a call to a tool that does not exist gets the nearest names back, and a call that cannot run yet says which tool to use first.
Models: posing, editing and painting
Inside model_, each part of the model viewer has its own group of tools:
model_pose_boneandmodel_pose_selectpose a bone as pose mode does, andmodel_clip_keys,model_clip_flipandmodel_clip_markersdo the dope sheet's work by key. See Animations.model_clip_import,model_clip_mappingandmodel_clip_actionsimport an animation, show or save its bone mapping, and point an RF Online monster's action at a clip. See Importing animations.model_edit_beginthroughmodel_edit_applyrun an Edit tab session: parts, selection, transforms, operations, parts from other models, weights, undo, and a review before anything is written. See Editing a model.model_paint_begin,model_paint_stroke,model_paint_fill_uv,model_paint_saveand their undo, redo and revert paint on the model, andmodel_glow_maskpaints an RF Online glow mask. See Painting on the model.model_blender_editandmodel_clip_blenderopen the model, or the clip showing, in Blender. See Editing in Blender.model_item_iconandmodel_item_variantrender an RF Online item's inventory icon and make a recolor variant. See Importing models.model_rowslists the game data rows that draw the model in front.
model_clip_import, model_clip_actions, model_edit_apply, model_item_icon and model_item_variant take dry_run, which returns what they would write without writing it.
Installing and reviewing
map_plan_install, map_install, project_changes, project_revert and server_test_in_game take the same choice as the Install dialog in scope: only the map or document in focus, or the whole project. project_changes lists every change with a key, and with key shows that change's diff. map_plan_install, map_install and server_test_in_game take only or exclude, lists of those keys, which narrow the install the way unticking changes in the review does. When two maps' changes to one file clash, map_plan_install returns the clash under its issue, as the Install dialog shows it. project_revert reverts one change, or with whole_map the whole map.
map_list_backups lists the project's install backups, newest first, and map_restore_backup restores the newest or the one it names. Test in game asks before restarting a server and says how many players are connected to it.
See Projects and Install and Problems, changes and undo.
Spawns and layers
map_tune_spawnsreports the selected spawns' count, respawn time and radius as ranges, or sets, offsets or scales them as one step, refusing what the server would refuse.map_populate_spawnslists another RF Online map's monster blocks, or places them on the open map with a mob count factor, and returns the new spawns' ids.map_set_layermoves objects to another layer, or to a new one, as the inspector's Layer row does.
Macros
macro_record starts a recording, and stops it to save it under a name or cancels it. While it runs the assistant's map edits and yours are both kept. Every step that adds objects returns their ids, and a later step naming one of them is replayed against the replay's own copy. macro_list and macro_show say what would stop a replay, including the steps that name objects from before the recording. macro_edit renames a macro and removes or moves steps. macro_play replays on the open map, with anchor for where it lands (recorded, selection, cursor or first) and fixed_ids for objects from before (stop, keep or skip). A replay is one undo step and reports the step that failed, if one did.
To make a macro that replays on any map, an assistant selects with map_select by kind or search, or with map_select_similar, instead of naming ids. Objects added by map_run_steps verbs do not come back as created ids, so a later step naming one counts as an object from before. See Macros.
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. Installing, restoring a backup, stopping a server, Test in game, reverting a change and deleting a macro are marked as tools that change things for good, 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 draft a bug report about Studio with studio_report_bug. Studio opens the draft in its Report a bug window, where you can read and change it; nothing is sent until you press Send, and Cancel drops it. A sent report is filed under your name and marked as drafted 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.