Overview Installation Workflows AI Agents Collaboration Job Policies Credits & Monetization

AI Agents & MCP

OpenFork exposes a hosted MCP server so AI desktop and coding agents can operate movie workflows directly: discover models, read project context, plan a production run, dry-run the launch, monitor jobs, review assets, and regenerate failed work through the Distributed GPU Network.

Hosted MCP URL

Remote MCP endpoint

https://www.openfork.video/api/mcp/openfork

OAuth is the preferred path for Codex, Claude, OpenCode, OpenClaw, Hermes, and other clients that support remote MCP authentication. API key / Bearer auth is the advanced fallback for clients that cannot complete browser sign-in.

What Agents Can Do

Plan productions

Read capabilities, choose starter templates, create a task graph, select compute tiers, and prepare launch values for full movies or small sample versions.

Work with projects and branches

List editable projects, read branch-safe context, create projects or child branches through OAuth grants, and keep sample runs isolated when a branch grant allows it.

Operate and repair runs

Launch dry-runs, start approved workflows, stream progress, review generated assets, cancel jobs, update scenes, and run from a failed step without throwing away good upstream work.

Use project memory

Resolve named characters, voices, styles, locations, props, and reference assets from OpenFork memory instead of guessing from chat history alone.

Connect From Your Agent

Codex

codex mcp add openfork --url https://www.openfork.video/api/mcp/openfork

Claude

Add a custom remote MCP connector named OpenFork, use the hosted MCP URL above, and approve the OpenFork OAuth grant in the browser.

Hermes

hermes mcp add openfork --url https://www.openfork.video/api/mcp/openfork --auth oauth

OpenClaw

# Requires Node 22.19+; Node 24 is recommended.
npm install -g openclaw@latest
openclaw onboard --install-daemon
openclaw mcp add openfork --url https://www.openfork.video/api/mcp/openfork --transport streamable-http --auth oauth
openclaw mcp login openfork
openclaw mcp doctor openfork --probe

Open AI Agents setup

Pick your app, copy setup commands, and create fallback API keys

Safe Production Loop

Discover first

Ask the agent to call openfork_get_capabilities, then openfork_list_projects or openfork_get_project_context before choosing a workflow.

Dry-run before spend

The agent should plan and dry-run the launch before a real workflow starts. Non-dry-run launches should happen only after visible user approval.

Use available funding

Plan and dry-run responses expose generationAccessStatus for own DGN clients, credits, free generations, and prepaid wallet balance. If the approved route is covered, the agent can use credit or monetize routing within the numeric limits.

Stay inside the grant

OAuth grants and account API keys are scoped, revocable, command-limited, and capped by numeric production limits such as VRAM, duration, and queued jobs. They are not DGN/provider keys and do not expose raw database, wallet, admin, or autoscale access.

Starter Prompt

Use the OpenFork MCP server named openfork.

First call openfork_get_capabilities.
Then call openfork_list_projects.
Help me choose an existing project/branch or create a new one.
Plan a short movie workflow first.
Inspect generationAccessStatus for my own DGN client, credits, free generations, and prepaid wallet.
If wallet or credits can cover the approved route, use credit or monetize routing instead of refusing paid jobs.
Ask whether I want 2-4 sample versions before the full movie.
Dry-run launch first.
Do not launch a real workflow until I explicitly approve.