Skip to main content
Glama

Related Servers

Alternatives to renpy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      An MCP server for Ren'Py project tooling that enables AI agents to inspect game state, evaluate expressions, read/write variables, and capture screenshots from running Ren'Py games.
      54
      49 PyPI
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides 70+ MCP tools for creating and managing Ren'Py projects, enabling natural language requirements to be converted into editable projects with build, preview, and asset generation capabilities.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.
      31
      25 npm
      16
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents debug Python code by running scripts, setting breakpoints, stepping through execution, inspecting live variable values, and editing or reverting files to verify fixes. It relies only on Python's standard sys.settrace, requiring no debugpy, DAP, pdb, or PTY.
      MIT

    TDQS

    A4.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is intentional overlap: run_renpy can duplicate compile/lint, check_project combines compile+lint, and exec_rpy is a universal write escape hatch. These overlaps are well-documented, so misselection risk is low but not zero.

    Naming Consistency5/5

    All 19 tools use the same tool_ prefix followed by snake_case verb_noun or verb_noun_phrase patterns. The convention is predictable throughout with no mixed casing or verb styles.

    Tool Count4/5

    19 tools is slightly above the typical 3-15 range, but the domain is broad (script editing, compilation, linting, assets, saves, docs, translation). Each tool appears to serve a meaningful purpose, though a few convenience tools could be merged.

    Completeness4/5

    The surface covers the core Ren'Py development lifecycle well: reading, writing, compiling, linting, fixing, assets, docs, saves, and translation checks. Minor gaps exist (e.g., asset deletion, direct label renaming/deletion), but exec_rpy and run_renpy provide escape hatches for most missing operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues