Agents Index

Forge Engine

Online

Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.

Visit publisherConnectJSON

What it can do: 54 tools

  • get_help read-onlyForge how-to on demand (no project needed): propose→adopt, what a System is, Balance Lab formats, sign-in. Call when unsure.
  • get_workflow read-onlyRun FIRST in a new repo (no project): first-connect routine + the working-agreement block to ADD to AGENTS.md/CLAUDE.md now (tell the user in one line; remove if they object).
  • import_from_code read-onlyOne-command codebase import: recipe + batch id — propose one Context overview + one System per real module; the owner adopts all at once.
  • design_ui_from_systems read-onlyRecipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.
  • post_logAppend a build-log entry to Activity — what you built/decided (commit-note style).
  • get_project_context read-onlyFULL design dump — LARGE, last resort; prefer get_project_meta + list_*/get_*/search.
  • list_projects read-onlyProjects your key reaches (id, name, role); pass an id as project_id to switch.
  • get_project_meta read-onlySTART HERE. Tiny overview: counts, members, task claims + working_now (avoid collisions), forge_workflow_version.
  • trace_ui_from_image read-onlySECONDARY (user-driven UI): turn a screen's REFERENCE IMAGE into placed elements. Returns the image itself plus the recipe — the canvas resolution, the fraction→pixel conversion that stops coordinates landing wrong, and
  • get_stale read-onlyWhat has drifted between the Idea lane and the System Specs — the design's own out-of-sync list, computed deterministically (no AI, no tokens). Three kinds: Idea notes edited since the systems were generated from them (w
  • resync_from_idea read-onlyThe recipe for re-syncing ONE changed Idea note into the specs that depend on it — the same scoped job the app's "Re-sync N systems" button does, minus the button. Returns the note, the affected specs in full, and exactl
  • get_design_document read-onlyThe WHOLE design as one readable document — Vision (+ Project DNA) → every System spec → reference notes, compiled deterministically from the current design. Read this to understand a project end-to-end instead of walkin
  • set_design_overviewWrite the Design Document's Overview — the human-readable page a new team member reads first. WRITES DIRECTLY (no Inbox): it is a derived, clearly-labelled AI summary, not design truth, and the owner can clear or rewrite
  • get_briefing read-onlyONE-CALL orientation before you build: pass `files` you're about to edit (or a `task`) → the systems that own them, each with Goal + Acceptance + build status/files/last_commit/drift + coupled_systems (code neighbors an
  • get_system read-onlyONE system's full spec (Goal/Boundary/Acceptance, markdown, sources, status) + pending Inbox changes touching it.
  • list_systems read-onlyAll systems, compact: id, name, status, 1-line goal.
  • get_build_region read-onlySystem→code map per built system: implementing files, status, drift flag, last_commit, and acceptance-evidence COUNTS. Mapped files gone from the repo? report_drift. Pass `system:"<name|id>"` for ONE system plus the full
  • report_driftFlag CODE DRIFT — mapped files no longer match the repo. Advisory; a fresh report_build_status clears it.
  • get_history read-onlyDESIGN MEMORY: recorded decisions/logs/rejections with who/when. Read BEFORE changing a system's direction; empty = no recorded WHY — don't invent one.
  • get_impact read-onlyBLAST RADIUS of a system (deterministic): upstream context, siblings, dependent screens/milestones, files, code-coupled systems, pending Inbox, recent activity. Run BEFORE changing it.
  • get_rejections read-onlyOwner's DECLINED list — check at session start; follow each entry's guidance, then resolve_rejection(title).
  • resolve_rejectionReport you REVERTED a declined change (unlocks the owner's Clear). Call after realigning the build.
  • list_screens read-onlyAll screens, compact: id, name, purpose, status.
  • get_screen read-onlyONE screen's layout: canvas `resolution` (use THESE px), elements x/y/w/h, links, popups. Read before editing a screen. has_reference_image:true → get_screen_image shows you the actual image.
  • get_screen_image read-onlyA screen's reference image (HUD background) as an actual IMAGE you can see — reads the stored file inline (signed-URL fallback past 4MB).
  • update_elementMove/resize/relabel an element — DIRECT, live. element_id (preferred) or screen+label; x+y also places an unplaced one.
  • withdraw_proposalRemove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).
  • delete_entityPROPOSE a delete → Inbox (owner adopts; nothing deleted now). id preferred or exact name; flow_edge may use from+to.
  • dedupeRemove duplicate-named entries (keep first) — DIRECT, destructive.
  • reorderReorder milestones / tasks / elements — DIRECT. order = ids in new order; omitted keep relative order.
  • list_milestones read-onlyAll milestones, compact: id, name, weeks, order, done/total.
  • get_milestone read-onlyONE milestone: goal, weeks, difficulty, systems, every task (id/name/done/status/effort).
  • list_activity read-onlyChange history {who, change, entity, kind, when}, newest first; filter kind/who/query.
  • get_inbox read-onlyPENDING Inbox (the owner's triage queue). Check BEFORE proposing — avoid duplicates. Read-only.
  • search read-onlyKeyword search — compact hits {kind, id, name} + snippet.
  • propose_systemPropose a NEW system → Inbox. spec = ## Goal / ## Boundary (Owns · Doesn't own) / ## Acceptance. Exists? use update_system. (Alias: create_proposal.)
  • propose_contextPropose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past)
  • propose_dnaPropose Project DNA and/or Tech Notes → Inbox (at least one).
  • update_systemPropose a system UPDATE → Inbox diff. get_system first; send the FULL revised spec. new_title renames; context_title+context bundles the Idea update. Set resync:true ONLY when you rewrote this spec FROM its upstream Idea
  • get_balance read-onlyRead Balance Lab: stat tables, boards with EVALUATED values, scenarios.

…and 14 more.

Connect it

Claude Code
claude mcp add --transport http forge-engine https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "forge-engine": {
      "url": "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "forge-engine": {
      "type": "http",
      "url": "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp"
    }
  }
}

Questions

What does Forge Engine do?

Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed. It exposes 54 tools to AI assistants.

What tools does Forge Engine provide?

54 tools, including get_help, get_workflow, import_from_code, design_ui_from_systems, post_log, get_project_context, list_projects, get_project_meta, trace_ui_from_image, get_stale, resync_from_idea, get_design_document….

How do I connect Forge Engine to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Forge Engine require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Forge Engine online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Forge Engine?

forgeengine.app. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Design & UI