The server assembles your project and passes flags on launch that the embedded decorator picks up — the decorator executes the tool request and replies over a reverse connection, then closes. That is why an answer arrives with the application's own logs attached: the server appends them before handing the result back.
A Go MCP server that builds and launches your Ebitengine game, then captures what it does: frames from the running game plus build, launch and runtime output.
- Frames captured from the running game — N frames with a delay of M milliseconds between them
- Build and launch logs captured alongside the frames
- Application errors surfaced with the run rather than lost in a terminal you closed
- A one-line change on your side: wrap the game with `mcp.Wrap(NewGame())` inside `ebiten.RunGame`
Go. Add the package with `go get github.com/sedyh/ebitengine-mcp@v1.1.0`, wrap your game, and register the server as `go run github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0`. DrawFinalScreen is supported; LayoutF is not.
Build from source — clone the repository and build it, then point your client at the binary