forgecraft

ForgeCraft is a setup-time CLI tool that analyzes your project and generates a suite of engineering standards tailored to your stack. This MCP server helps you bootstrap a production-grade coding standard by scanning your codebase, detecting your technology stack, and producing instruction files, quality gates, and documentation that guide AI assistants and developers. When you run the tool, it creates a forgecraft.yaml configuration, set of CLAUDE.md and other rule files, and pre-configured hooks to enforce standards. It also supports multiple AI assistants and domains, making it easier to enforce consistent patterns across tools like Claude, Cursor, Copilot, Windsurf, Cline, and Aider. Use it to establish SOLID-compliant blocks, testing pyramids, DDD/CQRS patterns, and 12-Factor practices across your repo.

To use ForgeCraft, invoke the MCP command through npm/npx as shown in the README: run npx forgecraft-mcp setup . from your project root. This triggers auto-detection of your stack and the generation of the forgecraft.yaml plus the corresponding instruction blocks and hooks. If you want to augment the setup with sentinel diagnostics for your AI, you can add the mcp sentinel command to guide future actions, then remove it after the initial configuration to keep token usage low.

Prerequisites

• Node.js (recommended LTS) and npm installed on your system
• Internet access to fetch the forgecraft-mcp package

Install and run ForgeCraft MCP (setup-time CLI):

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v

2. Run the ForgeCraft MCP setup using npx (no global install required): npx forgecraft-mcp setup .

3. The tool will auto-detect your stack, generate forgecraft.yaml, and create instruction files (CLAUDE.md, .cursor/rules/, etc.) in your project. Follow any on-screen prompts if they appear.

4. Optionally, configure version control hooks and CI/CD guidance as guided by the generated files. You can later modify forgecraft.yaml to adjust tags, tier, and other preferences.

Tips and notes:

• ForgeCraft is a setup-time tool; it does not run as part of your production runtime. Remove it after initialization if you want a lean runtime footprint.
• The generated forgecraft.yaml controls project classification, tags, and tier. You can customize it to tailor the standards to your domain.
• If you need to re-scan after making changes, use the MCP refresh command as described in the CLI docs (e.g., forgecraft mcp refresh <dir>).
• The tool supports multiple AI assistants and domain rules. Ensure your repo has appropriate stacking (REST/GraphQL, frontend frameworks, etc.) so the auto-detection yields the most relevant blocks.
• If you want to experiment with a sentinel diagnostic step, you can integrate a small helper invocation (as shown in the README) to guide the AI, then remove it after initial setup to save tokens.