RPG Maker MV MCP Server
Related Servers
Alternatives to RPG Maker MV MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI models to develop and automate RPG Maker MZ projects by creating maps, events, and plugins through natural language commands. It provides comprehensive tools for database management, asset integrity checks, and direct map tile manipulation.287 npm1ISC
- AlicenseBqualityDmaintenanceEnables AI agents to directly manipulate RPG Maker MZ projects through natural language commands, allowing creation and modification of game assets like items, weapons, enemies, maps, and plugins without manually editing game files.3670 npm2MIT
- AlicenseBqualityAmaintenanceEnables AI assistants to read and write RPG Maker MZ projects directly, covering database, maps, events, and system settings with 119 tools.10070 npm6MIT
- AlicenseAqualityDmaintenanceEnables creating RPG Maker MZ games using natural language through AI assistance, with tools for project management, map creation, event systems, and batch operations.1070 npm1MIT
- AlicenseCqualityDmaintenanceProvides tools for managing RPG Maker MZ game data, maps, events, and system settings through natural language, enabling AI-assisted game development.3570 npm29MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and edit RPG Maker VX Ace and VX project data files directly, including databases, maps, events, scripts, and validation, without requiring Ruby.1MIT
TDQS
Scored across 28 tools
Each tool has a clearly distinct purpose, covering events, maps, plugins, skills, records, project info, backups, and playtesting. No overlapping functionality; create_damage_skill, create_healing_skill, and create_state_skill are specialized but clearly different.
Almost all tools follow a consistent verb_noun snake_case pattern (e.g., create_event, list_maps). Only playtest_log and playtest_status deviate by starting with a noun instead of a verb, which is a minor inconsistency.
With 28 tools, the count exceeds the recommended range for a well-scoped server. While the domain is broad, many tools (e.g., three separate skill creators) could be consolidated, making the surface feel heavy and potentially confusing.
Significant gaps exist: there is no get_record for full record reads, no delete operations for records, maps, or events, and no tile editing support. This leaves critical CRUD operations incomplete, hindering agent workflows.