Automation

MCP integration

Use publisher-scoped MCP tokens so agents and developer tools can manage games without sharing account passwords.

Endpoint and auth

Rendered MCP endpoint and Authorization Bearer header reference.
Every MCP client uses the same endpoint. Permissions are controlled by the publisher-scoped token.
Endpoint: https://newgame.win/mcp
Header: Authorization: Bearer <mcp-token>

Available scopes

  • publisher:read, games:read, games:write
  • builds:read, builds:write, releases:read, releases:write
  • testers:manage, capacity:read, capacity:request

Tooling model

Each token is bound to one publisher. All game, build, release, tester, and capacity operations are checked against that publisher boundary.