# Steam [Health: Active]

**Category:** 🎮 Gaming  
**Repository:** https://github.com/pipeworx-io/mcp-steam  
**GitHub Stars:** 0  
**npm Downloads (last month):** 472  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/steam

## Description
Steam Web API: profiles, owned games, achievements, app news, player counts.

## Tools
Capabilities this server exposes over MCP:

- **resolve_vanity_url** — Vanity URL → SteamID64.
- **player_summary** — Fetch public Steam profile for a single SteamID64: persona name, avatar, profile URL, country, last logoff, visibility status.
- **player_summaries** — Fetch public Steam profiles for up to 100 comma-separated SteamID64s in one request; returns persona name, avatar, country, and status for each.
- **friend_list** — List a Steam user's friend list by SteamID64; optionally filter by relationship type (friend or all). Returns array of SteamID64s and relationship status.
- **owned_games** — List all games owned by a SteamID64; optionally include app name/icon and free-to-play games. Returns appid, playtime_forever (minutes), and per-game metadata.
- **recently_played** — List games played by a SteamID64 in the last two weeks, with playtime in the last 2 weeks and total playtime. Optional count caps results.
- **player_achievements** — Achievements for a game.
- **player_stats** — User stats for a game.
- **player_level** — Return the Steam Community level (integer) for a given SteamID64.
- **player_bans** — Check VAC ban, community ban, and economy ban status for one or more comma-separated SteamID64s. Returns CommunityBanned, VACBanned, NumberOfVACBans, DaysSinceLastBan.
- **app_news** — App news feed.
- **app_details** — Store page detail (Steam Store API).
- **app_list** — Full app list (large).
- **current_player_count** — Current concurrent players.

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

```json
"mcpServers": {
  "steam": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-steam"],
    "env": {
      "PLATFORM_STEAM_KEY": ""
    }
  }
}
```

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

## Documentation

## What Steam MCP server does

The Steam MCP server gives MCP-compatible agents access to public data from Steam. Its tools cover player identity and profile information, friends, owned and recently played games, achievements, per-game statistics, Steam levels, and ban status. It also exposes application news, store details, the complete application list, and current concurrent player counts.

The server is suited to questions such as identifying a Steam ID from a vanity URL, checking which games a player owns, retrieving achievement progress for a specific title, or comparing current player counts. It does not provide general Steam account control; the documented capabilities are read-oriented data lookups.

## How it works

The implementation uses two Steam endpoints: `api.steampowered.com` for Steam Web API data and `store.steampowered.com/api` for store information. MCP clients call named tools with arguments such as `steamid`, `appid`, `steamids`, language, country code, or result limits.

Two connection modes are available. The hosted Pipeworx endpoint exposes the Steam tool pack through MCP, while the local package communicates over standard input and output. The hosted connection also lists shared Pipeworx tools, including routing and discovery functions; the standalone process exposes only the Steam pack's tools.

## Setup and configuration

For a hosted connection, add the Pipeworx MCP URL to an MCP client configuration. The README names Claude Desktop, Cursor, and Windsurf as examples. The hosted endpoint is `https://gateway.pipeworx.io/steam/mcp`.

For local use, run `npx -y @pipeworx/mcp-steam` and configure the MCP client to launch that command. The local mode does not require a Pipeworx account or a gateway round trip, but Steam authentication still follows the package's API-key configuration. The platform key is named `PLATFORM_STEAM_KEY`; requests can also provide a key with the `_apiKey` parameter.

## Tools and capabilities

The available operations include:

- Resolve a vanity username to a SteamID64.
- Read one or multiple player summaries and friend lists.
- List owned or recently played games.
- Retrieve achievements and statistics for a player's game.
- Read Steam level and player ban information.
- Fetch application news and store details.
- List Steam applications or get the current player count for an app.

The hosted gateway can also accept natural-language requests through `ask_pipeworx`, which selects a tool and fills its arguments. This routing function is part of the gateway connection rather than the standalone Steam process.

## Limitations and notes

The full application list is described as large, so clients should account for a potentially substantial response. Store details come from the Steam Store API, while the remaining documented data is sourced from the Steam Web API.

Hosted pack connections include shared Pipeworx meta-tools in addition to the Steam tools. Their exact tool scope can change, so the connection's `initialize` response is authoritative. The local process avoids those shared tools and exposes only the Steam-specific set.

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