Steamworks Release Assistant

steamworks-mcp

Put your game on Steam with your AI assistant. It reads your game project, asks you what it cannot find, writes your store page with you, checks everything against Valve's rules, and fills in Steamworks only after you say yes. It never publishes anything: you press Publish.

Works with Claude (Desktop, Code and claude.ai), ChatGPT (web and desktop app) and Codex (app, CLI and IDE extension). Free and open source (MIT).

38 tools · 38 skills · 24 code rules · 128 release checks · 115 store-text rules · Unity, Godot and Unreal

Not affiliated with or endorsed by Valve. "Steam" and "Steamworks" are trademarks of Valve Corporation.

Contents: How it works · Install · Your first conversation · Words you will see · What it can do · Skills · Code rules · Safety · Troubleshooting · Known limits · Advanced setup

How it works

flowchart LR

A["Your game folder"] --> B["Scan: what the project already says"] B --> C["Questions for what is missing"] C --> D["Drafts: store text, achievements, images, settings, SDK code"] D --> E{"You approve?"} E -- "change it" --> D E -- "yes" --> F["Checks against Valve's rules"] F --> G["Files + a checklist for Steamworks"] F --> H["Fills Steamworks after a dry run and your OK"] G --> I["You press Publish in Steamworks"] H --> I

Your game goes through four release steps, the same ones Valve reviews. The tool shows how far each one is:

flowchart LR

S0["Step 0 · Prerequisites account, bank, tax, app fee"] --> S1["Step 1 · Store page texts, images, tags, languages"] S1 --> S2["Step 2 · Build review the game, Steam features"] S2 --> S3["Step 3 · Release date, price, Release button"]

Everything about your game's Steam release lives in one readable file in your game folder, steamworks.yaml. Every value in it has a status: missing, draft (found or written, not yet checked by you), approved (you said it is right), done in Steamworks, or needs review (it changed after you approved it, so you look at it again).

Install

You need uv, a small tool that runs Python programs (one command to install), and Claude, ChatGPT or Codex. You do not need Steam keys or a Steam login to start.

The server speaks both MCP transports:

Over HTTP every request needs sign-in (OAuth, or a bearer token); over stdio only the app that started the server can talk to it.

Claude Desktop

In a terminal:

uvx steamworks-mcp setup

It asks where your games are and connects Claude Desktop (and Claude Code, if you have it). Restart Claude Desktop. To use the skills there too, add the folders in skills/ as skills in Claude's settings.

Claude Code: the plugin (server and skills in one step)

In Claude Code, type:

/plugin marketplace add https://github.com/wazzapsenk/steamworks-mcp

/plugin install steamworks@steamworks-mcp

It asks for your games folder. That's it.

ChatGPT (web or desktop app) and claude.ai

These apps reach the server over the internet, through a secure address on your computer.

1. Install cloudflared once (free, from Cloudflare). On Windows: winget install --id Cloudflare.cloudflared; on a Mac: brew install cloudflared.
2. In a terminal:

   uvx steamworks-mcp remote

The first time, it asks where your games are. Then it prints an address that ends in /mcp and an access code.

1. Add the address in your app, with OAuth as the authentication:

• ChatGPT on the web: Settings > Apps & Connectors > Advanced settings: turn on Developer mode, then create a connector.
• ChatGPT desktop app (Windows, macOS): Settings > Plugins > MCPs > Add.
• claude.ai: Settings > Connectors > Add custom connector.

1. A steamworks-mcp page opens and asks for the access code: type the one from step 2.
2. Ask your assistant: "Where are my games on Steam?"

Keep the terminal from step 2 open while you work. Custom connectors in ChatGPT need developer mode; check that your plan has it. The address changes every time you start remote (update the connector's URL then); a fixed address needs a little more setup.

Codex (app, CLI and IDE extension)

1. In a terminal (the same command as for Claude Desktop):

   uvx steamworks-mcp setup

1. Type the folder that holds your games (Enter keeps the one shown). The keys it offers are optional: Enter skips them.
2. When it asks Codex?, answer y. If it says "not found", Codex has not run on this computer yet; y still works.
3. Restart Codex (the app, or a new CLI session) and ask: "Where are my games on Steam?"

The server goes into ~/.codex/config.toml, which the Codex app, the CLI and the IDE extension all read, so one setup covers all three. Codex starts the server on your computer: no tunnel and no access code. Tools that only read run without asking; Codex asks before every tool that changes something.

Check the installation

uvx steamworks-mcp doctor

It lists what is set up and what to fix; Troubleshooting covers the common problems. Other apps that support MCP, and connecting by hand: docs/ADVANCED.md.

Your first conversation

Just talk to your assistant. Some things you can say:

Every answer starts with one plain sentence and, where it helps, a table. The assistant shows you each draft; only you approve.

For a new game the assistant first asks you to describe it in a few sentences, then shows what it understood in one list for you to confirm. The questions after that come a few at a time; the optional ones you can skip, and "not yet" is always a fine answer.

Words you will see

What it can do

Start and see where you are

Store page, images and translations

Market (live data from Steam's public store)

| Rough sales from revi