ProdForge

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.5.0Updated Oct 26, 2026

Connects MCP servers, packages, security checks, and release gates in one repo.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

ProdForge bundles a catalog of production tooling and MCP servers, letting an assistant list packages, merge MCP configs, run readiness checks and a release…

What you can do
  • List the bundled packages and production tools, optionally filtered by production phase
  • Generate one merged MCP config that wires every shipped MCP server together
  • Show the production checklist grouped by phase, with the tool that runs each step
  • Run local production-readiness checks on the current project and validate the catalog itself
  • Run the release gate, executing each installed fleet tool and reporting missing ones as ABSENT rather than PASS
When to use it
Useful when starting a new product or repo and you want a pre-assembled set of build, security, test, release and operate tooling instead of wiring MCP servers one by one. Also fits teams that want a repeatable pre-release gate that refuses to fake a pass.
Requirements
Runs as a local stdio process, either via npx from the npm package or via the published container image. No authentication, environment variables or headers are declared. The ship gate executes other installed fleet tools in a target directory, so those tools must be present for a full run.
Before you install
The ship gate runs other installed tools in a given directory, so review what those tools do before invoking it. The README notes that stacks declare required environment variables, so check a stack's needs before scaffolding. No credentials are requested by this server itself.

Installation

In SourceWeft

  1. Open ProdForge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ProdForge

Take any product to production without wiring it all yourself.

You have the product idea. Then comes the hassle nobody warns you about: which MCP servers do I need, how do I connect them, what security checks matter, how do I know a release actually shipped, what breaks in production first?

ProdForge is one massive repo that already connected all of that together.

One catalog. One merged MCP config. Five production stacks. One ship gate.

bash
npx @reneturcios/prodforge listnpx @reneturcios/prodforge connect --write mcp.jsonnpx @reneturcios/prodforge doctornpx @reneturcios/prodforge checklistnpx @reneturcios/prodforge shipnpx @reneturcios/prodforge init cli-tool my-tool   # real scaffold: files + tests

What is inside

  • catalog/ - Every tool in the fleet in one registry: Greenlight, Shipcheck, Wallcheck, the Security Wave (hookcheck, actionpin, injectcheck, mcpvet, depguard, flowcheck, tracewatch), mcpaudit, cidiff, reprocheck, contextbudget, agentsfile, envdoc, npmpreflight, envdoctor, logdigest, and more. 26 tools, grouped by production phase: build, secure, test, release, operate.
  • mcp/ - One merged MCP config that wires every shipped MCP server together at once, for Claude, Cursor, and VS Code. Stop copy-pasting server blocks one by one.
  • stacks/ - Five production stacks you start from instead of a blank repo: mcp-server, saas-web, api-service, cli-tool, ai-agent. Each stack says exactly which tools are pre-wired, which env vars it needs, and what its release gate is. prodforge init <stack> <name> generates a real one: package.json, tsconfig, README, src, and a passing test suite.
  • playbooks/ - The production playbook, the release playbook, the security playbook, and the observability playbook. Short, checkable, no fluff.
  • CLI + MCP in one bin - Same fleet factory pattern as Greenlight and Shipcheck: prodforge is a CLI for humans and an MCP server for agents. Agents get list_packages, connect_config, production_checklist, doctor_report, catalog_health, and ship_gate.

Why this exists

Every tool in the catalog already shipped on its own: npm, GHCR, and the MCP Registry, with tests and real production validation. The pain was never any single tool. The pain was figuring out how they fit together while you are trying to ship a product.

ProdForge is that fit, done once, in public, and kept updated.

Start here

  1. Run prodforge doctor in your project. Fix what it names.
  2. Run prodforge connect --write mcp.json. Your agent now has the whole fleet.
  3. Pick a stack in stacks/ closest to your product and follow its checklist.
  4. Before you tag anything, run prodforge ship. It executes each installed fleet tool and reports the rest honestly: any FAIL is a NO-GO, a missing tool is ABSENT (never a PASS), and an unwired gate is NOT-WIRED. Exit 0 only on GO.

Stacks at a glance

StackForPre-wired gates
mcp-serverA new MCP servermcpaudit, mcpvet, shipcheck, npmpreflight
saas-webA web SaaS productwallcheck, flowcheck, envdoc, shipcheck
api-serviceAn API or backend servicedepguard, flowcheck, logdigest, shipcheck
cli-toolA CLI / dev toolagentsfile, contextbudget, cidiff, shipcheck
ai-agentAn agent productinjectcheck, tracewatch, mcpvet, contextbudget

Status

v0.5.0, built 2026-10-25 (Wave D: MCP catalog hardening, a vetting ledger covering all 27 registry tools, and a 107 server discovery list with every unvetted server kept out of the default profile). Overnight build log in docs/OVERNIGHT-2026-10-25.md. Roadmap in docs/ROADMAP.md - 5x the current scope, in waves.

MIT. By Rene Turcios / CloudCorpRecords. Fleet: https://github.com/CloudCorpRecords

Source: README.md at commit 8c31ef0

Tools

6

list_packages

List every package ProdForge can wire together, optionally by production phase.

Parametersphase

connect_config

Return one merged MCP config wiring every shipped MCP server together.

Takes no parameters.

production_checklist

The full production checklist, grouped by phase, with the tool that runs each step.

Takes no parameters.

doctor_report

Run local production-readiness checks on the current project.

Takes no parameters.

ship_gate

Run the release gate: executes each installed fleet tool in the given directory, reports ABSENT when missing, never fakes a PASS.

Parametersdir

catalog_health

Validate the ProdForge catalog itself: duplicates, missing fields, bad phases.

Takes no parameters.

Version history

1
  1. v0.5.0LatestOct 26, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts