Skip to main content
Glama
a951753abc

RPG Maker MZ MCP Server

by a951753abc

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
load_projectA

Load an existing RPG Maker MZ project. Must be called before using other tools.

create_projectA

Create a new RPG Maker MZ project with default data files.

get_project_infoA

Get information about the currently loaded RPG Maker MZ project.

list_resourcesC

List resource files (images, audio) in the project.

list_entitiesC

List all entities of a given type (actors, items, weapons, etc.)

get_entityB

Get detailed information about a specific entity by ID.

create_entityB

Create a new entity. Provide the entity data as a JSON object. Required: name. Other fields use defaults if omitted.

update_entityB

Update an existing entity. Only provided fields will be changed.

delete_entityA

Delete an entity by ID. Cannot delete system default entities (ID 1) for actors/classes/states.

search_entitiesC

Search entities by keyword across name and description fields.

list_mapsB

List all maps in the project with their hierarchy.

create_mapC

Create a new map.

get_mapB

Get detailed information about a specific map, including its events.

update_mapC

Update map properties (name, display name, BGM, note, etc.).

delete_mapB

Delete a map. Cannot delete Map 1 (system default).

list_eventsC

List all events on a specific map.

create_eventC

Create a new event on a map at the specified position.

update_eventC

Update event properties (name, position, note, character sprite).

add_event_commandsA

Add commands to an event page. Commands use human-readable format that gets converted to RPG Maker MZ codes.

Supported command types:

  • show_text: { type: "show_text", face: "Actor1", faceIndex: 0, text: "Hello!" }

  • show_choices: { type: "show_choices", choices: ["Yes", "No"] }

  • transfer_player: { type: "transfer_player", mapId: 1, x: 5, y: 5 }

  • control_switches: { type: "control_switches", startId: 1, value: 0 } (0=ON, 1=OFF)

  • control_variables: { type: "control_variables", startId: 1, operationType: 0, operand: 0, value: 100 }

  • control_self_switch: { type: "control_self_switch", key: "A", value: 0 }

  • conditional_branch: { type: "conditional_branch", conditionType: 0, param1: 1, param2: 0 }

  • common_event: { type: "common_event", eventId: 1 }

  • change_gold: { type: "change_gold", operation: 0, value: 100 }

  • change_items: { type: "change_items", itemId: 1, operation: 0, value: 1 }

  • play_bgm: { type: "play_bgm", name: "Town1", volume: 90 }

  • play_se: { type: "play_se", name: "Decision1" }

  • wait: { type: "wait", duration: 60 }

  • fadeout_screen, fadein_screen, erase_event, game_over, return_to_title

  • comment: { type: "comment", text: "This is a comment" }

  • label/jump_to_label: { type: "label", name: "start" }

  • And many more (change_hp, change_exp, battle_processing, shop_processing, etc.)

delete_eventC

Delete an event from a map.

generate_scenarioA

Generate a game scenario outline based on theme and genre. Returns structured suggestions that can be implemented using other tools (create_entity, create_map, create_event, etc.).

generate_dialogueA

Generate NPC dialogue for a scene. Returns event commands that can be directly used with add_event_commands.

generate_questC

Generate a quest design with objectives, rewards, and event flow.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 23 tools

Disambiguation4/5

Most tools have clearly distinct purposes, cleanly separated by resource (entities, maps, events) and action (list/get/create/update/delete). The only mild overlap is among the generation tools (generate_quest, generate_scenario, generate_dialogue), which are related but target different scopes (quest vs. full scenario vs. dialogue), and add_event_commands vs. generate_dialogue which is complementary rather than conflicting.

Naming Consistency5/5

Nearly every tool follows a strict verb_noun snake_case pattern (get_project_info, load_project, create_entity, update_map, delete_event, add_event_commands). The convention is applied uniformly across projects, resources, entities, maps, and events with no style mixing.

Tool Count4/5

23 tools sits at the heavy end of the reasonable range, but the domain genuinely spans projects, resources, entities, maps, events, event commands, and content generators, so most tools earn their place. Slightly more than ideal, but not bloated or redundant.

Completeness4/5

The surface covers the full lifecycle well: project load/create/info, entity and map and event CRUD, and rich event-command authoring plus generators. Minor gaps exist (e.g. no get_event for a single event, no way to remove/edit already-added event commands, no delete_project), but agents can work around these.

Maintenance

ActivityInactive
ResponsivenessNo issues