Skip to main content
Glama

Related Servers

Alternatives to playcal

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to verify their own work on real Godot 4 projects: edit scenes and scripts safely, launch the game, send real keyboard/mouse input, wait on conditions, read live runtime state, capture screenshots and errors, and run declarative scenario play-tests that return per-step pass/fail reports with the observed failing value.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to see and act inside a live Godot 4 editor, inspecting scene trees and capturing visual evidence while performing undo-backed, approval-gated edits with runtime verification.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to develop VRChat worlds through a live Unity editor bridge: UdonSharp authoring and out-of-Unity linting, declarative scene assembly, spatial and budget audits, assets and open-licence fetching, ClientSim scenario verification, and local PC/Quest builds without a human in the editor.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to inspect a running Unity editor's state and capture console and compiler errors, trigger asset refreshes to recompile externally edited scripts, and execute editor menu items. It closes the edit → compile → check loop by bridging tool calls to the editor main thread over a local-only HTTP listener.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read Godot editor context, search project scenes/scripts/resources, and propose reviewable scene node edits that must be previewed, confirmed, then applied through Godot's UndoRedo, after which the current scene can be run and its diagnostics collected. All writes stay within fixed allowlisted routes and node types, with no arbitrary code execution and no fabricated success when the editor is unavailable.
      31 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct concerns (meta/asset/audio checks, perf baseline, visual diff, replay, report), and descriptions are explicit about scope. The main overlap risk is among the run-related tools (loop, observe, playtest, replay), plus report/calibrate/tests, but the descriptions differentiate them well enough for an agent to choose.

    Naming Consistency4/5

    All 20 tools use a consistent `playcal_` prefix with a single short lowercase word, which is predictable and readable. There is minor inconsistency in part of speech (verbs like observe/ingest/lock mixed with nouns like logs/meta/assets), but the pattern itself is uniform.

    Tool Count4/5

    20 tools is on the heavy side for a single server, but the domain is broad (environment setup, import checks, play runs, replay, visual/perf gating, reporting, calibration, collaboration). Each tool covers a distinct workflow step, so the count is justified rather than bloated, though it sits at the upper end of comfortable.

    Completeness4/5

    Coverage is broad: setup (doctor), safety (checkpoint, lock), import validation (meta, assets, audio), execution (loop, observe, playtest, replay), gating (visual, baseline, tests), and analysis (logs, report, calibrate, ingest, ui). Minor gaps exist around baseline lifecycle management (e.g., explicitly updating/replacing a saved baseline) and test/checklist authoring, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues