Skip to main content

MCP for Blazium Games

The Blazium Games MCP server lets AI agents create and update game pages, ship and promote builds, read analytics, crash reports, reviews, and bug tickets, manage game keys, and issue deploy credentials. Version 1.11.0 has 66 developer tools (54 after 2026-10-28) and 34 player tools.

ProtocolMCP 2026-07-28, Streamable HTTP
Endpointhttps://mcp.blazium.games/mcp
AuthOAuth 2.1 with PKCE (no token needed), or an API key sent as a Bearer token

Manage access at blazium.games/settings/mcp.

Want an agent to buy, top up, or download games for you as a player? Use the separate player server at https://mcp.blazium.games/player.

Using Cursor?

Install the Blazium Games Cursor plugin. It adds this server plus skills that walk the agent through store pages, deploys, and crash debugging.

Add the server URL only. Your client discovers the authorization server, opens a Blazium Games sign-in and consent page, and completes PKCE on its own.

Cursor mcp.json:

{
  "mcpServers": {
    "blazium-games": {
      "url": "https://mcp.blazium.games/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http blazium-games https://mcp.blazium.games/mcp

On the consent screen you choose what the client may manage:

  • Account: every project you own or administer.
  • A single project: only that project. Account-level tools (profile, account, keys, setup, creating games, payments) return 403 with code 4030.
  • What it may do: a preset such as Store page, CI, Crash triage, Keys, Money, Read-only, or Full access. See Scopes. Read-only write calls return 403 with code 4031.

Access renews automatically for 30 days from when you approved it, then the client asks you to sign in again. Each renewal replaces the refresh token; if an old one is ever used again, the whole chain is revoked and the client has to ask you again.

Option B: API key​

  • Account key: create one at blazium.games/settings/mcp. It covers every project you own or administer.
  • Your key for one project: create one from the project's edit page, MCP tab. It only controls that project.

Cursor mcp.json with a key:

{
  "mcpServers": {
    "blazium-games": {
      "url": "https://mcp.blazium.games/mcp",
      "headers": {
        "Authorization": "Bearer bgames_mcp_YOUR_KEY"
      }
    }
  }
}

Other clients send Authorization: Bearer bgames_mcp_... on every request to https://mcp.blazium.games/mcp.

Never commit a key. Keep it in your client's config or a secret store.

Next​