Steam MCP Server

Steam store/game data (no key) plus player profiles, libraries and achievements (Steam Web API).

Local serverstdioGo

What is the Steam MCP server?

Steam store/game data (no key) plus player profiles, libraries and achievements (Steam Web API). That is what the steam mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP server for Steam: search games and read store details, prices, reviews, discounts and news (no key), plus player profiles, libraries and achievements via the official Steam Web API (free key).

Getting it running

steam-games-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • search_games — –
  • get_game — –
  • get_items — –
  • discover_games — –
  • get_game_reviews — –
  • get_review_histogram — –
  • get_prices — –
  • get_specials — –
  • get_featured — –
  • get_game_news — –
  • get_global_achievements — –
  • get_current_players — –

What it needs from you

Configuration is passed through the environment: STEAM_API_KEY, STEAM_ID, STEAM_COUNTRY, STEAM_LANGUAGE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Steam.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Steam's toolset — search_games, get_game, get_items and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Grinv; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
search_games
get_game
get_items
discover_games
get_game_reviews
get_review_histogram
get_prices
get_specials
get_featured
get_game_news
get_global_achievements
get_current_players
get_wishlist
get_followed_games

How to install the Steam MCP server

{
  "mcpServers": {
    "steam": {
      "command": "npx",
      "args": ["-y", "steam-games-mcp"],
      "env": {
        "STEAM_API_KEY": "your-steam-web-api-key (optional — enables player tools)",
        "STEAM_ID": "your-steamid64-or-vanity-name (optional — default 'you' for player tools)",
        "STEAM_COUNTRY": "US (optional — store price region)",
        "STEAM_LANGUAGE": "english (optional — store language)"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
STEAM_API_KEYCredential the server authenticates with.Yes
STEAM_IDConfiguration value read at startup.Optional
STEAM_COUNTRYConfiguration value read at startup.Optional
STEAM_LANGUAGEConfiguration value read at startup.Optional

Example prompts to try

  • Use Steam to search games.
  • Use Steam to get game.
  • Use Steam to get items.

Frequently asked questions

It connects Steam to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (search_games, get_game, get_items, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Steam directly.