record
record 1-5 frames with 100-1000 ms delay between them
LABSCO SUMMARY
The editor builds and runs the game; the decorator answers from inside it.
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.
What it is
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.
What you get
- 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())insideebiten.RunGame
Requirements
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.
Setup effort
One command — go run github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0
USE CASES
01
Showing the agent what the bug looks like
Capture a run of frames from the live game instead of describing what you saw.
02
Debugging something that only shows up over time
Take several frames with a delay between them and compare what changed.
03
Catching a failure that happens before the window appears
Build and launch output is captured too, so a crash at startup is visible.
04
Keeping the game code untouched
One wrap call in ebiten.RunGame is the whole integration; nothing else in the project changes.
1 tool
Listed in project code.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool registered in the project's code.
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
go run github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"ebitengine-mcp": {
"command": "go run github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"ebitengine-mcp": {
"type": "stdio",
"command": "go",
"args": [
"run",
"github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0"
]
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"ebitengine-mcp": {
"command": "go",
"args": [
"run",
"github.com/sedyh/ebitengine-mcp/cmd/server@v1.1.0"
]
}
}
}
