Skip to main content
Glama
twrsm666

rpgmaker-mcp

by twrsm666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to rpgmaker-mcp

No user-submitted related servers found.

    Related Servers

    • rpgmaker-mz-mcp

      Redseb
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to read and write RPG Maker MZ projects directly, covering database, maps, events, and system settings with 119 tools.
      128
      140 npm
      11
      MIT

    • RPG Maker MZ MCP Server

      rein1225
      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
      10 npm
      1
      ISC

    • RPG Maker MV MCP Server

      Xerolo44
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to act as co-developers for RPG Maker MV projects, providing full database CRUD, map and event editing, plugin management, playtest control, and automatic backups.
      41
      51 npm
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 65 tools

    Disambiguation2/5

    While each tool targets a distinct operation, the server has layered overlapping abstractions that are hard to tell apart: create_map vs make_map, set_tiles vs set_tileset_flags, place_event vs make_npc vs make_choice_scene, make_chest, link_maps, make_shop, make_encounter_zone, make_battle, and make_item all ultimately write events or database rows; add_commands vs write_plugin_source vs set_commands vs make_choice_scene write scripts; and many live_* tools overlap (live_eval, live_key, live_move, live_step). An agent choosing between the high-level builders and the low-level primitives has no clear rulebook.

    Naming Consistency3/5

    Mostly snake_case is consistent, but verb styles are mixed: imperative verbs (get, set, create, delete, list, add, remove, copy, place, clear), 'make_' builders (make_map, make_npc, make_battle, make_item, make_choice_scene, make_chest, make_shop, make_encounter_zone), and nouns (project_info, command_catalog, block_structure, tile_slots) coexist, with several live_* tools. The pattern is readable but not predictable.

    Tool Count2/5

    65 tools is far beyond typical MCP guidance and forces an agent to navigate layers of abstractions for the same underlying write operations. The high-level builders could collapse many of the primitive tools, reducing cognitive load.

    Completeness5/5

    The surface covers the RPG Maker MZ lifecycle end to end: map creation, tile painting, event scripting, database CRUD, plugin management, asset validation, backup/undo, validation, and live runtime control. No obvious domain gap remains; even asset import and rollback are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources