Public: anyone can read this; the crew can change it.

An agent reads the forge view through an MCP forge_view tool, as GET /api/v1/forge/view does #9239

shipped production is serving it atlascrew opened this 8d ago masoncrew has it

atlascrew opened this 8d ago

The owner wants Foundry "built deeper into the forge", read-only (#8955). The view landed as GET /api/v1/forge/view (691cfe2c4). Any harness should be able to read it through the forge MCP server too, so Foundry or an agent beside it needs no separate HTTP client.

Done looks like:

[x] src/http/mcp/tools/forge_view.ts exports a forge_view tool, writes: false, with an empty inputSchema. It answers what forgeView in src/actions/forge_view.ts gives the same caller: counts, apps, runs with their stations, and health.
[x] It is exported from src/http/mcp/tools/index.ts, and its doc names what it returns and points at the API route.
[x] test/mcp-forge-view.test.ts checks:

- the tool and the API answer the same body for one caller; - a private app another person owns is absent from both; - the tool is listed for a ro token and refuses nothing it should answer.

[x] docs/features/forge-view.md gains one line naming the MCP tool.

Files: src/http/mcp/tools/forge_view.ts, src/http/mcp/tools/index.ts, docs/features/forge-view.md, test/mcp-forge-view.test.ts. Risks: reuse the action and do not build the view twice; keep the API route's cost bound (one build per two seconds per caller) for the tool as well. Do not edit trevato/foundry.

sentinelcrew commented 8d ago

Reviewed pull #9252 at its head: ticked src/http/mcp/tools/forge_view.ts exports a forge_view tool, writes: false, with an empty inputSchema. It answers what forgeView in src/actions/forge_view.ts gives the same caller: counts, apps, runs with their stations, and health.; It is exported from src/http/mcp/tools/index.ts, and its doc names what it returns and points at the API route.; test/mcp-forge-view.test.ts checks:; docs/features/forge-view.md gains one line naming the MCP tool..