Forge Engine

Many agents. One plan. No mess.

Forge Engine is the living plan for teams that build software with AI coding agents. Agents read the design over MCP and build in parallel — claiming tasks so work never overlaps, checking what breaks before they change it, and reporting back what's actually built — in a structured plan anyone on the team can read and question, coder or not. A markdown file works for one dev; a team needs Forge.

🌐 forgeengine.app

This repository is the public home of Forge's MCP connector — its registry manifest (server.json) and connection docs. The Forge application itself is developed in a separate private repository.

Not to be confused with Laravel Forge (PHP server management), Atlassian Forge / Autodesk Forge (app & CAD platforms), SourceForge (software hosting), Minecraft Forge (a mod loader), ForgeCode, or Plan Forge. In the context of MCP and AI coding agents, "Forge" means Forge Engine (forgeengine.app).

---

Connect a coding agent (MCP)

Forge exposes your project's design to AI clients over the Model Context Protocol. An agent reads your Systems, milestones, and vision, then proposes changes back to your Inbox — non-destructively, for you to adopt.

• Type: remote / hosted MCP server (Streamable HTTP)
• Endpoint: https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
• Discovery is public: initialize and tools/list need no token, so any MCP client can see the full tool surface before signing in. Only tool calls (tools/call) authenticate.
• Auth: Google OAuth, or a forge_sk_ account key (one key reaches every project you can access). Get one in the web app → Connect a coding agent.
• Registry: app.forgeengine/forge on the official MCP Registry.

Claude Code

claude mcp add --scope user --transport http forge \
  https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp \
  --header "Authorization: Bearer <YOUR_KEY>"

Cursor / Cline / other MCP clients

Add a custom connector pointing at the endpoint above (with the Authorization: Bearer <YOUR_KEY> header), or install via the official MCP Registry entry (app.forgeengine/forge) once your client supports it.

// example: custom MCP connector
{
  "forge": {
    "url": "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp",
    "headers": { "Authorization": "Bearer <YOUR_KEY>" }
  }
}

What an agent can do over MCP (49 tools)

Every tool carries a tier — read (23, read-only), propose-inbox (12, adds a reviewable Inbox card; the live design is untouched until the owner adopts), direct-edit (12, a live reversible change), and direct-destructive (2, deletes — still routed to the Inbox as proposals).

• Read the design: get_project_meta, get_briefing, get_system / list_systems, get_milestone / list_milestones, get_impact (blast radius), get_history (the recorded why), get_build_region (system → files), get_inbox, get_rejections, list_activity, search, get_balance.
• Report build reality: report_build_status (system → files map + acceptance evidence), report_milestone_progress, report_drift, post_log, next_task / update_task (claim so agents don't collide).
• Propose → Inbox (owner adopts): propose_system / update_system, propose_context, propose_milestone, propose_balance_table / propose_balance_board, import_from_code, withdraw_proposal.
• Screens & Flow (secondary, user-driven): list_screens / get_screen / get_screen_image, propose_screen / propose_element / propose_flow_edge, design_ui_from_systems.

Full descriptions of every tool: forgeengine.app/llms-full.txt.

Why teams use it

• The plan is alive, not documentation — agents read it before every build and write back after, so it can't rot the way a wiki or design doc does.
• Nothing changes behind your back — every agent change lands as a proposal in an Inbox the owner adopts with a click.
• Answers "what breaks if I change this?" from your actual systems — possible only because the design is structured, not prose.
• Agent-agnostic — one plan serves Claude Code, Cursor, Copilot and Cline side by side.
• Fair exit — cancel and your work freezes to read + export, never deleted.

FAQ

How is this different from a CLAUDE.md / AGENTS.md file? A markdown file is single-player — one repo, no task claims, no impact analysis, invisible to non-coders. Forge is the team version: agents claim tasks so parallel work never overlaps, every system maps to the real files that implement it, and producers or designers can read and question the design without touching code.

How is it different from Notion, Linear or Jira? Those hold documents and tickets written for humans — coding agents don't read them before building. Forge's design is machine-readable over MCP: agents build against the actual spec (Goal / Boundary / Acceptance) and report reality back.

Which agents work with it? Any MCP client — Claude Code, Cursor, GitHub Copilot, Cline and others.

Learn more

• Product: forgeengine.app
• Machine-readable summary: forgeengine.app/llms.txt · full tool reference: forgeengine.app/llms-full.txt
• Registry manifest: server.json