Skip to main content
Glama

Related Servers

Alternatives to Courtship

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with running games in real time — introspecting game state, simulating keyboard and mouse input to actually play, capturing screenshots, executing Lua code, hot-reloading files, and receiving push notifications when state changes.
      8
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Let coding agents play, test and tune your 2D web game. The debuff MCP server attaches to the game you have open (or runs a headless copy) and gives agents live state, explained and source-mapped errors, frame timings, typed params, deterministic replays and rewind, scenario tests and fuzz playtesting. Everything an agent does shows in your dev panel, where you can undo it.
      21
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      AI-native open-source 2D game engine whose MCP server exposes every editor operation to coding agents as typed commands, so an agent can build, run, and verify a game inside the editor. It runs locally on macOS, Windows, and Linux with no cloud service or API key.
      43
      MIT

    TDQS

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools mostly occupy distinct roles: discovery, schema loading, proxied invocation, usage reporting, and a LÖVE-specific router. The only mild overlap is between love_task and call_tool, since both can lead to execution, but the descriptions make their intended levels of abstraction reasonably clear.

    Naming Consistency4/5

    Four tools follow a clear verb_noun snake_case pattern: discover_tools, load_tool_schema, call_tool, report_usage. love_task deviates as a domain-specific noun phrase, but it remains readable and stylistically consistent in casing.

    Tool Count5/5

    Five tools is well-scoped for a meta/proxy server focused on LÖVE development assistance. Each tool has a clear role in the discovery-to-invocation workflow, and there is no obvious padding.

    Completeness4/5

    The surface covers discovery, schema inspection, invocation, usage reporting, and a domain router, which is a coherent lifecycle for a proxy server. A dedicated list-all-tools operation is not explicit, though discover_tools likely covers most needs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues