AI assistants
SteamGauge is an MCP server. An assistant can find, download and read games and ask what their
players say, and the window shows each step. Its prompts appear in your assistant's own list,
such as the commands Claude Code shows under /: what players say about a game, comparing games,
and how players took an update. MCP tools lists every prompt and tool.
Hand it to your assistant
Paste this:
Add SteamGauge to yourself by following https://aureliolo.github.io/steamgauge/agent.md,
then tell me which file you changed.
It reads the guide, adds SteamGauge to its own settings, and says which file it changed.
Or do it yourself
The window's AI assistants page has Add beside every assistant it finds on this computer. From a terminal:
# Claude Code
steamgauge connect claude-code
# Claude Desktop
steamgauge connect claude-desktopClaude Code: Runs claude mcp add --scope user steamgauge -- "<path to steamgauge>" mcp. Claude Code starts it in its next session. Claude Desktop: Writes ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, ~/.config/Claude/claude_desktop_config.json on Linux, %APPDATA%\Claude\claude_desktop_config.json on Windows. Quit Claude Desktop completely and open it again.
steamgauge connect vscodeWrites ~/Library/Application Support/Code/User/mcp.json on macOS, ~/.config/Code/User/mcp.json on Linux, %APPDATA%\Code\User\mcp.json on Windows. VS Code asks once whether to trust it, the first time it starts.
steamgauge connect copilotWrites ~/.copilot/mcp-config.json on macOS and Linux, %USERPROFILE%\.copilot\mcp-config.json on Windows.
steamgauge connect cursorWrites ~/.cursor/mcp.json on macOS and Linux, %USERPROFILE%\.cursor\mcp.json on Windows.
# Devin Desktop and Devin CLI
steamgauge connect devin
# Windsurf
steamgauge connect windsurfDevin Desktop and Devin CLI: Writes ~/.config/devin/mcp_config.json on macOS and Linux, %APPDATA%\devin\mcp_config.json on Windows. Windsurf: Writes ~/.codeium/windsurf/mcp_config.json on macOS and Linux, %USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows. Refresh the servers in Cascade's MCP panel.
steamgauge connect codexWrites ~/.codex/config.toml on macOS and Linux, %USERPROFILE%\.codex\config.toml on Windows.
steamgauge connect geminiWrites ~/.gemini/settings.json on macOS and Linux, %USERPROFILE%\.gemini\settings.json on Windows.
steamgauge connect kiroWrites ~/.kiro/settings/mcp.json on macOS and Linux, %USERPROFILE%\.kiro\settings\mcp.json on Windows.
steamgauge connect zedWrites ~/.config/zed/settings.json on macOS and Linux, %APPDATA%\Zed\settings.json on Windows.
steamgauge connect opencodeWrites ~/.config/opencode/opencode.json on macOS and Linux, %USERPROFILE%\.config\opencode\opencode.json on Windows.
steamgauge connect kiloWrites ~/.config/kilo/kilo.jsonc on macOS and Linux, %USERPROFILE%\.config\kilo\kilo.jsonc on Windows.
steamgauge connect clineWrites ~/.cline/data/settings/cline_mcp_settings.json on macOS and Linux, %USERPROFILE%\.cline\data\settings\cline_mcp_settings.json on Windows.
steamgauge connect rooWrites ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json on macOS, ~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json on Linux, %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\mcp_settings.json on Windows.
steamgauge connect junieWrites ~/.junie/mcp/mcp.json on macOS and Linux, %USERPROFILE%\.junie\mcp\mcp.json on Windows.
steamgauge connect qoderWrites ~/.qoder/settings.json on macOS and Linux, %USERPROFILE%\.qoder\settings.json on Windows. Restart Qoder CLI, or run /mcp reload in it.
steamgauge connect ampWrites ~/.config/amp/settings.json on macOS and Linux, %USERPROFILE%\.config\amp\settings.json on Windows.
steamgauge connect warpWrites ~/.warp/.mcp.json on macOS and Linux, %USERPROFILE%\.warp\.mcp.json on Windows.
steamgauge connect factoryWrites ~/.factory/mcp.json on macOS and Linux, %USERPROFILE%\.factory\mcp.json on Windows.
# Tabnine CLI
steamgauge connect tabnine
# Tabnine in the editor
steamgauge connect tabnine-ideTabnine CLI: Writes ~/.tabnine/agent/settings.json on macOS and Linux, %USERPROFILE%\.tabnine\agent\settings.json on Windows. Run /mcp reload in a running session. Tabnine in the editor: Writes ~/.tabnine/mcp_servers.json on macOS and Linux, %USERPROFILE%\.tabnine\mcp_servers.json on Windows. Tabnine reads it while a project folder is open.
steamgauge connect firebenderWrites ~/.firebender/firebender.json on macOS and Linux, %USERPROFILE%\.firebender\firebender.json on Windows.
steamgauge connect piWrites ~/.pi/agent/mcp.json on macOS and Linux, %USERPROFILE%\.pi\agent\mcp.json on Windows. Run /reload in a running session.
steamgauge connect vibeWrites ~/.vibe/config.toml on macOS and Linux, %USERPROFILE%\.vibe\config.toml on Windows. A project's own .vibe/config.toml is read in place of this one.
steamgauge connect vtcodeWrites ~/Library/Application Support/com.vinhnx.vtcode/vtcode.toml on macOS, ~/.config/vtcode/vtcode.toml on Linux, %APPDATA%\vinhnx\vtcode\config\vtcode.toml on Windows. This also switches on VT Code's MCP support, which is off until set.
steamgauge connect zeroclawWrites ~/.zeroclaw/config.toml on macOS and Linux, %USERPROFILE%\.zeroclaw\config.toml on Windows. An agent uses it once one of its mcp_bundles names steamgauge, as ZeroClaw's MCP guide shows.
steamgauge connect gooseWrites ~/.config/goose/config.yaml on macOS and Linux, %APPDATA%\Block\goose\config\config.yaml on Windows. Goose loads it in its next session.
steamgauge connect hermesWrites ~/.hermes/config.yaml on macOS and Linux, %LOCALAPPDATA%\hermes\config.yaml on Windows.
steamgauge connect continueWrites ~/.continue/config.yaml on macOS and Linux, %USERPROFILE%\.continue\config.yaml on Windows. Continue uses it in agent mode, with Local Config chosen.
steamgauge connect openclawWrites ~/.openclaw/openclaw.json on macOS and Linux, %USERPROFILE%\.openclaw\openclaw.json on Windows.
steamgauge connect nanobotWrites ~/.nanobot/config.json on macOS and Linux, %USERPROFILE%\.nanobot\config.json on Windows.
steamgauge connect autohandWrites ~/.autohand/config.json on macOS and Linux, %USERPROFILE%\.autohand\config.json on Windows. Restart Autohand.
steamgauge connect deepcodeWrites ~/.deepcode/settings.json on macOS and Linux, %USERPROFILE%\.deepcode\settings.json on Windows.
steamgauge connect lm-studioWrites ~/.lmstudio/mcp.json on macOS and Linux, %USERPROFILE%\.lmstudio\mcp.json on Windows. LM Studio asks before each tool call.
steamgauge connect amazon-qWrites ~/.aws/amazonq/mcp.json on macOS and Linux, %USERPROFILE%\.aws\amazonq\mcp.json on Windows.
{"mcpServers": {"steamgauge": {"command": "<path to steamgauge>", "args": ["mcp"]}}}Settings, Tools, AI Assistant, Model Context Protocol (MCP), Add, at the Global level.
{"mcpServers": {"steamgauge": {"command": "<path to steamgauge>", "args": ["mcp"]}}}Settings, MCP, Add, Raw Config (JSON).
{"mcpServers": {"steamgauge": {"command": "<path to steamgauge>", "args": ["mcp"]}}}Settings, MCP, My Servers, Add. Qoder CLI is added by steamgauge connect qoder.
cmd mcp add --scope user steamgauge -- "<path to steamgauge>" mcpIn a terminal.
mcp:
servers:
steamgauge:
command: <path to steamgauge>
args: [mcp]In the fast-agent.yaml of the folder it runs in, and in the agent's servers.
"<path to steamgauge>" mcpAny assistant that starts an MCP server from a command. steamgauge clients prints this copy's path.
<path to steamgauge> is where the program is: %LOCALAPPDATA%\SteamGauge\steamgauge.exe from
the Windows setup, /Applications/SteamGauge.app/Contents/MacOS/steamgauge on macOS, and
steamgauge from Scoop, Homebrew or a Linux package. steamgauge clients prints it.
What it writes
One entry, named steamgauge, in the assistant's own settings file; everything else in the file
stays as it was, comments included. steamgauge disconnect <name> takes it out again.
{
"mcpServers": {
"steamgauge": {
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}Claude Desktop, Devin Desktop and Devin CLI, Windsurf, Gemini CLI, Kiro, Cline, Roo Code, Junie, Qoder CLI, Warp, Tabnine CLI, Tabnine in the editor, pi, Deep Code, LM Studio and Amazon Q Developer.
{
"servers": {
"steamgauge": {
"type": "stdio",
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}VS Code.
{
"mcpServers": {
"steamgauge": {
"type": "local",
"command": "<path to steamgauge>",
"args": ["mcp"],
"tools": ["*"]
}
}
}GitHub Copilot CLI.
{
"mcpServers": {
"steamgauge": {
"type": "stdio",
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}Cursor, Factory Droid and Firebender.
[mcp_servers.steamgauge]
command = "<path to steamgauge>"
args = ["mcp"]Codex.
{
"context_servers": {
"steamgauge": {
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}Zed.
{
"mcp": {
"steamgauge": {
"type": "local",
"command": ["<path to steamgauge>", "mcp"],
"enabled": true
}
}
}opencode and Kilo Code.
{
"amp.mcpServers": {
"steamgauge": {
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}Amp.
[[mcp_servers]]
name = "steamgauge"
transport = "stdio"
command = "<path to steamgauge>"
args = ["mcp"]Mistral Vibe.
[mcp]
enabled = true
[[mcp.providers]]
name = "steamgauge"
enabled = true
command = "<path to steamgauge>"
args = ["mcp"]VT Code.
[[mcp.servers]]
name = "steamgauge"
command = "<path to steamgauge>"
args = ["mcp"]ZeroClaw.
extensions: {steamgauge: {name: "steamgauge", type: "stdio", cmd: "<path to steamgauge>", args: [mcp], enabled: true, timeout: 300}}Goose.
mcp_servers: {steamgauge: {command: "<path to steamgauge>", args: [mcp]}}Hermes Agent.
mcpServers: [{name: "steamgauge", type: "stdio", command: "<path to steamgauge>", args: [mcp]}]Continue.
{
"mcp": {
"servers": {
"steamgauge": {
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}
}OpenClaw.
{
"tools": {
"mcpServers": {
"steamgauge": {
"command": "<path to steamgauge>",
"args": ["mcp"]
}
}
}
}nanobot.
{
"mcp": {
"servers": [
{
"name": "steamgauge",
"transport": "stdio",
"command": "<path to steamgauge>",
"args": ["mcp"]
}
]
}
}Autohand.
How it connects
- Only while the window is open. The assistant reaches the open app over a local socket, a named pipe on Windows, that no other user or machine can reach. Closing the window closes the app; while it is closed, every tool says so and the assistant asks you to open it.
- Through updates. Updating SteamGauge closes its window and leaves every assistant connected. Until you restart an assistant, it offers the tools of the version it started.
- Both handshakes,
initializeandserver/discover. - HTTP, if you need it. Off until the AI assistants page turns it on: the app then also answers on 127.0.0.1 at a port you choose, to requests carrying the token that page shows.