A
licenseA
qualityC
maintenanceEnables AI agents to audit Steam store pages for algorithmic health, forecast sales cones with P10/P50/P90 scenarios, and retrieve genre benchmarks for indie game market analysis.
3
MIT
Steamworks Release Assistant
by wazzapsenk
Related Servers
Alternatives to Steamworks Release Assistant
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven control of Godot 4 for scene manipulation, 3D import, procedural textures, deterministic playtesting, game generation, and publishing to itch.io and Steam.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to research Steam games by fetching regional prices, reviews, current player counts, store charts, and news through public endpoints without an API key.MIT
Sprixen MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to create style-locked game projects and generate sprites, animations, tiles, maps, music, 3D models, and VFX, then export engine-ready packages for Godot, Phaser, Unity, GameMaker, or RPG Maker MZ.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to recommend Steam games from natural language by searching games, finding similar titles, filtering by tags and platform, and retrieving detailed game metadata.1MIT
glade-mcpofficial
AlicenseNot gradedqualityAmaintenanceConnect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot. 300+ granular tools, an editor aware system prompt, game design document project context, script semantic search, and skill calibration.225MIT
TDQS
A3.7/5.0
Scored across 35 tools
Disambiguation4/5
Most tools occupy clearly distinct phases of the pipeline (scan, interview, generate, validate, export, apply), and names like study_market/save_market_study vs study_reviews/save_review_study pair up predictably. The main overlap is among public-data readers - fetch_reference, store_lookup, study_market, compare_games - which all pull cached Steam data and could be confused, though the descriptions do differentiate them. A couple of general-purpose tools (apply, mark_applied, set_field) also sit near each other but are separated by intent.
Naming Consistency4/5
Nearly everything is lower_snake_case with a verb_noun shape (scan_project, set_field, save_draft, save_market_study, localization_set, export_package). A handful of bare nouns/generics (status, generate, validate, apply, server_info, integration_code) deviate from the verb_noun pattern but remain readable and consistent in casing. No mixed camelCase/snake_case chaos.
Tool Count3/5
35 tools is heavy and would normally suggest over-fragmentation, but the domain (store text, achievements, builds, localization, market/review studies, validation, exports, apply) genuinely spans many distinct phases. Still, some pairs (study_market/save_market_study, study_reviews/save_review_study, fetch_reference/store_lookup) could plausibly be consolidated, pushing this into borderline-heavy territory.
Completeness5/5
The surface covers a full release lifecycle: init/scan, guided interview, drafting, validation, code and build checks, image preparation, localization, market/review studies, Steamworks read/write via apply/import/set_build_live, and manual export packages. Read and write paths exist on both sides (steamworks_inspect vs apply, import_from_steamworks), and the deliberate omission of a publish action is explained, leaving no obvious dead ends.