Steam Games MCP

What Grinv/steam-games-mcp MCP server does

Grinv/steam-games-mcp MCP server connects an MCP client to Steam’s store and official Steam Web API. Its read-only tools cover catalog lookup, product details, prices, discounts, reviews, review history, news, current player counts, achievements, and hardware compatibility for Steam Deck, SteamOS, Steam Machine, and Steam Frame.

The server also supports account-oriented queries when a Steam Web API key is available. These include player summaries, bans, owned and recently played games, wishlists, followed games, friends, shared ownership, friend ownership, player achievement progress, vanity-name resolution, and personalized recommendations. It does not log users in or perform writes, purchases, trades, posts, or game launches.

How it works

Start with search_games when a tool needs an appid. get_game can instead resolve a title to the closest store match, but most other game tools expect the numeric appid. For catalog-wide filtering, discover_games can combine discount, release recency, native operating system, review, tag, and compatibility criteria. get_items is intended for checking a known list of appids, while get_prices handles larger price-only batches.

Store and discovery requests require no API key. Account and detailed achievement requests use the official Steam Web API and require STEAM_API_KEY; many also require a public profile or public game details. A configured STEAM_ID lets prompts refer to the configured player as “my” account, while individual tools can accept a SteamID64. resolve_vanity_url converts a custom profile name to that numeric identifier.

Some responses are deliberately capped. Examples include the first page of title search results, top games by playtime, recent reviews, achievement lists, wishlist results, and friend results. Trend and catalog tools also use bounded scans or recent windows, so a stricter filter may require a larger requested count and may still miss less popular titles.

Setup and configuration

Install the Grinv/steam-games-mcp MCP server through an MCP client using the package command npx -y steam-games-mcp. Store tools can be used with an empty environment configuration. To enable player features, create a free Steam Web API key and set STEAM_API_KEY. Set STEAM_ID to a 17-digit SteamID64 or a vanity profile name if the client should use a default player.

Optional STEAM_COUNTRY and STEAM_LANGUAGE values control the store price region and language. The repository also documents a source-based setup that builds with npm ci && npm run build and starts the generated Node entry point, but the package-based command is the direct installation path.

For account libraries, achievements, wishlists, and recommendations, the relevant Steam profile and game-details visibility generally must be public. Ban status and some profile information remain available under different visibility rules described by the individual tools.

Tools and capabilities

• Search titles and retrieve detailed store cards with pricing, genres, platforms, release information, ratings, DLC, requirements, and highlighted achievements.
• Find discounted, recent, well-reviewed, tagged, or hardware-compatible games across the catalog.
• Compare current prices, review percentages, tags, native platforms, VR support, and Steam hardware compatibility for batches of appids.
• Inspect review snapshots, historical review trends, front-page specials, featured sections, patch notes, global achievement rarity, and live concurrent players.
• Query player profiles, bans, libraries, recent play, wishlists, follows, friends, shared games, friend ownership, recommendations, and achievement progress.

The Grinv/steam-games-mcp MCP server returns structured results for these operations through MCP rather than exposing a separate interactive login flow.