Skip to main content
Glama
RPG Maker MZ Authoring MCP

RPG Maker MZ Authoring MCP

by NixonMSilva

Related Servers

Alternatives to RPG Maker MZ Authoring MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to inspect and edit an RPG Maker MZ project through its real JSON data files, render maps to PNG previews so layouts can be seen rather than guessed, and decode event commands into named, parameter-labelled lines. It also drives a live playtest through a bridge plugin and authors whole maps, databases, events and assets via high-level tool calls.
      65
      2
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables 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.
      28
      23 npm
      1
      ISC
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to read and write RPG Maker MZ projects directly, covering database, maps, events, and system settings with 119 tools.
      4
      128
      173 npm
      31
      MIT

    TDQS

    C2.9/5.0

    Scored across 75 tools

    Disambiguation2/5

    Several tools are near-duplicates: apply_changes, apply_event_changes and database_apply_changes are explicit aliases, and preview_changes / preview_event_changes / database_preview_changes all accept the same operation list. Read-side tools also blur together (get_map_summary vs list_map_events vs describe_map_event vs get_map_event; get_event_page vs describe_event_page vs get_event_page_native), so an agent can easily pick the wrong one.

    Naming Consistency4/5

    The surface is overwhelmingly snake_case with verb_noun patterns, and domain prefixes (database_*, map_*, event_*) group related tools predictably. Minor deviations exist (render_map, select_project, and a few noun-first names), but nothing that breaks the pattern.

    Tool Count2/5

    75 tools is far beyond what a coherent set should expose for one project editor, and the excess is partly literal duplication: three aliases of apply_changes and three overlapping preview entry points. Many finely sliced read tools (get_event_page_native, describe_event_page, get_event_logic) could be collapsed into a few parameterized tools.

    Completeness1/5

    No other domain expectations apply. The response only attempts to match a provided reference answer instead of answering the tool-coherence question, so it is not a usable assessment of this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues