Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Read-only Steam: friends, games, achievements, sales, plus game recommendations and co-op nights.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
STEAM_API_KEY, STEAM_USER, STEAM_MCP_TOOLSAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
claude mcp add steam --env STEAM_API_KEY=your-value --env STEAM_USER=your-value --env STEAM_MCP_TOOLS=your-value -- uvx steam-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"steam": {
"command": "uvx",
"args": [
"steam-mcp"
],
"env": {
"STEAM_API_KEY": "your-value",
"STEAM_USER": "your-value",
"STEAM_MCP_TOOLS": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"steam": {
"type": "stdio",
"command": "uvx",
"args": [
"steam-mcp"
],
"env": {
"STEAM_API_KEY": "your-value",
"STEAM_USER": "your-value",
"STEAM_MCP_TOOLS": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
STEAM_USER envSTEAM_MCP_TOOLS envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Sarg338 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: STEAM_API_KEY
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.19.0) kam vor 44 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv), MCPB auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Dialyne
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
Install uv, then:
Claude Code
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.
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:
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 useronly 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.
Account / profile (needs a public profile; set STEAM_USER and "my"/"I" default to you — no SteamID needed):
Account-independent (works for any game, no SteamID needed):
| 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, andsteam_recommendneed no key for
the store data; their personalization (passing a
steamidto use a user's
library/taste) requires a key and a public profile.
†
steam_get_inventoryreads 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.
Beyond tools, the server ships prompts (guided one-click flows that orchestrate the tools) and resources (reference Steam entities by URI):
what_should_i_play, is_it_worth_buying, plan_game_night, steam_deals, game_overview.steam://app/{appid} (store details) and steam://user/{steamid} (profile + live status).Recent reviews:
steam_get_app_reviewswithreview_filter='recent'asks
Steam for the exact review count and score of the last
day_rangedays (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 resultsampled: 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_priceuses 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.
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 https://steamcommunity.com/dev/apikey, 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.
The published package needs no checkout (Python 3.10+):
uvx steam-mcp # zero-install via uv (recommended)
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
Nur der Anfang wird gezeigt; den Rest findest du im Repo