-- **Forge as an MCP server** (`forge mcp serve`). Exposes the runtime as MCP tools so Claude Desktop, Cursor, Continue, and any other MCP client can plan and run Forge tasks from their own chat. Two trust tiers: read-only (default) exposes `forge_status`, `forge_plan`, `forge_get_task`, `forge_list_tasks`; `--allow-execute` (or `FORGE_MCP_ALLOW_EXECUTE=true`) adds `forge_run` and `forge_cancel_task`. Wraps the same `orchestrateRun()` entry point as the CLI/REPL/dashboard, so MCP-driven plans are byte-identical paths. See `docs/MCP-SERVER.md` for per-client setup.
0 commit comments