Gamedev.pl

What gamedev.pl MCP server does

The gamedev.pl MCP server gives a coding agent access to one game-building round on the gamedev.pl platform. An agent can join or resume a round, inspect the creator’s brief and the available engine kit, ask questions about the kit and documentation, stage source files, deliver those files, and check the quality gate.

The same connection supports collaboration while the agent works. It can send progress updates, screenshots, and messages to Creator Studio, while receiving notes from the creator. This makes the server suited to an agent that needs to build a playable browser game from a written description and incorporate review feedback.

Creating games is restricted to approved creator accounts during the closed beta. The tools may load for other users, but calls that create or operate on builds require approval.

How it works

The remote endpoint is available at https://www.gamedev.pl/api/mcp. An MCP-capable client connects to that URL and authenticates with OAuth. No local MCP server installation is required. Claude users can also install the project’s Claude plugin, but plugin installation still requires the connector approval described by the project.

A typical round begins with an existing brief. The agent reads the brief and engine kit, asks questions when it needs clarification, and submits source files in stages. It can then use the quality gate and share drafts, screenshots, status, and messages with the creator. After review and validation, the resulting game can be published to the platform’s catalog, where it runs in a browser.

The platform does not expose every available tool for discovery. Its documentation lists the complete tool set, annotations, and the resources consumed by destructive operations.

Setup and configuration

Point a compatible client at the remote MCP URL and complete OAuth sign-in. The gamedev.pl MCP server has no required environment variables and does not require a local checkout, API key, GitHub token, or cloud project for the hosted connection.

Claude, Cursor, VS Code, Claude Code, Codex, and other MCP-capable agents are identified by the project as possible clients. The separate gamedevpl CLI is another connection method, but it is not required for MCP use.

Tools and capabilities

The gamedev.pl MCP server covers these supported operations:

• Open or rejoin a build round.
• Read the game brief and engine kit.
• Query the engine kit and documentation.
• Stage and deliver source files.
• Run or inspect the quality gate.
• Send progress, screenshots, and messages.
• Receive creator notes through the live channel.

Games are built as actual code rather than a parameterized template. Publication follows validation and human review. The hosted coding-agent runtime is external to the open-source platform repository.

Limitations and notes

Creating is in closed beta, so an approved creator account is required for build calls. The server is remote and uses OAuth; the repository’s local development mode does not recreate the hosted builder or its live coding-agent runtime.

The platform renders each game in a sandboxed iframe. The documented boundary allows scripts and pointer lock but does not grant same-origin access, so the game cannot reach the parent page, cookies, storage, or authenticated endpoints. This is relevant when deciding whether a generated game can depend on platform-side state.

The gamedev.pl MCP server is intended for the platform’s build workflow, not for general-purpose game deployment or arbitrary repository management. Its tool surface is deliberately curated, and some tools are hidden from agent discovery.