forge vs Steamworks Release Assistant
forge is a plugin bundle for AI coding tools published by Tyler Technologies. Marketplaces we read that list it: 2 (Community GitHub marketplaces, npm registry (MCP servers)). Steamworks Release Assistant is an MCP server published by wazzapsenk. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Steamworks Release Assistant | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 1.4.0 Downloads/month (npm): 1 683 Downloads/week (npm): 1 065 Forks (GitHub): 38 Stars (GitHub): 74 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.2 Downloads/month (PyPI): 274 Downloads/week (PyPI): 1 276 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.5.2 Downloads/month (PyPI): 274 Downloads/week (PyPI): 1 276 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | forge | Steamworks Release Assistant |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 74 (better) | 13 (worse) |
| Forks (GitHub) (differs) | 38 (better) | 0 (worse) |
| Last release (differs) | 2026-10-29 (worse) | 2026-11-05 (better) |
| Where it runs (differs) | On your machine (@tylertech/forge-mcp) | On your machine (steamworks-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/tyler-technologies-oss/forge | github.com/wazzapsenk/steamworks-mcp |
| Changes in the last 7 days (differs) | 3 | 6 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
forge
Tyler Forge design system skills and MCP servers
Steamworks Release Assistant
Put a game on Steam: store page, achievements, Valve-rule checks, market data, Steamworks.
How to run each
forge As a Claude Code plugin
/plugin marketplace add tyler-technologies-oss/forge
/plugin install forge@tyler-forgeSteamworks Release Assistant As a local MCP server: PyPI package
claude mcp add --env "STEAMWORKS_PUBLISHER_KEY=<YOUR_STEAMWORKS_PUBLISHER_KEY>" --transport stdio steamworks-mcp -- uvx steamworks-mcpRequires: STEAMWORKS_PUBLISHER_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of forge publish no settings it asks for, so we do not compare settings.
What it can do: forge · What it can do: Steamworks Release Assistant · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.