Gameye

What Gameye does

Gameye MCP server exposes the Gameye orchestration API as tools that an MCP-compatible client can call. Agents can start billable containerized game server sessions, inspect their state, retrieve connection ports and players, and stop sessions by exact ID. Player membership can also be recorded through join and leave operations.

The Gameye MCP server covers more than session lifecycle operations. It can identify available hosting locations and organization regions, check image-tag availability, inspect applications and upstream registry tags, and enable tags for preloading. Agents can retrieve session logs, download files or directories from containers as tar archives, and create or edit applications when the token has the appropriate permissions.

How it works

The server communicates with clients over standard input and output using MCP. Each tool result identifies the environment and API host used for the request. The process selects one environment at startup; tools do not accept an environment parameter, so separate client entries are needed when both sandbox and production access are required.

Session launches apply configured guardrails, including a default time-to-live and an agent label. Launch and stop operations, application changes, tag enabling, and token creation are marked as write or destructive actions, and some support dry-run behavior. Starting a session incurs a charge according to the source documentation.

Setup and configuration

Node.js 22 or newer is required for the npm-based installation. Start the Gameye MCP server with npx -y gameye-mcp and provide GAMEYE_API_TOKEN. GAMEYE_ENV selects sandbox or production and defaults to sandbox. GAMEYE_API_URL can provide a custom HTTPS host for testing, while GAMEYE_TIMEOUT_MS changes the per-request timeout from its 30-second default.

The Gameye MCP server can be registered in Claude Code or in an MCP client configuration using an mcpServers entry. The documented clients include Claude Desktop, Cursor, and Windsurf. A published container image is also available for Docker on amd64 and arm64 systems. When using Docker, keep standard input enabled and do not allocate a terminal. Mount a writable directory if artifact downloads or token files must persist outside the container.

Use the least-privileged token scopes needed for the intended workflow. Observer access covers reads such as sessions, logs, artifacts, regions, and applications. Operator access adds session launch, stop, and state changes; deployer access adds application changes; token-admin access adds token creation.

Tools and capabilities

The Gameye MCP server provides tools for:

• Reading server context, session lists, session details, logs, artifacts, regions, locations, applications, and registry tags.
• Launching and stopping sessions, with dry-run support for applicable operations.
• Registering or removing players from sessions.
• Checking image tags and enabling tags for application preloading.
• Creating and editing applications.
• Creating API tokens and writing them to files.
• Comparing installed Gameye skills with the latest pack and optionally applying updates.

Limitations and notes

The project is in beta, and its tools, inputs, outputs, and behavior may change between releases. A Gameye API token is required, and permissions limit what an agent can do. Do not place that token in a game server's environment, because processes inside the container could read it.

The selected environment belongs to the server process and cannot be changed during a conversation. Artifact and token files written through Docker remain inside the container unless a host directory is mounted. On Windows, token-file permissions differ from macOS and Linux, and skill updates report commands instead of applying them automatically. Session launches are billable, so write access should be granted deliberately.