Rpgmaker Xp MCP

What rpgmaker-xp-mcp MCP server does

The rpgmaker-xp-mcp MCP server connects an AI assistant to an RPG Maker XP project and operates on the project’s native .rxdata files. It can read existing game data, create or update database records, edit map events, paint map tiles, and produce static map previews. Changes are written to the actual project files, so RPG Maker XP can open the result normally.

Supported project content includes actors, skills, items, weapons, armors, maps, events, scripts, and system data. The server is intended for RPG Maker XP’s RGSS1 Ruby 1.8 Marshal format, not the formats used by VX, VX Ace, MV, or MZ.

How it works

An MCP client launches the server over standard input and output, then exposes its tools to the model. The server reads the project directory identified by RPGMAKER_PROJECT_PATH. Map files are stored in the project’s Data/ directory, and the server understands XP-specific structures such as event command codes, actor parameter tables, equipment slots, and skill damage fields.

Map previews are static PNG renders. They show the layout that was authored but do not execute the game, validate gameplay, or replace testing in RPG Maker XP. When an operation writes to a file for the first time in a session, the original is copied to Data/.mcp-backup/ as a .bak file. This is a session-level safety measure, not long-term version control.

Setup and configuration

Install Node.js 18 or newer and an MCP-capable client. The published package can be launched with npx, or the repository can be cloned and built with npm install followed by npm run build. Configure RPGMAKER_PROJECT_PATH with the folder containing Game.rxproj and Data/.

Set RPGMAKER_RTP_PATH when the RPG Maker XP RTP is installed somewhere other than the default Steam location. RTP assets are read from the local installation; they are not bundled with the server. Claude Desktop and Claude Code examples are provided in the project documentation, and other MCP clients can connect through the standard stdio transport.

Close RPG Maker XP while the server is running. The editor can rewrite its data files when saving and may overwrite changes made by the server. Back up the complete Data/ folder before editing, and use source control if you need durable history.

Tools and capabilities

The documented tool groups cover several parts of an XP project:

• Read, create, update, and search actors, items, skills, weapons, and armors.
• Create damage, healing, and state-based skills using XP’s power, scope, and stat-influence fields.
• Inspect maps and events, create events, update event commands, add dialogue, and create transfer links between maps.
• Create maps, inspect tile data, set tiles, fill regions, apply autotiles, and scatter tiles.
• Validate map connectivity and search map events by their content.
• Render a map to a PNG preview for visual inspection.

The server handles XP-specific message structures, including continuation lines and the four-line message box layout. Transfer-event creation checks that target maps and positions exist before writing.

Limitations and notes

The rpgmaker-xp-mcp MCP server does not generate artwork or audio. It can import, classify, and validate graphics that already exist, but it cannot draw new assets. It also stores RGSS scripts as data rather than writing or verifying script logic, and it cannot run the game or perform gameplay tests.

Pokémon Essentials projects are structurally readable because they are based on RPG Maker XP, but the server does not understand Essentials-specific PBS files, plugin conventions, or custom data classes. Large Essentials projects require particular care with backups. RPG Maker XP itself is required when a project depends on RTP assets.