@forgeos/mcp — ForgeOS as an installable coordinator

The version of ForgeOS that runs inside the caller's own AI, with the caller's own wallet — so no one has to keep a laptop or server on.

A general contractor is a method, not a hosted service. This MCP server ships ForgeOS as that method: a playbook prompt (the brain) plus a set of deterministic verification tools (the trust layer). The caller's agent plans the goal, hires specialist ASPs on the OKX.AI marketplace with the caller's wallet, and calls these tools to recompute every deliverable against independent ground truth before paying. ForgeOS never fronts escrow and needs no always-on runtime — it's the recipe and the referee.

Install

Any MCP-capable AI (Claude Code, Cursor, Codex, …):

claude mcp add forgeos -- npx -y forgeos-mcp

On first use, npx finds it if cached or installs it automatically if not — the same "there → run it, missing → install it" you'd expect. From this repo, before publishing:

# built bundle (self-contained):
pnpm --filter @forgeos/mcp bundle
claude mcp add forgeos -- node apps/forgeos-mcp/dist/server.js
# or straight from source:
claude mcp add forgeos -- pnpm --filter @forgeos/mcp start

Set FORGEOS_CLIENT_AGENT_ID to your OKX.AI User agent id for discovery.

What it exposes

Prompt — forgeos_contractor: load ForgeOS's plan → hire → verify → pay-only-if-verified playbook for any goal.

Tools (all deterministic — no LLM key, no ForgeOS wallet): | tool | what it does | |------|--------------| | forgeos_plan | validate a task DAG (unique ids, acyclic, budget ≤ 1) → budget-allocated nodes | | forgeos_discover_agents | find real specialist ASPs for a capability (via your onchainos CLI) | | forgeos_verify_claims | recompute a deliverable's claims against live sources → matched/discrepant/unverifiable + verdict | | forgeos_verify_onchain | read one numeric on-chain fact and check a caller-asserted value against it |

The caller's AI supplies the intelligence (decomposition, claim extraction, hiring) using tools it already has; ForgeOS supplies structure + recompute. This is the "don't trust, recompute" layer, usable inside and outside OKX.AI.

Why this shape

The full hire-and-coordinate flow can't be a scale-to-zero endpoint (hiring needs a wallet, escrow, and async waiting). But it can run on the caller's side, because the caller already has an AI, a wallet, and marketplace access. So ForgeOS is distributed, not hosted: anyone can use it through their own AI, auto-installed if missing, with nobody's machine kept on.