MCP

Workshop exposes agent-facing surfaces so AI systems can author, inspect, revise, and prepare video artifacts without bypassing compiler governance.

There are two MCP-facing surfaces:

Surface Routes Best for
Streamable HTTP MCP transport GET/POST/DELETE /api/mcp MCP-compatible remote clients
HTTP gateway tools /api/mcp/* Plain HTTP clients, SDKs, tests, and simpler agent integrations

Discovery

GET/api/mcp/manifest

Get MCP manifest

Returns transport, auth, OAuth, and workflow metadata.

GET/api/mcp/tools

List tool definitions

Returns available HTTP gateway tools and input schemas.

bash
curl "$WORKSHOP_URL/api/mcp/manifest" \
  -H "Authorization: Bearer $WORKSHOP_BEARER_TOKEN"

Streamable HTTP Transport

Route Purpose
GET /api/mcp MCP streamable HTTP GET
POST /api/mcp MCP JSON-RPC messages
DELETE /api/mcp Close MCP session

Remote MCP sessions require authenticated API-key or bearer-token context. Demo authentication is not supported for remote MCP sessions.

HTTP Gateway Tools

Route Tool Purpose
POST /api/mcp/compile workshop_compile Compile .ws into RenderGraph
POST /api/mcp/scene workshop_get_scene Inspect one RenderGraph scene
POST /api/mcp/tokens workshop_get_tokens Extract design tokens and film metadata
GET /api/mcp/moods workshop_list_moods List moods and aliases
GET /api/mcp/templates workshop_list_templates List templates
POST /api/mcp/prompt workshop_generate_prompt Generate optional external video prompts
POST /api/mcp/documents/save workshop_save_document Create or update document
GET /api/mcp/documents workshop_list_documents List documents
GET /api/mcp/documents/{id} workshop_load_document Load document
DELETE /api/mcp/documents/{id} workshop_delete_document Delete document

Agent Production Pattern

A good Workshop agent does not jump directly from prompt to publish. It should:

  1. Draft .ws from intent.
  2. Compile and inspect diagnostics.
  3. Save the document for review.
  4. Render only when asked.
  5. Present source, graph summary, MP4, and metadata to a human or workflow gate.
  6. Leave the final publication decision to the governing application or operator.

OAuth Metadata

Remote MCP clients can discover OAuth metadata through:

  • GET /.well-known/oauth-protected-resource/api/mcp
  • GET /.well-known/oauth-authorization-server
  • POST /oauth/token

Client credentials are supported for remote MCP connectors.

Next Steps