SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Put a game on Steam: store page, achievements, Valve-rule checks, market data, Steamworks.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 29/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 41/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Steamworks Release Assistant。按照 https://mcp.popnx.com/i/wazzapsenk-steamworks-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Steamworks Release Assistant,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "steamworks": { "command": "uvx", "args": [ "steamworks-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Steamworks Release Assistant 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"steamworks": {
"command": "uvx",
"args": [
"steamworks-mcp"
]
}
}
}用 Steamworks Release Assistant 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Steamworks Release Assistant,或回答中出现 Steamworks Release Assistant 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
STEAMWORKS_MCP_ROOT 存放您游戏项目的文件夹。默认值:应用启动服务器时所在的文件夹。 STEAMWORKS_PUBLISHER_KEY 可选的 Steamworks 发行商 Web API 密钥,仅用于构建、测试分支和排行榜。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Steamworks Release Assistant
Steamworks Release Assistant 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Steamworks Release Assistant 的应用
B · 会计、财务与税务 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Steamworks Release Assistant,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user steamworks -- uvx steamworks-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Steamworks Release Assistant 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user steamworks -- uvx steamworks-mcp应能看到 Steamworks Release Assistant 在列表中并显示已连接
用 Steamworks Release Assistant 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Steamworks Release Assistant,或回答中出现 Steamworks Release Assistant 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
STEAMWORKS_MCP_ROOT 存放您游戏项目的文件夹。默认值:应用启动服务器时所在的文件夹。 STEAMWORKS_PUBLISHER_KEY 可选的 Steamworks 发行商 Web API 密钥,仅用于构建、测试分支和排行榜。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Steamworks Release Assistant,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "steamworks": { "command": "uvx", "args": [ "steamworks-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Steamworks Release Assistant 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Steamworks Release Assistant 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Steamworks Release Assistant,或回答中出现 Steamworks Release Assistant 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
STEAMWORKS_MCP_ROOT 存放您游戏项目的文件夹。默认值:应用启动服务器时所在的文件夹。 STEAMWORKS_PUBLISHER_KEY 可选的 Steamworks 发行商 Web API 密钥,仅用于构建、测试分支和排行榜。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Steamworks Release Assistant,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "steamworks": { "type": "stdio", "command": "uvx", "args": [ "steamworks-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Steamworks Release Assistant 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Steamworks Release Assistant 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Steamworks Release Assistant,或回答中出现 Steamworks Release Assistant 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
STEAMWORKS_MCP_ROOT 存放您游戏项目的文件夹。默认值:应用启动服务器时所在的文件夹。 STEAMWORKS_PUBLISHER_KEY 可选的 Steamworks 发行商 Web API 密钥,仅用于构建、测试分支和排行榜。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user steamworks -- uvx steamworks-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"steamworks": {
"command": "uvx",
"args": [
"steamworks-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"steamworks": {
"command": "uvx",
"args": [
"steamworks-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"steamworks": {
"type": "stdio",
"command": "uvx",
"args": [
"steamworks-mcp"
]
}
}
}STEAMWORKS_MCP_ROOT envSTEAMWORKS_PUBLISHER_KEY 机密 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 wazzapsenk 验证,该账户拥有此仓库
代码最后更新于15天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 steamworks-mcp@0.5.2 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/wazzapsenk-steamworks-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于15天前,最新版本(0.5.2)于15天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| 本项 Steamworks Release Assistant | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
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).
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:
| Transport | For | Started by |
|---|---|---|
| stdio (the default) | Apps that start the server on your computer: Claude Desktop, Claude Code, Codex (app, CLI, IDE extension) | the app itself (steamworks-mcp); setup and the plugin configure it |
| Streamable HTTP | Apps that connect over the internet: ChatGPT (web and desktop app), claude.ai | steamworks-mcp remote (with a secure address), or steamworks-mcp --http (local only, details) |
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.
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.
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.
These apps reach the server over the internet, through a secure address on your computer.
winget install --id Cloudflare.cloudflared; on a Mac: brew install cloudflared. 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.
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.
uvx steamworks-mcp setup
Codex?, answer y. If it says "not found", Codex has not run on this computer yet; y still works.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.
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.
Just talk to your assistant. Some things you can say:
| You want to… | Say |
|---|---|
| Start | "Where are my games on Steam?" · "Help me get my game in MyGame/ onto Steam." |
| See what's left | "What's still missing before my store page can go live?" |
| Store page | "Write my store page." · "Make my short description better." |
| Know the market | "What do the closest popular games do on their store pages?" · "Compare my game with games like it." |
| Price | "What should my game cost, and in each country?" |
| Achievements | "Design achievements for my game." · "Add the Steam code for them." |
| Check the code | "Check my game's Steam integration." |
| Images | "Make all my store images from my key art and logo." |
| Translations | "Translate my store page into German, French and Japanese." |
| Fill Steamworks | "Show me what would change in Steamworks, then apply it." |
| After launch | "How is my launch going?" · "What are players complaining about?" |
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.
| Word | Means |
|---|---|
| MCP server | A helper program your AI app talks to. This project is one. |
| Tool | One thing the server can do, like "check my code" or "make my images". Your assistant picks the tools. |
| Skill | A ready-made recipe for your assistant, like "write the store page" (several tools in the right order). |
| Prompt | The same as a skill, for apps that show prompts instead of skills. |
| Code rule | A check of your game's code against Steamworks requirements, with the fix. |
| steamworks.yaml | The file in your game folder with every Steam setting of your game. Readable and editable. |
| Draft / approved / done | A value found or written for you / a value you confirmed / a value Steamworks has. |
| Needs review | A value that changed after you approved it (or whose source text changed); approve it again. |
| Release step | Step 0-3 above (in the code: "gate"). |
| Dry run | Showing what would change in Steamworks without changing anything. Every write starts with one. |
| BROWSER mode | Optional: the tool fills Steamworks pages in a browser window you signed in to yourself. |
| Publisher key | Optional: a Steamworks key for builds, branches and leaderboards. Never share it. |
| App id | Your game's number on Steam (Steamworks > App Admin), e.g. 480. |
| Capsule | One of the store images: the boxes your game appears in on Steam's pages and lists. |
| Library assets | The images in the player's Steam library: hero (wide background), logo, header, capsule. |
| Tags / genres / categories | Tags are the words players search by; genres are Steam's broad types (Action, Indie); categories are features (Single-player, Online Co-op, Steam Cloud). |
| Depot | The container your game files are uploaded into; a build is one upload of your depots. |
| Launch option | The file Steam starts when a player presses Play. |
| Redistributables | Runtimes Steam installs with your game, like Visual C++ or DirectX. Unity and Godot games usually need none. |
| Content Survey | Valve's questionnaire about mature content and AI use, in Steamworks; required before review. |
| Steam Direct | Valve's per-game fee you pay before releasing; release comes at least 21 days later. |
Start and see where you are
| What | Tools |
|---|---|
| Find your games and show how far each one is, with the one next step | status |
| Start tracking a game and read what the project already says (Unity, Godot, Unreal) | init_project, scan_project |
| Game already in Steamworks? Fill the empty fields from what Steam has; never overwrites | import_from_steamworks |
| What is missing before each release step, with Valve's source for every rule | gap_report |
| Short batches of questions (a form when your app supports it), saving and approving answers | start_interview, set_field, approve_fields, mark_applied |
| What is turned on (keys, modes), reference data | server_info, get_spec_info |
Store page, images and translations
| What | Tools |
|---|---|
| Briefs for the store text, achievements and settings; your assistant writes, the server checks | generate, save_draft |
| Check everything against Valve's rules, a store-text rubric and an anti-copy check | validate |
| Preview the store text with the first screen marked | preview_store |
| Every store, library and icon image from one key art and one logo | prepare_images |
| Translate every text into every target language (your assistant translates, the server checks) | localization_status, localization_pending, localization_set |
| Measure a successful game's page (numbers only) | fetch_reference |
Market (live data from Steam's public store)
| What | Tools |
|---|---|
| Look any game up: price, reviews, players right now, features | store_lookup |
| Study the closest popular games' store pages, compare them side by side | study_market, save_market_study, compare_games |
| What close games charge in the US and in each country | price_brief |
| Rough sales from revi