Soup.video
Model Context Protocol

SOUP MCP.

Agents call Soup as an AI Director. You bring the idea; Soup directs the film. Paste the URL into Cursor, Claude, or ChatGPT.

Endpoint

https://soup.video/mcp

Streamable HTTP. Auth: Authorization: Bearer sk_soup_… from Developer Settings. list_models works without a key.

For agents

llms.txt

REST spec

OpenAPI

Reference

API docs

Tools

Tool Auth What it does
list_models Optional List models
create_generation API key Create generation
get_generation API key Get generation status
run_workflow API key Run authored workflow

The runner pays. Failed model steps refund. Workflows you did not author stay closed. Studio graphs never leave the server.

Cursor

Remote MCP server. URL plus one header.

{
  "mcpServers": {
    "soup": {
      "url": "https://soup.video/mcp",
      "headers": {
        "Authorization": "Bearer sk_soup_YOUR_KEY"
      }
    }
  }
}

Auth today vs OAuth

Pasting this URL into Cursor or a Claude custom connector is enough if you also send a Soup API key. The public Claude Connectors directory and ChatGPT Apps store need OAuth 2.1 (login on soup.video, then a token) — same pattern as Notion or Linear. That is a separate auth service, not a header. Bearer stays for keys and HTTP.

Details: MCP docs · where to list Soup · REST API