Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Read-only Steam: friends, games, achievements, sales, plus game recommendations and co-op nights.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
STEAM_API_KEY, STEAM_USER, STEAM_MCP_TOOLSLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
claude mcp add steam --env STEAM_API_KEY=your-value --env STEAM_USER=your-value --env STEAM_MCP_TOOLS=your-value -- uvx steam-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"steam": {
"command": "uvx",
"args": [
"steam-mcp"
],
"env": {
"STEAM_API_KEY": "your-value",
"STEAM_USER": "your-value",
"STEAM_MCP_TOOLS": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"steam": {
"type": "stdio",
"command": "uvx",
"args": [
"steam-mcp"
],
"env": {
"STEAM_API_KEY": "your-value",
"STEAM_USER": "your-value",
"STEAM_MCP_TOOLS": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
STEAM_USER envSTEAM_MCP_TOOLS envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub Sarg338, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: STEAM_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.19.0) llegó al registro hace 44 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv), MCPB en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Signoff
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo