Skip to main content
Glama
a951753abc

RPG Maker MZ MCP Server

by a951753abc

Related Servers

Alternatives to RPG Maker MZ MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      MCP 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.
      65
      38 npm
      1
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      A 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.
      37
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A plugin-based MCP server that enables AI assistants to interact with external systems through custom tools, resources, and prompts.
      4
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      44
      10 npm
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An 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.
      75
      229 npm
      3
      MIT

    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