Integrations

Use this page when you want Soup to show up as a provider inside other agents and apps. The surfaces that are live today are the REST API, OpenAPI, and the remote MCP server.

What Composio is

composio.dev/developers is not an app store for humans. It is a control plane for other people’s agents:

Toolkits — Gmail, Slack, GitHub, Fal, ElevenLabs, and 1,700+ more, with managed OAuth
Sessions / MCP — one hosted MCP URL that already has the user’s connected apps
Instant — paid tools run on Composio’s provider accounts; the agent builder’s Composio balance is charged, not each end-user’s Soup wallet
Firewall / traces / skills — screen tool calls, log them, and return playbooks

If Soup is listed as a Composio toolkit, every agent built on Composio can call “direct a film” without wiring our API. That is the acquisition channel.

How Soup gets in

Ship REST + remote MCP (done: this API and /mcp).
Apply at composio.dev/partnerships/toolkit — type Composio Toolkit Partnership. Tick REST + remote MCP, API key auth, company test account, docs URL https://soup.video/mcp-server, OpenAPI https://soup.video/openapi.json.
Optional Instant: only if we let Composio hold a company Soup key and bill their customers. That is a commercial agreement, not a code change. Default is user brings a Soup key so the runner still pays Soup directly.

Until the partnership is live, any Composio user can add Soup themselves as Custom MCP:

curl -X POST https://backend.composio.dev/api/v3.1/custom/toolkits \
  -H "x-api-key: $COMPOSIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Soup Director",
    "mcp_url": "https://soup.video/mcp",
    "auth_schemes": [{ "mode": "API_KEY" }],
    "user_id": "all"
  }'

Official MCP listings (after `/mcp` is deployed)

Place	Why	Submit
Official MCP Registry	Upstream. Glama / PulseMCP ingest it	`mcp-publisher` + server.json, DNS namespace `video.soup`
Smithery	Hosted catalog + scan	Paste `https://soup.video/mcp`; card at `/.well-known/mcp/server-card.json`
Claude Connectors	In-product directory	Needs OAuth 2.0 — custom connector works today with a URL
ChatGPT Apps	Consumer discovery	Apps SDK + OAuth; custom MCP on Business/Enterprise today
cursor.directory	Cursor community	GitHub repo + `.mcp.json`
Cursor Marketplace	Official Cursor plugins	Manual review

OpenAPI / HTTP catalogs

Spec: https://soup.video/openapi.json
Postman API Network — import the spec, publish a public workspace
Skip RapidAPI unless we want their 25% cut in front of Creem

Automation (needs webhooks next)

Zapier / Make / n8n / Pipedream want a “video ready” trigger. Today jobs are poll-only (GET /api/v1/generations/:id). Pipedream can still wrap the REST actions from OpenAPI. Webhooks are the Stage 1c follow-on.

Human directories (no new tech)

There’s An AI For That, Futurepedia, Fourth Feed, AIDEO, AlternativeTo, Product Hunt. Position as AI Director, not “another Kling wrapper.” Fourth Feed indexes llms.txt and the official MCP registry.

App stores

Google Play can list the site as a Trusted Web Activity once a PWA manifest exists. Apple will reject a thin WebView of soup.video. Not part of this MCP ship.

Guardrails

Studio graphs, node prompts, and other authors’ workflows stay off these surfaces. Listed on soup.video ≠ public_api.