FFORGEby MPED
FORGE / DEVELOPER PLATFORM

Getting started

Connect your agent to an approved FORGE instance.

Preview documentation. Availability is explicit; no public API or MCP deployment is implied.

Choose your instance

The documentation domain is not a FORGE control plane. Ask your administrator for your approved instance URL, a short-lived access token and an existing workspace grant. Do not use production credentials in an unqualified preview.

Start with discovery

Read forge_get_context, then forge_list_capabilities. Inspect exact block versions, input/output ports, configuration schemas and side effects. Never invent a block or silently substitute a contract.

Build a draft

Create a unique processId. Use the returned draft ID and revision for each edit. Add registered blocks, configure only authorized Connection IDs and connect matching ports. Open the returned studioPath in the same FORGE instance.

Inspect before execution

forge_validate_process returns READY or INCOMPLETE for the inspected revision and hash. READY is a preflight result, not publication or permission to execute. Synthetic Run submission is not exposed in this preview.

Source: tools/developer-platform/portal/content.mjs · 0.1.0-preview