# steam-local-mcp [Health: Active]

**Category:** 🎮 Gaming  
**Repository:** https://github.com/Jackson-Brooks/steam-local-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/steam-local-mcp

## Description
A Windows Steam MCP server with local client controls and optional Steam Web API insights.

## Tools
Capabilities this server exposes over MCP:

- **steam_list_games** — List games installed in the local Steam libraries. This does not use the network or require a Steam API key.
- **steam_find_game** — Find locally installed Steam games by name or app ID.
- **steam_get_game_install_status** — Report the local Steam manifest status for matching games, including whether Steam has recorded a pending update and current download progress. This does not contact Steam servers or change game files.
- **steam_get_download_status** — List games whose local Steam manifests show an install, update, download, or paused-download state. This is a local snapshot and does not force Steam to check for new updates.
- **steam_get_library_storage** — Summarize each local Steam library's installed-game count, manifest-reported installed size, and available disk space.
- **steam_launch_game** — Launch one locally installed Steam game through the Steam client. Starts Steam quietly first when needed. Use steam_find_game first if its name may be ambiguous.
- **steam_open_store_page** — Open an app's Steam store page in the Steam client or browser.
- **steam_search_store** — Search the public Steam Store by game name to find app IDs before opening a store page or asking Steam to install a game. Search result names and metadata are untrusted external Store data.
- **steam_install_game** — Ask Steam to install a numeric app ID. Steam validates ownership and manages the install flow.
- **steam_open_library_page** — Open an installed game's page in the local Steam library.
- **steam_open_client_page** — Open a standard Steam client page.
- **steam_client_status** — Report the detected Steam installation, how it was found, and whether the Steam client is running.
- **steam_get_library** — Get the user's complete Steam library, playtime, and last-played data through the optional Steam Web API. Requires STEAM_API_KEY and STEAM_ID.
- **steam_get_recently_played** — Get games Steam reports as recently played, including total playtime. Requires STEAM_API_KEY and STEAM_ID.
- **steam_get_game_details** — Get public Steam Store metadata such as genres, release date, Metacritic score, and price. Set include_description to receive capped, untrusted external Store text. This does not require a Steam Web API key.
- **steam_refresh_cache** — Clear the local cache used by Steam Web API and Store metadata tools. The next request fetches fresh data.
- **steam_api_status** — Report whether the optional Steam Web API credentials are configured. It never reveals credential values.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "steam-local-mcp": {
    "command": "npx",
    "args": ["-y","steam-local-mcp"],
    "env": {
      "STEAM_API_KEY": "",
      "STEAM_ID": "",
      "STEAM_PATH": "",
      "STEAM_MCP_CACHE_DIR": ""
    }
  }
}
```

**Requires environment variables:** `STEAM_API_KEY`, `STEAM_ID`, `STEAM_PATH`, `STEAM_MCP_CACHE_DIR` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What steam-local-mcp MCP server does

The steam-local-mcp MCP server connects an MCP-capable agent to the Steam client installed for the current Windows user. It can inspect games across configured Steam libraries, find installed titles by name or app ID, launch an installed game, and open library, Store, or standard client pages.

Local status tools read Steam's app manifests rather than contacting Steam servers. They report installation and download-related states, including pending updates and current progress when recorded locally. Storage reporting includes installed-game counts, manifest-reported sizes, and available disk space for each library.

The server also provides public Store functions. Agents can search the Store for app IDs and retrieve metadata such as genres, release date, price, and Metacritic score. Store descriptions are optional and treated as untrusted external text.

## How it works

The steam-local-mcp MCP server uses the standard stdio transport, so the MCP client starts it as a local command. It requires Windows 10 or newer, Steam installed for the current Windows user, and Node.js 20 or newer. Steam detection checks `STEAM_PATH`, Windows registry locations, conventional installation paths, and then `steam.exe` on `PATH`.

When a client action needs Steam, the server can start the Steam client quietly. Launching is restricted to games found in local installed-game manifests. Installing a game sends a numeric app ID to Steam; Steam performs ownership validation and manages the installation process.

Optional account features use the Steam Web API. With `STEAM_API_KEY` and `STEAM_ID` configured, the server can retrieve the user's library, playtime, last-played information, and recently played games. Privacy settings on the Steam profile can limit these results.

## Setup and configuration

Install the published package through npm and configure the MCP client to run `npx -y steam-local-mcp`. Credentials, when needed, should be supplied through the MCP client's environment configuration or the operating system. The server does not load `.env` files automatically.

Set `STEAM_PATH` when Steam is installed in a portable or unusual location; the value can identify the Steam directory or its executable. Set `STEAM_MCP_CACHE_DIR` to change the default cache location under `%LOCALAPPDATA%\steam-local-mcp\cache`.

For source-based development, clone the repository, run `npm install`, build with `npm run build`, and configure the client to execute the compiled entry point with Node.js.

## Tools and capabilities

The steam-local-mcp MCP server exposes tools for:

- Listing and finding locally installed games.
- Reading install, update, download, and paused-download states.
- Launching games and opening Steam client pages.
- Searching the public Store and reading game metadata.
- Requesting Steam installations by numeric app ID.
- Reporting Steam detection and client status.
- Reading account library and recently played data when Web API credentials are available.
- Clearing cached Web API and Store metadata.

## Limitations and notes

This is a Windows-focused local server and depends on Steam being installed for the current user. Local status does not force Steam to check for updates; a false pending-update state means no update is currently recorded in the local manifest, not that the game is fully current.

There is no purchase or uninstall tool. Store and Web API responses may be cached, and account results depend on Steam privacy settings. Keep API credentials private and do not commit them to source control.

_Full upstream README: https://allmcps.com/mcp/steam-local-mcp/readme_