gamedev.pl MCP server

gamedev.pl

Describe a game. An AI agent builds it. Everyone plays it in the browser.

Play now → www.gamedev.pl · closed beta

You write a few sentences about a game you want. The app asks what it needs to know, then you can hand the brief to the platform builder or connect your own coding agent over MCP. The agent builds actual code, not a template with the numbers changed. After review, the game appears in the catalog and runs in a browser. Bring friends — some games turn phones into controllers around one shared screen.

Every game above was built this way.

This repository is the platform that does all of that, and it is open source.

Watch an AI dev team ship in public

Most of this codebase was written by coding agents, and the pipeline that builds the games is itself run by agents. That is unusual enough to be worth watching rather than just reading about:

before any code is written.

• A creator's description becomes a spec, and a QA gate asks real clarifying questions

Claude Code, Codex, or other MCP-capable agent.

• A creator chooses the hosted platform builder or connects their own Cursor, VS Code,

works; creator notes return over the same live channel.

• The agent reports progress, screenshots, and playable drafts to Creator Studio while it

relying on a stale branch or pull request.

• Revisions start a new task from the exact stored version the creator played, rather than

agent-maintained games repository.

• Every game passes the validation gate and human review before publication to the separate,

One guarantee that CI enforces: every game in the catalog is playable with a thumb. Touch support is derived from each game's source, not declared in its spec, so a game cannot claim playability it does not have.

The interesting engineering is written up in docs/ — start with docs/README.md.

Connect your agent (MCP or the gamedevpl CLI)

Two doors, same games. The on-site page is https://www.gamedev.pl/connect (also /mcp). It lives in the header menu, not on /create or public game pages.

MCP. The server is remote and needs no install: point an MCP-capable client at https://www.gamedev.pl/api/mcp and sign in with OAuth. Claude users can install it as a plugin instead — listings/mcp/claude-plugin/README.md has the exact sequence, including the connector approval that installing does not do on its own. The official registry entry is pl.gamedev/creator.

The tools cover one build round: opening or rejoining it, reading the brief and the engine kit, asking the kit and docs a question, staging and delivering source files, checking the quality gate, and exchanging progress, screenshots and messages with the creator. Several more exist and are deliberately never advertised, so an agent will not discover them. listings/mcp/README.md lists every tool with its annotations, what each destructive one actually consumes, and why the rest are hidden.

CLI. apps/cli is the gamedevpl terminal client (no local model). With no verb it opens a REPL: talk first; a game starts when you ask for one. gamedevpl checkout is the own-editor path. Installers (/install.sh) 404 while CLISURFACE is off. With the flag on, the route serves the script even if no cli-v GitHub release exists yet — that download is what fails then. Until a release ships, npm install then npm run bundle -w @gamedevpl/cli. Details: apps/cli/README.md.

Shortened. The full README is on GitHub.