Skip to main content
Glama
Sign In
RPG Maker MV MCP Server

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start playtest

playtest_start

Launch a playtest of the current RPG Maker MV project in a browser or NW.js runtime, stopping any previous session and returning the URL or captured output for testing.

Instructions

Start a playtest of the current project. mode 'nwjs' launches the game with an NW.js runtime (pass runtimePath, e.g. the Game.exe inside the RPG Maker MV install's nwjs-win folder) and captures its stdout/stderr. mode 'browser' serves the project over a local HTTP server and returns a URL to open. Any previous playtest is stopped first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "playtest_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNobrowser
portNoPort for browser mode
runtimePathNoPath to NW.js executable. If omitted in nwjs mode, common install locations (Steam, KADOKAWA, the project's own Game.exe, $RPGMAKER_MV_NWJS) are probed automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, and it does well: it discloses the implicit stop of any prior playtest (a side effect), that NW.js mode captures stdout/stderr, that browser mode returns a URL, and how the runtime is resolved when omitted. It doesn't state what happens on failure (e.g., missing runtime, occupied port).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core action and each subsequent sentence covering one distinct behavior (mode nwjs, mode browser, prior-playtest stop). Slightly dense parenthetical, but every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param, no-required, no-annotation, no-output-schema tool, the description covers the essential behaviors an agent needs to call it correctly. The main remaining gap is error/edge-case handling such as an unresolvable runtime or a port conflict.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds real meaning beyond the 67% schema coverage: it explains runtimePath concretely (Game.exe inside the RPG Maker MV install's nwjs-win folder) and ties mode to its consequences. The port parameter and its default are left entirely to the schema, keeping it just short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Start a playtest of the current project") and immediately distinguishes its two modes with concrete, differentiating detail: NW.js launch with captured stdout/stderr vs. browser mode serving over HTTP and returning a URL. An agent can tell this apart from playtest_status, playtest_stop, and playtest_log without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context on when each mode applies and how to supply runtimePath in NW.js mode, plus the key precondition that any previous playtest is stopped first. It doesn't explicitly point to playtest_stop or playtest_log as follow-ups, but the mode-selection guidance is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools