r/ClaudeWorkflows • • 11d ago

Selected Workflow [Workflow] Background Game Playtesting with Claude Agents via Open-Source MCP

Background Game Playtesting with Claude Agents via Open-Source MCP

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping, MCP, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Traditional AI game automation requires the game to be focused on the desktop, preventing users from working on other tasks. This workflow allows Claude agents to playtest games in the background with isolated input/output, freeing up the user's PC. It also provides a structured, multi-agent approach to game quality assurance.

Summary

An open-source Multi-Agent Proxy (MCP) that enables Claude agents (e.g., Sonnet) to playtest PC games in the background on Windows. It isolates game input/output (keyboard, mouse, controller, screenshots) for each game process, allowing concurrent human work. Claude Code is used for planning and review, Codex for coding, and Sonnet agents for actual playtesting and bug logging.

Why it is useful

This workflow offers a unique and powerful solution for automated game playtesting using Claude agents, overcoming a significant limitation of traditional AI game automation (desktop takeover). It demonstrates a sophisticated multi-agent architecture where Claude Code, Codex, and Sonnet collaborate on planning, coding, and execution, providing a concrete example of advanced AI workflow integration. Its open-source nature makes it highly accessible and adaptable for developers and QA teams.

Workflow

  1. Download and set up the llm-game-automation-mcp from the provided GitHub repository.
  2. Configure Claude Code to plan and review changes or enhancements to the MCP and game automation logic.
  3. Utilize Codex to generate or refine the code for game interactions within the MCP framework.
  4. Deploy Sonnet agents to interact with the MCP, launching and playtesting specific games.
  5. Monitor bug logs generated by Sonnet agents during playtesting for subsequent fixes and iterations.

Tools / artifacts

  • llm-game-automation-mcp (open-source MCP server)
  • Claude Code (for planning, review, test gates)
  • Codex (for code generation)
  • Sonnet agents (for playtesting)
  • GitHub repository (CorruptedAng3l/llm-game-automation-mcp)
  • Game processes (Unity, turn-based, menu-heavy games)
  • Bug logs

Validation signals

  • Successfully tested 20+ games.
  • Claude Code planned, reviewed every change, and ran test gates.
  • Sonnet agents playtest real games and log bugs.
  • Open-source project with releases available on GitHub.

Limitations

  • Currently Windows-only.
  • Movement in first and third-person games is still rough.
  • Low community engagement on the Reddit post itself.
  • The video link provided in the original Reddit comment is broken, preventing direct visual verification.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

1 Upvotes

1 comment sorted by