gameflow-matchmaking
Installation
SKILL.md
GameFlow Matchmaking
GameFlow forms matches from tickets and hands each match a dedicated server. You draw the matching rules as a node graph in the dashboard. Your backend creates and polls tickets. The game client only talks to your backend and then connects to host:port. The game server learns who is in the match from its payload.
client --find match--> your backend --POST /v1/matchmaking/tickets--> GameFlow
client <--host:port--- your backend <--status "assigned", "host:port"-- GameFlow (long-poll)
client --connect--> game server (reads payload: match_id, teams) --matches:start / matches:end--> GameFlow
Essentials (details in the gameflow skill):
- Base URL
https://api.gameflow.gg/v1, headerx-api-key: $GAMEFLOW_API_KEY. A 404 on a known path usually means/v1is missing. - Write request JSON in lowerCamelCase (
playerId,gameMode,timeoutSeconds). Responses are camelCase only. Unknown or misspelled fields are silently dropped. The server payload JSON is the exception: it is snake_case (match_id). - The API key never ships in a game client. Clients call your backend.
playerIdcomes from your auth, never from the request body. - If the GameFlow docs MCP is connected, check each request body against
get_api_operationbefore 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
Check these before writing code: