gameflow-servers

Installation
SKILL.md

GameFlow dedicated servers

You ship a Linux server build. GameFlow builds it into an image, runs it in your regions, autoscales it and hands players a host:port. Your server process talks to the platform only through the GameFlow Game Server SDK.

Account, API key and CLI setup live in the gameflow skill. The essentials, repeated here:

  • API base https://api.gameflow.gg/v1, header x-api-key: $GAMEFLOW_API_KEY.
  • Write lowerCamelCase JSON. Unknown or misspelled request fields are silently dropped, not rejected.
  • Responses are camelCase and always include zero values. int64 fields come back as strings.
  • The key never goes into a game client. Only your backend, CI, and (if it calls the API) the dedicated server hold it.
  • Don't invent endpoints, CLI flags or SDK methods. If it isn't here or in the references, say "verify in the docs or API reference".
  • If the GameFlow docs MCP is connected, check each request body against get_api_operation before writing it. If a field name differs from this skill, don't choose yourself or write code with either name. The docs can be ahead of the deployed API, and the wrong name is silently dropped. Show the user both names and ask which one their environment accepts.

0. Prerequisites

Installs
4
First Seen
Oct 20, 2026