MCP

Soup exposes a remote Model Context Protocol server so agents can list models, start a generation, poll the job, and run a workflow you authored. The product is an AI Director: pass the user’s idea, not a camera questionnaire.

Public listing page (sitemap, footer): soup.video/mcp-server.

Endpoint

https://soup.video/mcp

Transport: Streamable HTTP. Auth: Authorization: Bearer sk_soup_… on tool calls that charge or read jobs. list_models works without a key.

Create a key in Developer Settings. Same wallet as the REST API — the runner pays.

Tools

Tool	Auth	What it does
`list_models`	no	Listed image and video models, pricing, params
`create_generation`	yes	Start a job. Charges the key owner
`get_generation`	yes	Poll `job_id` until completed or failed
`run_workflow`	yes	Run a published workflow you authored. Other people’s listed graphs stay closed

Failed model steps refund; successful steps keep the charge. See Billing.

Cursor

Add a remote MCP server named Soup, URL https://soup.video/mcp, header Authorization = Bearer sk_soup_….

Or an install-style config:

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

Claude

Custom connector: Customize → Connectors → Add custom connector → paste https://soup.video/mcp. Claude’s public Connectors Directory needs OAuth 2.0; Bearer keys work for a custom connector on your account.

ChatGPT

Custom MCP plugins (Business/Enterprise) accept this URL the same way. The public ChatGPT app directory also wants OAuth — that is a follow-on, not this endpoint.

Composio

Composio is an agent tool router: 1,700+ app toolkits, per-user OAuth, sandbox, and Instant (Composio’s wallet pays the provider). Soup is not a first-party Composio toolkit yet.

Until then, point a Custom MCP toolkit at https://soup.video/mcp with API-key auth, or apply as a toolkit partner at composio.dev/partnerships/toolkit with this docs URL, OpenAPI, and a company test account.

Discovery files

Server card: https://soup.video/.well-known/mcp/server-card.json
Registry manifest: https://soup.video/.well-known/mcp/server.json
OpenAPI: https://soup.video/openapi.json

Publish the registry manifest with mcp-publisher under the video.soup namespace (DNS proof for soup.video) when you list in the official MCP Registry.

What this is not

Not public API for other people’s listed workflows. That stays author-only until Stage 2 public_api.
Not a graph leak. Tools never return node prompts or Studio JSON.
Not OAuth yet. Directory listings on Claude Connectors and ChatGPT Apps need OAuth 2.0 on top of this server.