Steam Mcp

MCP开发工具

提供方 Sarg338 · 包名 steam-mcp

开发工具 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

Read-only Steam MCP server for AI agents: 37 tools + prompts + resources across library, friends, achievements, store, reviews, sales, discovery, recommendations, and co-op planning. Official Steam Web API, bring-your-own-key, open source. On PyPI + the MCP Registry.

一句话选型结论

按资料字段整理

Steam Mcp 属于开发工具类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

steam gaming games reviews deals pricing inventory read only

支持客户端

适用场景

steamgaminggames

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
uvx steam-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Steam Mcp当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Sarg338上游标注的维护方 Sarg338
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时steam-mcp · python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

15.3 KB
来自项目仓库与上游目录的原文,未做删改

Steam MCP

A read-only Model Context Protocol server for the
public Steam Web API and storefront — 41 tools, 5 prompts, and 2 resources that let
any MCP client (Claude Desktop, Claude Code, Cursor, …) answer questions about Steam:
your friends, games, playtime, and achievements, plus account-independent things like
sales, reviews, live player counts, Steam Deck compatibility, discovery,
recommendations, and co-op planning.

Read-only · official Steam APIs only · open source. Nobody logs in, and the server
never writes, trades, posts, launches games, or makes purchases.

Quick start — no API key needed

Install uv, then:

Claude Code```bash
claude mcp add steam -- uvx steam-mcp


That's the whole setup. **19 of the 41 tools work with no credential at all** — anything
about the store or a game itself:

> *"Is Baldur's Gate 3 worth buying, and how are its recent reviews trending?"*
> *"What co-op games are on sale under £20 right now?"*
> *"How many people are playing Helldivers 2 this minute?"*
> *"Will Hades II run properly on my Steam Deck?"*

The three game-finders (`steam_discover`, `steam_should_i_buy`, `steam_recommend`) work
without a key too, as long as you don't personalize them.

### Adding your own account

A free Steam Web API key (a minute to get)
unlocks the other 22 — the ones that read a *specific account*: library, playtime,
friends, achievements, wishlist, inventory. Add `STEAM_USER` too and "my"/"I" default to
you, so you never have to paste a SteamID:```bash
claude mcp add steam --env STEAM_API_KEY=YOUR_KEY --env STEAM_USER=your_steam_name -- uvx steam-mcp

> Tip: this defaults to the current project. Add --scope user only if you want
> Steam in every project — that keeps its tools in context everywhere, so prefer
> per-project scope unless Steam is cross-cutting for you.

Claude Desktop — download steam-mcp.mcpb from the
latest release and open it
(Settings → Extensions). Both fields are optional; leave them blank for the keyless
tools and fill them in later.

Cursor / Cline / Windsurf and the manual pip setup are under Setup below.

> Without a key, the account tools are still listed but marked
> [unavailable: needs STEAM_API_KEY], so your assistant knows to reach for a keyless
> tool instead of failing at one it can't use.


What it can answer

Account / profile (needs a public profile; set STEAM_USER and "my"/"I" default
to you — no SteamID needed):
- "Who's on my friends list, and who's online right now?"
- "Which of my friends own Helldivers 2 — and who's playing it now?"
- "It's game night — what co-op games do my online friends and I all own?"
- "Analyze my library — my backlog, and what I loved but abandoned."
- "Which achievements am I missing in Hollow Knight, and which are my rarest?"
- "What's on my wishlist, and is any of it on sale?"
- "Based on what I play most, what should I check out next?"
- "What's in my CS2 inventory, and which items are marketable?"

Account-independent (works for any game, no SteamID needed):
- "Is Baldur's Gate 3 worth buying — and how are its recent reviews trending?"
- "What's on sale right now, and what are the current top sellers?"
- "How many people are playing Counter-Strike 2 this minute?"
- "Will Hades II run on my Steam Deck?"
- "What's the Community Market price of a Field-Tested AK-47 | Redline?"
- "Is Elden Ring a soulslike? What are its community tags?"
- "Find well-reviewed co-op roguelikes under $20."
- "Recommend games like Hollow Knight that I don't already own."


Tools

