|Docs

MCP and Supercomputer

Sume developer tools are designed around one boundary: the public API is the source of truth, and wrappers stay thin.

Tooling layers

  1. Public API: workspace-scoped HTTP endpoints.
  2. CLI: shell-friendly wrapper around the public API.
  3. MCP: model-facing wrapper around the same public API.
  4. Supercomputer tools: app-integrated tools with server-injected workspace context.

Asset Library use case

An agent can search scenes, select one asset, and reuse its media metadata in a later generation or analysis workflow.

sume assets search "woman looking at camera hook" --limit 5 --json
sume assets get <asset_id> --json

Supercomputer should not ask the user for a workspace id. Workspace context is resolved by the authenticated app session.