steamworks-mcp

Purpose: Managing Steam game releases, store content, achievements, compliance checks, and market data across Steamworks workflows.

Inferred · not functionally tested

Audience: Steam game developers and publishers

Inferred · not functionally tested

Functions: workflow_automation, data_extraction

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, steamworks-mcp takes a focused approach. Inferred · not functionally tested: It focuses on managing Steam game releases, store content, achievements, compliance checks, and market data across Steamworks workflows. Inferred · not functionally tested: steamworks-mcp is an open-source project aimed at steam game developers and publishers. Basis unknown · not verified: steamworks-mcp is open source under the MIT license. Basis unknown · not verified: steamworks-mcp is available on the command line, and it can be self-hosted.

It is developed by wazzapsenk, and it first shipped in 2026. Development happens publicly on GitHub with 63 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are store page management, achievement management, and valve rule checks. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.