PricingSign In

    Automate media with MCP or REST

    Developers connect Claude, Cursor, or internal workers to Kubeez through MCP, or call REST directly. The same credit ledger backs automation and the web UI—no duplicate billing systems.

    Primitives you will call

    • generate_media + status

      Start asynchronous video or image jobs and poll until assets are ready.

    • generate_music

      Kick off full song renders with predictable parameter blocks (model ids from get_models).

    • Models & estimates

      Query model catalogs, balances, and credit estimates before heavy jobs.

    • Reference uploads

      Use upload helpers for image-to-video and image-to-image pipelines.

    How it works

    1. Authorize OAuthConnect through the documented consent URL so tokens map to the right workspace.
    2. Discover modelsCall get_models to keep integrations aligned with the live catalog.
    3. Orchestrate jobsSubmit work, poll statuses, and hydrate your CMS or DAM with returned URLs.
    MCP clients especially benefit from structured tool metadata published at kubeez.com/docs/tools-* without scraping HTML.
    Get started free

    FAQ

    Where is the MCP endpoint?
    https://mcp.kubeez.com/mcp — see /docs/overview for setup.
    Is there a Swagger for REST?
    Yes—browse /docs/api-overview for base URL, auth headers, and interactive docs.
    Can we dry-run costs?
    Use get_generation_estimate and get_balance before submitting long renders.