Build with MetaForge

MetaForge brings projects, design artifacts, engineering agents and a digital twin into one workspace. The engine runs on your own machine; the dashboard, CLI and your coding agent are three windows onto the same gateway.

❯

Start buildingClone, start the backends, run your first ingest{ }Explore the APIConnect your own tools to the gateway

One workspace, one connected design

Every deliverable MetaForge produces is versioned, reviewable and buildable — that is the whole constraint the system is designed around. Agents never touch a tool directly; they go through the Model Context Protocol, and everything they produce lands in the Digital Twin where it can be diffed and approved.

Work through the engineering loop

A design is rarely finished in one pass. Define the intent, produce an artifact, check it against analysis, and use what you learn to inform the next revision.

01 / Define

Capture the objective, the constraints and the acceptance criteria.

02 / Design

Create or import the artifacts that describe the system.

03 / Validate

Check the assumptions against analysis, simulation or measurement.

04 / Review

Inspect the proposed change and approve the next iteration.

Keep the evidence next to the design

A model is not proof of performance. Check the source, the assumptions and the validation status of a result before an engineering decision rests on it — a rendered 3D view and a moving simulation establish neither.

Make your first request

Start with the gateway health endpoint. It also tells you which authentication mode the gateway is in, which is the one thing you cannot infer from the outside.

Terminal

export METAFORGE_GATEWAY="http://localhost:8000"

# Check that the gateway is available
curl "$METAFORGE_GATEWAY/health"

# Read the project library
curl "$METAFORGE_GATEWAY/v1/projects"

Choose your starting point

Drive it from the CLI

Every subcommand with flags, examples and output shapes — including the interactive forge chat TUI.

Drive it from your agent

Set MetaForge up as an MCP server in Claude Code or Codex and let it call the tools directly.

Drive it from the dashboard

The route-by-route tour of the workspace: projects, twin, runs, approvals and the bill of materials.

What is actually built

Phase 1 (v0.1) covers 6–7 specialist agents across 6–7 disciplines, with KiCad read-only. The capability matrix is the honest list: 97 MCP tools, 11 dashboard routes, and the Phase-1 limits stated as limits. Troubleshooting covers what goes wrong first.

The examples/drone_flight_controller/ reference project — a 4-layer PCB around the STM32F405RGT6 — runs end to end on mock adapters with no Docker required.

Architecture and contributors

Lower-level material for people building MetaForge rather than using it: the architecture overview, the roadmap, the skill, MCP and twin specs, the testing strategy and the governance rules.

If you are contributing code, start with the repo-root CLAUDE.md — it covers the development workflow, the observability requirements and the git conventions. Operational runbooks and UAT artifacts stay in the repository under docs/runbooks/ and docs/uat/ rather than on this site.