Developer Preview Ferrosa Forge — compact tooling for AI coding agents.

Ferrosa Forge

CLI and MCP server for coding agents

Give agents results they can read.

Forge wraps common developer operations — builds, tests, diffs, lint, code analysis — and returns compact structured output.

A coding agent reads machine-readable results and spends fewer tokens on raw logs.

SPECIMEN frg run cargo test
failed
2
errors[0].file
src/engine.rs
errors[0].line
412
output
structured JSON
The same run, as an agent sees it. Developer preview — the CLI and MCP tool surface may still change before 1.0.

What's in the box

Structured toolchain wrappers

frg run cargo|go|dotnet|npm|python|mix parse native build/test/lint output into JSON with error locations, warning counts, and an actionable hint on failure. Covers build, test, check, clippy/vet/lint, and format checks.

Log & diff distillation

test-summary (cargo/pytest/jest/go/mix), log-distill (errors + warnings with context), diff-filter (collapses large hunks, skips lockfiles and generated files), lint-dedup, and log-monitor (stall, OOM, and disk-pressure detection on live streams).

Quality & security scans

smell-detect, doc-coverage, coverage-gate, STRIDE threat-scan, fail-loud-scan (swallowed errors and silent fallbacks, AST-based across 8 languages), materialization-scan, secret-scan, and CVE deps-audit.

Architecture analysis

dsm (Design Structure Matrix with cycle detection and refactor suggestions), dsm dead-code, dep-tree fan-in/fan-out, api-diff and schema-diff breaking-change detection, and merge-check.

Code discovery

digest — a structural summary with no bodies, the best first call on an unfamiliar file — plus excerpt, lookup, outline, glob with per-file stats, and project-detect.

CQL-backed task board

frg task create|update|list|link|board — a kanban store on a CQL cluster, plus checklist for persistent workflows with DAG dependencies, typed waiting gates, and atomic claim/release for agent fleets.

Knowledge-graph ingestion

ingest (codebase structure via LSP), SSRF-guarded ingest-url/fetch-url, web-search via a trusted SearXNG backend, and ingest-paper (academic PDFs with reading-order reconstruction for multi-column layouts) — all writing typed entities and edges into Ferrosa Memory.

Claude Code hooks & analytics

frg init --global installs Claude Code hooks that suggest frg digest or frg excerpt before Claude reads a very large file; frg gain and frg analytics report the token savings per tool.

Install

Forge is a developer-preview release with prebuilt binaries. Pick one path:

Homebrew (macOS Apple Silicon, Linux x86_64)

brew install ferrosadb/tap/forge
frg --version

Release binaries

Download from the GitHub Releases page and put frg on your PATH:

PlatformAsset
macOS Apple Silicon (arm64)frg-macos-aarch64.tar.gz
Linux x86_64frg-linux-x86_64.tar.gz
Linux aarch64frg-linux-aarch64.tar.gz
Windows x86_64frg-windows-x86_64.zip

Each release includes a SHA256SUMS file; verify with sha256sum -c SHA256SUMS --ignore-missing.

From source

Building from source needs Rust, from rustup.rs. On macOS it also needs Apple's command line developer tools; the first git command offers to install them.

git clone https://github.com/ferrosadb/forge.git
cd forge
cargo install --path crates/cli --locked

Any platform with a Rust toolchain works; frg has no Apple-Silicon-only constraint.

Connect it to your agent

Expose the stdio MCP server by adding Forge to ~/.claude/settings.json (Claude Code):

{
  "mcpServers": {
    "forge": {
      "command": "/path/to/frg",
      "args": ["--mcp"]
    }
  }
}

Any MCP client that can launch frg --mcp as a stdio server works the same way. For a long-running shared client, start Streamable HTTP on loopback and connect to POST /mcp:

frg --mcp-http --mcp-http-addr 127.0.0.1:9977
# MCP endpoint: http://127.0.0.1:9977/mcp

Ferrosa Memory's next release installs and validates Forge for its research and ingestion workflows, including project_summary and dry-run ingest. Then install the Claude Code hooks:

frg init --global

Optional backends

The core tools are standalone. Some tool families need a backend, and each fails loudly when its backend is missing:

Tool familyNeedsResolution
Task board / checklistsA CQL contact pointcql_host arg → FORGE_CQL_HOST env → .forge/config.toml → 127.0.0.1:9042
IngestionRunning Ferrosa Memory HTTP endpointAuto-discovered from ~/.config/ferrosa-memory.toml
web-searchTrusted SearXNG endpointFORGE_WEB_SEARCH_URL or SEARXNG_URL
ingest-descriptionsLocal Ollama modelOllama default endpoint

Uninstall

  1. Remove the hooks with frg init --global --uninstall, and with frg init --uninstall in any project where you ran frg init.
  2. Delete the forge entry from the mcpServers block you added. Removing the hooks leaves it in place.
  3. Remove the binary with brew uninstall ferrosadb/tap/forge or cargo uninstall forge, or delete the frg you downloaded.
  4. Optionally delete Forge's local data: ~/Library/Application Support/forge on macOS, which holds run history and saved raw output, and any .forge/ folders in your projects, which hold checklists, sheet mappings and project settings.
Developer preview. Forge is useful today, but the public API and MCP tool surface may still change before 1.0. Apache-2.0 licensed.