Tool What it returns Needs key?
steam_resolve_vanity_url Vanity name / profile URL → SteamID64 yes
steam_get_player_summary Status (Online/Away/In-Game…), current game, for 1–100 users yes
steam_get_friend_list Friends enriched with name + live status yes
steam_find_friends_who_own Which friends own (or are playing) a game — "who can I play X with" yes
steam_get_user_groups The Steam groups/clans a user is in (name, URL, member count) yes
steam_plan_coop_night Co-op games the host + friends all own (ranked by owners) — or mode="new" for fresh co-op games none of them own yet; with who's online now yes
steam_get_owned_games Owned games with total/recent hours (sortable) yes
steam_analyze_library Backlog, playtime distribution, abandoned games across a whole library yes
steam_get_recently_played_games Last-2-weeks playtime yes
steam_get_steam_level Steam community level yes
steam_get_player_bans VAC / game / community / economy bans yes
steam_get_player_achievements Per-game unlocked vs locked achievements yes
steam_get_game_schema A game's achievement definitions (names, descriptions, hidden flag) yes
steam_get_global_achievement_percentages Achievement rarity (global %) no
steam_get_user_game_stats A user's in-game stats (kills, wins, distance…) for a game yes
steam_get_rarest_unlocks A player's rarest achievement unlocks in a game (by global rarity) yes
steam_search_apps Game title → appid (+ price) no
steam_discover Find/recommend games by tag, price, sale, platform, release window ("last N days") — optionally personalized to a user's taste (excludes games they own) no*
steam_should_i_buy Buying brief — price, lifetime + recent reviews (trend), tags, Metacritic, and your taste match no*
steam_recommend Recommend games like a seed game or your taste, with the shared tags as the "why" no*
steam_get_app_details Full store details — play modes/co-op, controller, DLC, languages, requirements, Metacritic, Steam Deck no
steam_get_deck_compatibility Steam Deck rating (Verified/Playable/Unsupported) + the per-criterion test results no
steam_get_dlc A game's DLC, with live prices and what's on sale no
steam_get_app_regional_pricing A game's price across regions (each in local currency) no
steam_get_workshop_item Workshop item metadata (game, tags, subscribers, favorites, views) no
steam_get_app_tags A game's top community tags (Souls-like, Roguelike, Cozy…) no
steam_get_app_reviews Lifetime verdict, +/- counts, sample reviews; optional recent (last-N-days) score via review_filter='recent' no
steam_analyze_game One-call brief on a game: price, all-time and 30-day reviews, players now, Deck, tags, the latest update's effect on reviews, and news no
steam_compare_games Compare 2-5 games side by side: price, reviews and their trend, players now, Steam Deck, co-op, tags no
steam_get_update_impact Did an update change the reviews? Review score in the days before vs after each recent patch no
steam_analyze_app_reviews Analyze thousands of reviews: sentiment over time, by language and playtime, Steam Deck, key activations vs Steam purchases, refunds, developer replies no
steam_get_featured_specials Games currently on sale (regional) no
steam_get_store_highlights Top sellers, new releases, or coming soon no
steam_get_wishlist A user's wishlist, with live prices + what's on sale yes
steam_get_inventory A user's inventory — game items or Steam Community items (cards, emoticons…), with tradable/marketable flags yes†
steam_get_market_price Community Market price for an item (lowest/median/24h volume) + type/rarity + CS2 condition no
steam_get_player_badges Badges + the XP breakdown behind a Steam level yes
steam_get_package_details Package/bundle price + included games no
steam_compare_players Shared games between two users, with playtime yes
steam_get_current_players Live concurrent player count no
steam_get_app_news Recent news / patch notes no

Every tool supports response_format: "markdown" (default) or "json", and all are
annotated readOnlyHint: true. Prefer the composite tools (steam_should_i_buy,
steam_recommend, steam_discover, steam_plan_coop_night) over chaining several
calls, and ask for json only when you need to parse fields. Tools that read
localized text accept a language parameter — a Steam language name like french or
schinese (default english).

> * steam_discover, steam_should_i_buy, and steam_recommend need no key for
> the store data; their personalization (passing a steamid to use a user's
> library/taste) requires a key and a public profile.
>
> † steam_get_inventory reads a keyless endpoint, but it still has to know whose
> inventory — and turning a vanity name (or STEAM_USER) into a SteamID64 is itself a
> keyed call. Pass a raw 17-digit SteamID64 and it works with no key.

Prompts & resources

Beyond tools, the server ships prompts (guided one-click flows that orchestrate
the tools) and resources (reference Steam entities by URI):

  • Prompts: what_should_i_play, is_it_worth_buying, plan_game_night,
    steam_deals, game_overview.
  • Resources: steam://app/{appid} (store details) and steam://user/{steamid}
    (profile + live status).

> Recent reviews: steam_get_app_reviews with review_filter='recent' asks
> Steam for the exact review count and score of the last day_range days (default
> 30), the same numbers as the store page's "Recent Reviews" row. If Steam refuses
> that request it falls back to counting the newest reviews, up to
> recent_max_reviews, and marks the result sampled: true.
>
> Whose reviews count: by default both scores count what the store page
> counts: Steam purchases only for a paid game (key activations are left out) and
> everyone for a free game. purchase_type='all' or 'steam' forces either.

> Market prices: steam_get_market_price uses Steam's Community Market
> endpoints, which are undocumented and tightly rate-limited. Results are cached
> briefly; an item with no current listings reports its price as unavailable.


Setup

1. Get a free Steam Web API key (optional)

Skip this if you only want the 19 keyless tools — the server runs fine without a
key and the account tools simply advertise themselves as unavailable.

To unlock the account tools, visit , sign in,
register a domain (any domain you control works; localhost is commonly used for
personal keys), and copy the key. Usage is governed by the
Steam Web API Terms of Use.

2. Install

