mcp-server-steam
Related Servers
Alternatives to mcp-server-steam
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables interaction with Steam: search games, get store details, reviews, prices, discounts, news, and player profiles, libraries, and achievements via the Steam Web API.25128 npm4MIT
- AlicenseBqualityCmaintenanceProvides tools for interacting with the Steam Web API to access player profiles, game libraries, achievements, statistics, inventories, and game information through natural language.3458 npm5MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to query Steam profiles, libraries, achievements, store data, and reviews via the Steam Web API.152MIT
- AlicenseNot gradedqualityDmaintenanceProvides Steam Web API integration for querying owned games, player achievements, app news, and store details. Part of the Pipeworx MCP gateway enabling natural language queries to Steam data.3 npmMIT
- AlicenseAqualityBmaintenanceExposes Steam Web API tools as MCP resources for Claude Code, Claude Desktop, and Gemini CLI, enabling profile lookups, game searches, achievement tracking, and more.1110 npm1MIT
- AlicenseAqualityAmaintenanceEnables Claude Desktop and Claude Code to access Steam Web API data locally over stdio, including player profiles, owned games, achievements, friend activity, and game news.1534 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct resource/action: profile, friends, games, achievements, store details, news, workshop, reviews, bans, and vanity URL resolution. Even similar tools like get_owned_games vs get_recently_played_games are clearly differentiated by scope (all vs recent).
All tool names use snake_case with a verb_noun pattern, predominantly 'get_*' (e.g., get_user_profile, get_friends_list). The two exceptions, search_games and resolve_vanity_url, still follow verb_noun and are semantically distinct, so the overall convention is consistent and predictable.
With 16 tools, the count is slightly above the typical 3-15 sweet spot, but each tool maps to a real Steam Web API endpoint and the coverage is broad, so it does not feel bloated. The slight excess is justified by the platform's feature set.
The set covers major Steam data domains: user profiles, friends, games, achievements, store info, news, workshop, reviews, and bans. Minor gaps exist (e.g., no user game stats or DLC listing), but these are edge cases; core read workflows are well represented.