Steam MCP Server
Related Servers
Alternatives to Steam MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Steam that enables LLM agents to manage gaming libraries, achievements, stats, and discover store content through 20 tools.213MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to search Steam games by keyword, retrieve game details (price, release date, genres), and fetch player reviews with recent ratings.-
- AlicenseAqualityBmaintenanceMCP server enabling AI assistants to search Steam games, retrieve official store metadata, and analyze player review sentiment via public Steam Storefront JSON APIs without an API key.36 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Valve's Steam that enables querying game libraries, player profiles, achievements, friends, store listings, Workshop items, and current player counts. Provides 14 tools across 5 categories with a React dashboard and REST bridge.141MIT

SteamGPTofficial
AlicenseNot gradedqualityBmaintenanceMCP server for Steam data, backed by steamgpt.net - a free Steam data API for AI agents. Steam profiles, SteamID conversion, VAC / game / community / trade bans, FACEIT stats, public friend graph, batch lookups and player comparison. No API key, no registration, no tracking.5 npmMIT- FlicenseNot gradedqualityBmaintenanceA read-only MCP server that enables AI assistants to access a user's Steam library, playtime, achievements, friends, wishlist, and store data for backlog analysis, game recommendations, discount monitoring, and play-activity summaries.-
TDQS
Scored across 26 tools
Most tools are distinct by resource (achievements, workshop, leaderboards, store data), but there is some overlap: steam_getReviews vs steam_getAppReviewSummary vs steam_getAppDetails all return review-related data, and steam_getPriceOverview vs steam_getRegionalPricing both provide pricing. The mutation tools are clearly marked, but the read tools for reviews/pricing could be confused.
The tools follow a consistent steam_verbNoun pattern (e.g., steam_getReviews, steam_createLobby, steam_uploadWorkshopItem). Minor deviations include steam_resolveVanityURL (camelCase in the noun) and steam_validateStoreAsset (verb+noun but no direct resource prefix), but overall the pattern is predictable.
26 tools is on the high end for a single server, but Steam is a large platform with many distinct domains (store, player, achievements, workshop, leaderboards, pricing). The count is borderline heavy; some tools like steam_createLobby and steam_uploadWorkshopItem are documentation/code-sample tools rather than API operations, which inflates the count.
The server covers a broad range of Steam domains: store browsing, app details, reviews, pricing, player profiles, owned games, achievements, workshop, leaderboards, and news. Obvious gaps include no tool for searching players by name, no friend list access, and no way to update/delete workshop items beyond metadata (though that's an SDK limitation). Overall, the surface is fairly complete for common Steam API use cases.