Log inSubmit server
Steam logo

Steam

Access Steam profiles, games, achievements, news, store details, and player counts through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Steam

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "steam": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-steam"
      ],
      "env": {
        "PLATFORM_STEAM_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 14 tools correctly (6d ago).

Overview

The Steam MCP server exposes Steam Web API and Steam Store data through tools for profiles, games, achievements, news, and player counts. It can run locally over stdio with the `@pipeworx/mcp-steam` package or through the Pipeworx gateway over MCP or HTTP. Use it when an agent needs to look up public Steam data, inspect a player's library, or retrieve current game activity. A Steam API key is supplied through the platform configuration or a request parameter.

Use cases

  • Resolve Steam vanity names to numeric IDs
  • Inspect a player's library and recent games
  • Retrieve achievements and game statistics
  • Read Steam app news and store details
  • Check current concurrent player counts

Key features

  • Steam profile and friend lookups
  • Owned and recently played game data
  • Achievements, stats, levels, and bans
  • App news and store details
  • Current player counts
  • Local stdio and hosted MCP modes

Tools14

What Steam lets your agent do. Expand a tool for its parameters.

Verified live~686 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 46d

What it can do

From the 14 tools this server returned when we ran it.

Makes network requests · 3Read-only tools · 14
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age150 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-steam (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads472Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Steam works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Steam

Steam is an MCP server that connects AI agents to the Steam Web API and Steam Store API. Its main tools resolve vanity URLs, inspect profiles, friends, games, achievements, stats, bans, news, app details, app lists, and current player counts. It supports gateway or local stdio use.

Install it locally by configuring your MCP client to run `npx -y @pipeworx/mcp-steam`. This starts the package as a stdio MCP server and does not require a Pipeworx account. You can instead configure the hosted endpoint at `https://gateway.pipeworx.io/steam/mcp`.

It uses a Steam API key supplied as `PLATFORM_STEAM_KEY` or through the `_apiKey` request parameter.

Yes, Cursor is named as a supported MCP client in the setup instructions. Add the hosted Steam MCP endpoint to Cursor, or configure Cursor to launch the local `npx -y @pipeworx/mcp-steam` command.

Related MCP servers

All in Gaming All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSteam AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/steam?style=directory)](https://allmcps.com/mcp/steam)
HTML Embed
<a href="https://allmcps.com/mcp/steam"><img src="https://allmcps.com/api/badge/steam?style=directory" alt="Steam on AllMCPs" /></a>