npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

steam-user-mcp

v1.0.4

Published

MCP server for Steam — library inspection, backlog recommendations, and game wishlist. Works alongside itad-mcp and opencritic-mcp.

Readme

steam-mcp

An MCP (Model Context Protocol) server that connects AI assistants to the Steam Web API and storefront services. Enables game library analysis, backlog recommendations based on mood, wishlist evaluation, and storefront searches. Works alongside itad-mcp and opencritic-mcp.

npm version

What this does

This server acts as the foundational layer of a 3-server gaming stack:

  • steam-mcp (this one) — understands your Steam library, playtime, backlog, wishlist, and tastes. It surfaces game AppIDs.
  • opencritic-mcp — takes game names/AppIDs and provides detailed critic scores and reviews.
  • itad-mcp — takes game names/AppIDs and finds the best deals across legitimate storefronts and historical lows.

Example workflow: User: "I want something atmospheric and chill to play tonight."

  1. steam-mcp (recommend_from_library) finds unplayed "Atmospheric" + "Relaxing" games in your backlog.
  2. opencritic-mcp validates which of those games have great critic scores.
  3. User: "These look great, any of them on sale?"
  4. itad-mcp takes the AppIDs and checks if any are on sale right now.

Wishlist deal check: get_wishlist → take AppIDs → itad-mcp get_historical_low → surface any games at or near their historical low price.

Tools

| Tool | Parameters | Description | Requires API Key? | |---|---|---|---| | get_library | steam_id (string, optional)sort ("playtime" | "recent" | "name")filter ("all" | "unplayed" | "played")limit (number, default 50) | Retrieve the user's owned Steam game library with playtime statistics. | Yes | | get_recently_played | steam_id (string, optional) | Games played in the last 2 weeks. | Yes | | get_wishlist | steam_id (string, optional)sort ("priority" | "date_added" | "name")limit (number, default 50) | Retrieve the user's Steam wishlist to find interesting games. | Yes | | get_app_details | appid (number)country_code (string, default 'us') | Full Steam Store metadata for a specific game (description, genres, categories, price, metacritic). | No | | get_app_reviews | appid (number)filter ("all" | "recent" | "positive" | "negative") | Steam user review sentiment for a game. | No | | search_games | query (string)limit (number, default 10) | Resolve a game title to a Steam AppID. | No | | recommend_from_library | steam_id (string, optional)tags (string[])unplayed_only (boolean, default true)limit (number, default 10) | Find games in the user's library that match specified tags/mood. | Yes | | discover_games | tags (string[])steam_id (string, optional)max_results (number, default 20)country_code (string, default 'us') | Find well-reviewed games on Steam matching specific tags that the user does NOT own. | Optional |

Prerequisites

  • Node 18+
  • Steam account with a public library
  • Steam Web API key

Getting a Steam API Key

  1. Go to https://steamcommunity.com/dev/apikey
  2. Log in with your Steam account.
  3. Enter any domain name (e.g. localhost).
  4. Click "Register" and copy the generated 32-character API key.

Finding your Steam ID

You can use either your vanity name or your 17-digit SteamID64.

  • If your profile URL is https://steamcommunity.com/id/your_vanity_name/, your Steam ID is your_vanity_name.
  • If your profile URL is https://steamcommunity.com/profiles/76561198012345678/, your Steam ID is 76561198012345678.

Make your profile public

For the API to read your library and playtime, your Game Details privacy setting must be Public.

  1. Go to your Steam Profile -> Edit Profile -> Privacy Settings.
  2. Set "My Profile" to Public.
  3. Set "Game details" to Public.
  4. Set "Inventory" to Public if you want wishlist access.

Installation

Option A: Using npx (Recommended)

Add this to your MCP configuration JSON (mcp_config.json):

{
  "mcpServers": {
    "steam": {
      "command": "npx",
      "args": ["-y", "steam-user-mcp"],
      "env": {
        "STEAM_API_KEY": "your_api_key_here",
        "STEAM_ID": "your_vanity_name"
      }
    }
  }
}

Note: You can omit the "env" block entirely and place a .env file containing your STEAM_API_KEY and STEAM_ID in the directory where your MCP client runs.

Option B: Clone & Build

git clone https://github.com/brandikun/steam-mcp
cd steam-mcp
npm install
npm run build

Then add this to your MCP config:

{
  "mcpServers": {
    "steam": {
      "command": "node",
      "args": ["/path/to/steam-mcp/dist/index.js"],
      "env": {
        "STEAM_API_KEY": "your_api_key_here",
        "STEAM_ID": "your_vanity_name"
      }
    }
  }
}

MCP Configuration variables

  • STEAM_API_KEY (Required): Your 32-character Steam Web API key.
  • STEAM_ID (Optional): The default user to query for library and playtime tools. If not provided, it must be passed per tool call.

Usage with itad-mcp and opencritic-mcp

For the ultimate gaming assistant, combine all three:

{
  "mcpServers": {
    "steam": {
      "command": "npx",
      "args": ["-y", "steam-user-mcp"],
      "env": { "STEAM_API_KEY": "your_api_key", "STEAM_ID": "your_id" }
    },
    "itad": {
      "command": "npx",
      "args": ["-y", "itad-mcp"],
      "env": { "ITAD_API_KEY": "your_itad_key" }
    },
    "opencritic": {
      "command": "npx",
      "args": ["-y", "opencritic-mcp"],
      "env": { "RAPIDAPI_KEY": "your_rapidapi_key" }
    }
  }
}

Troubleshooting

  • "No Steam ID provided": You must set STEAM_ID in your environment or provide it in the tool call.
  • "Steam API key is required": The STEAM_API_KEY environment variable is missing.
  • "Vanity URL not found": The Steam ID provided couldn't be resolved. Ensure it's your exact vanity name or a valid SteamID64.
  • Library returns empty: Your profile is private. See the "Make your profile public" section above.
  • Tags not matching: Steam tags are very specific. The server does its best with fuzzy matching, but if a tag isn't found, try a broader synonym (e.g., "RPG" instead of "Role-playing").

Privacy

Credentials are only read from environment variables. No data is logged or sent anywhere except Steam's own APIs.

License

MIT