MCP Server and SDK

Workshop is meant to be integrated into other production systems. The MCP surface gives agents safe video-production tools. The SDK and Studio surfaces give humans and operators editable workflows around the same .ws source.

MCP: Agents As Video Producers

The MCP layer lets an agent create, inspect, repair, and save video artifacts without bypassing compiler governance.

Agents can:

  • Compile .ws and read diagnostics
  • Inspect scenes in a RenderGraph
  • Extract mood and design tokens
  • List moods and templates
  • Save, load, list, and delete documents
  • Prepare source-to-clip workflows through the API

The agent should not be treated as the final publisher. A strong workflow lets agents draft and revise while humans or product rules decide what is published.

HTTP Gateway And Remote MCP

Workshop exposes both a streamable HTTP MCP transport and simpler HTTP gateway endpoints under /api/mcp/*. Remote clients can authenticate with bearer tokens or API keys, and OAuth client-credentials discovery is available through the .well-known metadata routes.

See MCP for the current route surface.

SDK And Studio

The SDK and Studio layers make .ws editable without asking users to work only in a terminal. They are useful for:

  • SaaS products embedding video creation
  • Operator review tools
  • Internal content workflows
  • Template filling and personalization
  • Human-in-the-loop approval before render or publish

The design goal is a collaborative document workflow, not a traditional timeline editor. The source remains the artifact of record.

Why This Matters

Agentic video production needs a boundary between generation and publication. Workshop provides that boundary with a compiler, persisted documents, diagnostics, render metadata, and deterministic output.

Next Steps