Agent access
Let an AI agent work on the project open in Studio over MCP, while you watch every edit land.
Studio can serve an MCP endpoint (the Model Context Protocol) on your own computer. Any agent that speaks MCP can then work on the project open in Studio: Claude Code, Claude Desktop, opencode, Codex, Cursor, Gemini CLI and others.
An agent's edit goes through the same services as an edit made by hand. It appears on the canvas as it lands, it is saved by the same auto-save, and each call that changes the project is one step of undo. You can pause the agent, undo what it did, or edit alongside it at any moment.
Agent access needs a Studio release after 1.4.5. Studio must be open while the agent works: the endpoint is part of Studio, and an agent can only reach it while Studio runs.
What an agent can do
| Area | What the tools cover |
|---|---|
| Projects | Create a project from the Skeleton or Empty template, open one, change its name, design resolution, game languages and the settings a new player starts with |
| Assets | Import images, audio, video and fonts, make labelled placeholder images, find where an asset is used and delete assets nothing uses, list audio tracks, ask you for access to a folder outside the project |
| Characters and variables | Create, update and delete characters with image poses, dialogue avatars and an entrance position; build layered characters from images named by layer and tag, or from a PSD, and preview their looks; declare, rename and delete global variables |
| Story | Read and write a whole scene as .story text; create, rename and delete scenes; rename and delete chapters; set the entry scene; rename a story |
| Interface | Read and write pages, Game UI and components as .ui text, make small element edits, install the standard working screens in a project made from the Empty template, rename and delete pages and set the entry page, apply interface templates, set the palette and fonts, screenshot a page or one control in its hover or pressed state, read what you selected |
| Blueprints | Read and write blueprints as .bp text, remove one left behind, and run one from a story row |
| Translation and voice | Translate story lines, names, interface text, named keys and plugin text into the game's languages, marked Machine for you to review; set the voice languages and the recording file-name rule, and link recordings to their lines by name or one by one |
| Plugins | Whatever the tools of a plugin loaded in the project offer. The built-in Gallery plugin's tools fill the Extra page with CGs, recollections, music and voice lines |
| Checking and building | Run the project checks and the built-in tests, play the game in Dev Mode line by line and click, point and press keys in it, read the console, build for the current system, Windows, macOS, Linux or the web |
Every tool is listed in Tools.
What it cannot do
- Edit data a plugin owns, unless the plugin offers agent tools for it. See Plugin tools.
- Set up Live2D or Spine characters. The model and its runtime are set up in the character editor; the agent writes the story rows that drive them.
- Change the audio bus. It can list the audio tracks only.
- Set the project icon, signing credentials or other build settings, or build for Android or iOS.
- Write files in the project folder directly. Every change goes through a tool, so you can see it and undo it.
- Read Studio's own folders, your home folder as a whole, or a drive root, even with full access. See Folders outside the project.
Two pieces
The MCP server is built into Studio and is off until you switch it on. It gives an agent the tools.
The narraleaf-make-game skill is the guide the agent follows: the order of work, the text formats it writes, interface design rules and the traps to avoid. Studio exports it as a folder, and the server also serves the same guide to agents that cannot load skills.
The exported folder also holds an optional second skill, narraleaf-port-renpy, for porting a Ren'Py game that comes with its source. See Porting a Ren'Py game.
Next
Connecting an agent
Switch on agent access and add Studio to your agent.
Making a game with an agent
From a script and art to a built game, and how to step in.
Tools
Every tool, grouped by what it works on.
What agent access exposes
Who can reach the endpoint, the folders an agent may read, and the switches that limit it.
Troubleshooting
Connection problems and refusal codes.