Steam MCP

io.github.Playtide-studiosPublished by GitHub account Playtide-studiosv0.2.8Updated Oct 27, 2026

Steam market intelligence MCP server for game developers: app search, trends, reviews, news.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper ToolsData & Analytics

Overview

AI-generated overview

Steam market intelligence MCP server that lets an assistant search Steam apps, check player trends, reviews, store details and news for game developers.

What you can do
  • Search Steam apps and resolve game names to appids
  • Pull a one-call overview of players, reviews, price, release, genres and news
  • Read full store listings with regional pricing, platforms, DLC count and metacritic
  • Mine reviews with recency, sentiment and keyword filters plus representative quotes
  • Fetch news and patch-note digests, and player-count history with week-over-week change
  • Get a curated market digest of Steam trends, live-ops patterns and competitor notes
When to use it
Useful for game developers and community managers who want Steam answers inside an IDE or chat session instead of switching to store pages, especially for launch planning and tracking how a game is actually performing over time.
Requirements
Runs locally as a Python package installed from PyPI (pip install playtide-steam-mcp) and started over stdio; the README also describes a Node-based source install. Network access to Steam's public endpoints and to the companion backend, which defaults to the Playtide hosted beta. Optional environment variables: STEAM_MCP_BACKEND_URL, STEAM_MCP_BACKEND_KEY, STEAM_MCP_TIMEOUT_MS, STEAM_MCP_REMOTE_MANIFEST, STEAM_MCP_AUTO_UPDATE, STEAM_MCP_UPDATE_ORIGIN.
Before you install
Trend and market-pulse data come from a third-party companion backend, so queries about tracked apps reach that service; the hosted beta is the default and can be pointed at a self-hosted instance. An optional backend API key can be supplied via STEAM_MCP_BACKEND_KEY. The server checks a vendor update channel at boot unless STEAM_MCP_AUTO_UPDATE is set to 0, and can be told to fetch tool descriptions from the backend via STEAM_MCP_REMOTE_MANIFEST. Reviews and news text is untrusted internet…

Installation

In SourceWeft

  1. Open Steam MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

steam-mcp

Steam market intelligence for AI agents — an MCP server that gives your coding assistant live Steam data: app search, player-count trends, store details, review mining, and news digests.

Built for game developers and community managers who want Steam answers inside their IDE conversation instead of tab-switching to store pages.

Why

Steam's public APIs are fragmented (store search, appdetails, user stats) and none of them keep player-count history — the single most useful signal for launch planning. steam-mcp stitches the surfaces together behind one tool set and pairs them with a companion backend that snapshots player counts every 30 minutes, so your agent can answer "how is the game actually doing" with real numbers.

Install

bash
# from PyPIpip install playtide-steam-mcpsteam-mcp

or from source:

bash
git clone https://github.com/Playtide-studios/steam-mcp.gitcd steam-mcpnpm installnpm start

Requires Node 26+. Zero runtime dependencies — the server talks plain HTTP/JSON-RPC over stdio.

Tools

ToolWhat it does
steam_search_appsResolve a game name to appids via Steam store search
steam_get_app_overviewOne-call health check: players, reviews, price, release, genres, latest news
steam_get_store_detailsFull store listing: pricing per region, platforms, DLC count, metacritic
steam_get_app_reviewsReview mining with recency/sentiment/keyword filters + representative quotes
steam_get_game_newsNews and patch-note digests, summary or full text
steam_get_player_trendPlayer-count history with min/max/avg, week-over-week change, and a plain-language insight line
steam_get_market_pulseCurated market digest for game developers: Steam trends, live-ops patterns, competitor notes

Client configuration

stdio (Claude Desktop / Cursor / any MCP client):

json
{  "mcpServers": {    "steam": {      "command": "node",      "args": ["/path/to/steam-mcp/src/index.ts"]    }  }}

Streamable HTTP:

bash
npm run start:http   # serves MCP on http://localhost:8788/mcp

Ready-to-edit client configs live in examples/.

Configuration

VariableDefaultPurpose
STEAM_MCP_BACKEND_URLhttps://api.playtide.devCompanion backend base URL — hosted beta by default; override to self-host. Must be https:// unless loopback
STEAM_MCP_BACKEND_KEY—Backend API key (optional; the hosted beta is open)
STEAM_MCP_REMOTE_MANIFEST0Opt in to fetching tool descriptions from the backend each boot
STEAM_MCP_TIMEOUT_MS10000Per-request timeout to Steam or the backend

Everything else is zero-config: tool schemas are pinned to the packaged manifest (see src/fallback-manifest.json).

Data provenance & safety

  • Store search, details, reviews, and news come directly from Steam's public endpoints at request time — nothing is scraped ahead or cached on disk.
  • Trends and the market digest come from the companion backend.
  • All free-text fetched from the internet (reviews, news bodies) is treated as data, never instructions — tool descriptions tell the model the same.
  • The server sends no telemetry anywhere. The only outbound calls are the Steam endpoints you asked about and the backend you configured.

The companion backend

Trend and pulse data come from the steam-mcp companion backend — a small Express + Postgres service that snapshots player counts for every tracked app every 30 minutes.

  • Hosted backend (open beta — the default): installs use https://api.playtide.dev out of the box; no key needed during beta. To pin it explicitly:

    bash
    STEAM_MCP_BACKEND_URL=https://api.playtide.dev npm start

  • Self-hosted: the backend is a standard docker-compose Postgres + API stack; set STEAM_MCP_BACKEND_URL to your instance. See docs/TROUBLESHOOTING.md for connectivity help.

Troubleshooting

Backend unreachable, HTTPS requirement errors, deprecated_client on trend calls, rate limits — see docs/TROUBLESHOOTING.md.

Contributing

Issues and PRs are welcome — see CONTRIBUTING.md. Bug reports that include the failing tool call JSON get fixed first.

License

MIT © Playtide Studios. Steam is a trademark of Valve Corporation; this project is not affiliated with Valve.

Source: README.md at commit b00584b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.8LatestOct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts