mocop
Browse · Docs · Guide · Analyze

windpaint

MCP server by Windpaint · mcp

Windpaint generates images, video, audio and text through capabilities (image.generate, image.edit, mask.segment, media.upscale, video.generate, audio.speech, video.lipsync, text.llm). Every job is asynchronous and billed in credits; credits are held when a job starts and settled when it finishes. Check get_balance or the available_credits in estimates before large runs. Not every capability has a served model yet: check available. For a common task, check list_workflows first: a workflow (e.g. text-to-clip, product-to-ad) runs a whole multi-step pipeline from one form (run_workflow). Otherwise compose capabilities yourself. Typical capability flow: list_capabilities -> upload_asset (references, start frames, audio) -> estimate_cost -> generate (wait=true for images; wait=false then wait_for_job for video) -> download_asset. Inputs go in named slots (inputs: {slot: [asset_id, ...]}); list_capabilities shows each capability's slots. Pass asset ids from upload_asset or from ear…

Endpoint: https://mcp.windpaint.ai/mcp

Verification: observed. Source: crawl.

Capabilities (28)

  • list_capabilities
  • list_loras
  • estimate_cost
  • upload_asset
  • generate
  • get_job
  • wait_for_job
  • download_asset
  • cancel_job
  • list_recent_jobs
  • list_assets
  • get_balance
  • list_projects
  • create_project
  • update_project
  • list_items
  • get_item
  • create_item
  • list_takes
  • star_take
  • export
  • list_workflows
  • get_workflow
  • estimate_workflow
  • run_workflow
About · Contact · Privacy