RPG Maker MZ

This MCP server lets you control RPG Maker MZ projects with AI agents, enabling direct creation and modification of game assets, maps, plugins, and resources. You can instruct the AI to design items, enemies, maps, or plugins and see those changes reflected in your project, streamlining your development workflow.

How to use

Connect your MCP client to the RPG Maker MZ MCP Server to start issuing commands. You can request actions such as creating items, defining new skills, generating maps, installing plugins, or scanning available resources. The server ensures changes are applied safely and synchronized with the editor, so you can iterate quickly without risking data loss.

How to install

Prerequisites you need before installing: Node.js (recommended latest LTS) and npm. You also need access to your RPG Maker MZ project and engine installation.

# Step 1: Clone the MCP server
git clone https://github.com/devmagary/MCP-Maker.git
cd MCP-Maker

# Step 2: Install dependencies
npm install

# Step 3: Build the project
npm run build

Configuration and connection

Configure your MCP client to connect to the local server. The provided examples show how to wire your client to run the MCP server via a Node command and point to the built entry file.

{
  "mcpServers": {
    "rpgmaker_mz": {
      "command": "node",
      "args": ["C:/path/to/MCP-Maker/dist/index.js"],
      "env": {
        "RPGMAKER_PROJECT_PATH": "C:/Users/You/Documents/RMMZ/MyGame",
        "RPGMAKER_ENGINE_PATH": "C:/Program Files (x86)/Steam/steamapps/common/RPG Maker MZ"
      }
    }
  }
}

Operational notes

Two common ways to run the server are shown in practice: using a client integrated command line or an editor’s configuration. The environment variables specify where your RPG Maker MZ project is located and where the engine is installed. The server uses safe write operations and editor synchronization to prevent conflicts while you edit assets.

Notes on multiple clients

If you use different clients, you can configure separate MCP server entries so each client connects to the same local server or to another instance. Maintain consistent environment variables across configurations to ensure correct project paths and engine locations.

Troubleshooting

If changes do not appear in RPG Maker MZ, verify that the editor is syncing correctly with the server. Check that the project path and engine path are accurate, and confirm that the built entry file exists at the path you provided in the config. Ensure that your Node process has permission to read and write the project files.

Safety and reliability

The server applies changes atomically to prevent partial writes and data corruption. This reduces the risk of breaking your project while AI-driven edits are being applied.

Resources and capabilities

You can explore the server’s full feature set, including database-like CRUD for assets, map generation, plugin installation, and resource scanning. Use these capabilities to build richer game content and automate repetitive tasks.

Security considerations

Limit access to trusted clients, keep your project and engine paths private, and monitor the server while experiments run. Regularly back up your project before applying automated edits.

Available tools

Database CRUD

Create, read, update, and manage assets such as items, weapons, armors, enemies, states, actors, classes, and skills with structured validation and safety checks.

Map & World

Create and list maps, generating MapXXX.json files with metadata like size, tileset, and BGM.

Plugin & Resources

Install plugins by generating JS files and registering them, and scan available graphics, audio, and DLC resources.

Safety Features

Atomic writes with SafeWriter and editor synchronization to ensure data integrity and prevent conflicts.