The published package needs no checkout (Python 3.10+):```bash
uvx steam-mcp # zero-install via uv (recommended)

or

pip install steam-mcp # run as: python -m steam_mcp.server


Both MCP Python SDK majors work (`mcp>=1.28`). On the v2 SDK the server speaks
spec revision 2026-07-28 — stateless, no `initialize` handshake — advertises
cache hints on its tool/prompt/resource listings, and can ask you which Steam
account is yours when `STEAM_USER` isn't set (once per session, and only if your
client supports elicitation). On the v1.x line it serves the `initialize`
handshake that modern clients fall back to anyway. Nothing to configure either
way.

> **TLS note:** the HTTP client is `httpx2`, which verifies certificates against
> your **operating system's** trust store rather than a bundled CA list. If you
> run this somewhere minimal (a slim container with no system CA store, or behind
> a private CA), point `SSL_CERT_FILE` or `SSL_CERT_DIR` at a CA bundle.

### 3. Add it to your MCP client

Both settings are optional. `STEAM_API_KEY` unlocks the account tools; `STEAM_USER`
(your Steam vanity name, SteamID64, or profile URL) makes those tools default to *you*
whenever you don't name a user, so you never paste a SteamID. It's a public profile
name, not a secret, and you can still pass a `steamid` to any call to override it.

Configure neither and you get the keyless server; configure both and you get everything.

**Smaller tool set (optional).** Every tool's definition goes into the model's context
on every request, about 11.5k tokens for all 41. Set `STEAM_MCP_TOOLS=essentials` to
load just 15: search, the one-call game brief, details, reviews, compare, should-I-buy,
discover, recommend, update impact, sales, and your profile, library, library analysis,
wishlist and co-op night. Add others by name (`essentials,get_inventory`), or list
exactly the ones you want. The default is `all`. The built-in prompts may mention a
tool your set leaves out.

**Claude Code**```bash
claude mcp add steam --env STEAM_API_KEY=YOUR_KEY --env STEAM_USER=your_steam_name -- uvx steam-mcp

> STEAM_USER is optional — drop the second --env if you'd rather give a
> SteamID to each call.

Claude Desktop — install steam-mcp.mcpb from the
latest release via
Settings → Extensions and paste your key (and, optionally, your Steam name).

Everything else (Claude Desktop config, Cursor, Cline, Windsurf, VS Code, …) —
drop this block into the client's MCP config file:json { "mcpServers": { "steam": { "command": "uvx", "args": ["steam-mcp"], "env": { "STEAM_API_KEY": "YOUR_KEY_HERE", "STEAM_USER": "your_steam_name" } } } }

Installing with an AI agent such as Cline? Point it at
llms-install.md, which walks it through the setup.

Config locations: Claude Desktop claude_desktop_config.json (%APPDATA%\Claude\
on Windows, ~/Library/Application Support/Claude/ on macOS); Cursor
.cursor/mcp.json; Cline cline_mcp_settings.json. Restart the client and the
Steam tools appear. Running from a source checkout instead? Use
"command": "python", "args": ["-m", "steam_mcp.server"].


Security

Read-only, official-Steam-only, and bring-your-own-key. In short:

  • Read-only — never writes, trades, posts, launches games, or buys anything.
  • Your key stays yours — read from STEAM_API_KEY; never written to disk,
    logged, cached, or put in output (and redacted from error messages).
  • Official hosts only — the request layer refuses any host that isn't
    api.steampowered.com / store.steampowered.com / steamcommunity.com (SSRF
    guard), with per-host rate limiting and retry/backoff.
  • Typed, validated inputs (extra="forbid"); no data kept between requests
    beyond a small TTL cache of non-user store data.

Full details and how to report issues are in SECURITY.md.


Versioning & stability

steam-mcp follows Semantic Versioning. As of 1.0, the
following are the stable public surface — they won't change without a major
(2.0) release:

  • Tool names and their input parameters (names, types, whether required,
    defaults)
  • JSON output fields (response_format: "json") — names, types, and structure
  • Prompt names/arguments and resource URI templates
    (steam://app/{appid}, steam://user/{steamid})
  • Core semantics: read-only, bring-your-own-key, prices in cents / playtime in
    minutes, and errors returned as strings

Within a major version, minor releases may add tools, prompts, resources,
optional parameters, and JSON fields; patch releases are bug fixes only. The
Markdown output wording, internal implementation, caching behavior, and which
Steam endpoints back a given tool may change at any time and are not part of
the contract.


License

MIT. Not affiliated with Valve. "Steam" is a trademark of Valve Corporation.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Steam Mcp 怎么安装?

在客户端按下面的安装命令接入:uvx steam-mcp。对应的包名是 steam-mcp。装完在客户端配置里引用同一个包或端点。

Steam Mcp 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Steam Mcp 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Steam Mcp 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Steam Mcp 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Steam Mcp 能提供哪些能力?

资料显示能力标签包括 steam、gaming、games、reviews、deals、pricing。具体工具清单以官方文档为准。

Steam Mcp 需要什么运行环境?

运行时为 python;属于本地进程,需要在本机装好运行环境。

Steam Mcp 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。