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 分