Steam MCP

io.github.Playtide-studios由 GitHub 帳號 Playtide-studios 發布v0.2.8更新於 Oct 27, 2026

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

概覽

AI 產生的概覽

Steam 市場情報 MCP 伺服器,讓助理搜尋 Steam 應用程式、查看玩家趨勢、評論、商店詳情與新聞,面向遊戲開發者。

可以做什麼
  • 搜尋 Steam 應用程式,將遊戲名稱解析為 appid
  • 一次呼叫取得玩家數、評論、價格、發行、類型與最新新聞概覽
  • 讀取完整商店資訊,含分區定價、平台、DLC 數量與 metacritic
  • 依時間、情緒與關鍵字篩選挖掘評論,並附代表性引文
  • 取得新聞與更新說明摘要,以及含週對週變化的玩家數歷史
  • 取得面向開發者的市場簡報,含 Steam 趨勢、營運模式與競品動態
適用情境
適合遊戲開發者與社群經營者,希望在 IDE 或對話中直接取得 Steam 答案而不必切換商店頁面,特別用於發行規劃與長期追蹤遊戲實際表現。
執行需求
以本機程序執行,從 PyPI 安裝 Python 套件(pip install playtide-steam-mcp)並透過 stdio 啟動;README 另提供以 Node 為基礎的原始碼安裝方式。需能連線 Steam 公開端點與配套後端,後端預設指向 Playtide 託管測試版。選用環境變數:STEAM_MCP_BACKEND_URL、STEAM_MCP_BACKEND_KEY、STEAM_MCP_TIMEOUT_MS、STEAM_MCP_REMOTE_MANIFEST、STEAM_MCP_AUTO_UPDATE、STEAM_MCP_UPDATE_ORIGIN。
安裝前請注意
趨勢與市場簡報資料來自第三方配套後端,因此關於被追蹤應用程式的查詢會送往該服務;預設使用託管測試版,也可改為自架實例。可透過 STEAM_MCP_BACKEND_KEY 提供選用的後端 API 金鑰。除非將 STEAM_MCP_AUTO_UPDATE 設為 0,否則啟動時會檢查廠商更新通道;透過 STEAM_MCP_REMOTE_MANIFEST 可讓伺服器從後端取得工具描述。評論與新聞文字屬於不可信的網路內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Steam MCP,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 b00584b

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.8最新Oct 13, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分