Forge Platform

Handbook

MCP Servers

This folder documents the expected MCP adapter layer for Forge products. Most adapters are not fully shipped — treat this page as a roadmap with honest status labels.

Updated

Status legend

Label Meaning
Shipped (partial) Runnable today with documented limits
Planned Design accepted; no standalone package in this repo yet
Not shipped No production entrypoint

Adapter status

Documented name Real entry Status
forge_lcdl_mcp python -m forge_lcdl.integrations.mcp.server Shipped (partial) — eight baseline LCDL tools always; three gated autonomy tools when env allowlist/dispatch opt-in
forge_fleet_mcp (planned standalone package) Planned — today only lcdl.dispatch_fleet_job on the LCDL sidecar when FORGE_LCDL_MCP_ALLOW_DISPATCH=1 (argv submit subset, not template list/approval)
forge_lenses_mcp (none in this repo) Not shipped — safe Lenses control-plane MCP is future work

Canonical operator detail for the LCDL sidecar: forge-lcdl docs/agents/MCP-SIDECAR.md.

LCDL sidecar tool surface (shipped subset)

Tool Always Gated
lcdl.create_contract … lcdl.final_report (8 tools) yes —
lcdl.run_flow, lcdl.flow_status — FORGE_LCDL_MCP_FLOW_ALLOWLIST
lcdl.dispatch_fleet_job — allowlist + FORGE_LCDL_MCP_ALLOW_DISPATCH=1

Fleet job dispatch via MCP is a subset of the future forge_fleet_mcp template surface — argv submit only, not template list/approval flows.

Planned adapters (not shipped)

When implemented, adapters should remain thin:

  • forge_lenses_mcp — safe Lenses control-plane read/write APIs (approval-aware).
  • forge_fleet_mcp — safe Fleet template/job APIs beyond LCDL dispatch subset.
  • Full forge_lcdl_mcp autonomy surface — opt-in only; policy in Blueprints; approval in Lenses.

Design rules

  • Do not embed platform policy in MCP servers.
  • Platform policy belongs in Blueprints; approval state belongs in Lenses.
  • Reference nav lists this page as MCP roadmap — not as “all MCP servers available.”