RPG Maker MZ MCP Server
Related Servers
Alternatives to RPG Maker MZ MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server that reads and writes RPG Maker XP project .rxdata files, enabling AI assistants to create and edit actors, items, skills, maps, events, and scripts, and render map previews, by describing what you want.6538 npm1MIT
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables management of RPG Maker MZ and MV project data, including actors, items, maps, and events. It allows users to create, update, and search game assets through natural language integration with MCP-compatible clients.371-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to act as dynamic dungeon masters for text-based RPGs with dynamically generated rule systems and comprehensive game state management.11 npm10MIT
- AlicenseNot gradedqualityBmaintenanceA plugin-based MCP server that enables AI assistants to interact with external systems through custom tools, resources, and prompts.4AGPL 3.0
- AlicenseAqualityDmaintenanceAn MCP server that gives AI assistants direct control over Godot 4 game development projects. It enables launching the editor, running projects, creating and editing scenes, writing GDScript, and inspecting assets through natural language commands.4410 npm4MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives AI assistants full control over the Godot game engine, enabling scene building, script writing, game running, and more through natural language.75229 npm3MIT
TDQS
Scored across 23 tools
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.
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.
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.
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.