The operations layer goes past status polling: comparison across servers, alerting on the ones with problems, a trend built from accumulated samples, and a diagnosis pass that names a likely cause. Administration is deliberately harder to reach — RCON passwords live in environment variables named by the inventory file rather than in the file itself, and changing the inventory needs an admin token matched on both sides.
Two halves in one server: the Steam Web API for profiles, libraries and player counts, and a gamedig-based operations layer over game servers you register in a servers.json file.
- Steam lookups: a vanity URL turned into a SteamID, a profile summary, owned and recently played games, live concurrent players for an app, and an app's news and patch notes
- Game servers you have registered queried for name, map, player count and ping, plus the player list and the server's cvars
- All registered servers seen at once, one server's health diagnosed, several compared with a recommendation, and only the problem servers filtered out
- Player-count trend for a server, built from samples that accumulate as you query it
- A diagnosis pass that analyzes the cause rather than only reporting the state
- Administration over RCON: kick a player, ban one for 1h, 24h, 7d or permanently, request a restart, or run a whitelisted RCON command such as status, say, players or time
- Server inventory: add and remove entries in servers.json, list what is registered without authentication, and discover candidates through the Steam Master Server — with a dry run that proposes rather than writes
- Recent player_join, player_leave and error events pulled out of a server's log file
Node.js 18 or newer, and a Steam Web API key in STEAM_API_KEY — without it every Steam tool returns a message telling you to check the variable. Run it with npx steam-game-server-mcp@latest over stdio, from the npm package steam-game-server-mcp, currently 1.0.1. STEAM_ID sets a default account so tools do not need one passed in. The game-server half depends on a servers.json inventory: STEAM_MCP_SERVERS_PATH points at it, falling back to ./servers.json, and with neither present only the Steam tools work. RCON passwords are never stored in that file — each server names an environment variable and the password is read from it. Adding or removing servers needs STEAM_MCP_ADMIN_TOKEN set and the same value passed as the adminToken parameter. Log reading takes a local file path only, not a remote URL or SSH. Tool descriptions are in Korean.
One command plus a key — npx steam-game-server-mcp@latest, then supply credentials