Cospark for Claude

Claude writes the ad. Cospark shoots it.

Claude is already good at the script. Connect Cospark and the same conversation produces the footage, the voiceover, and a cut you can open in an editor.

Most of an ad never makes it out of the chat. Claude writes a hook, three variants, a shot list — and then the work stops, because turning any of it into footage means leaving for a different tool and rebuilding the context you just spent twenty minutes creating.

Cospark closes that gap. It is a remote MCP server, so Claude keeps the brief, the brand voice, and the reasoning it already did, and calls generation tools directly. The script it just wrote becomes a 9:16 talking-head clip. The clip lands on a real timeline you can open in the browser, edit by hand, or hand back to Claude for another pass.

In Claude Code that matters twice over, because your product copy, landing page, and brand files are already in the repo Claude is reading. The reference for the ad and the tool that makes the ad are finally in the same place.

Two ways in

The CLI takes one command. Desktop takes a URL.

  1. 01

    Claude Code

    Add the server from any terminal. Claude Code stores it in your user config, so it is available in every project.

    terminal
    claude mcp add --transport http cospark https://api.cospark.so/api/mcp/cospark
  2. 02

    Authenticate

    Run /mcp inside Claude Code, select Cospark, and finish the sign-in in your browser. The token is stored locally and refreshed for you — there is no API key to paste or rotate.

    claude code
    /mcp
  3. 03

    Claude Desktop and claude.ai

    Open Settings → Connectors → Add custom connector, paste the Cospark URL, and authorize it in the browser window that opens. Custom connectors are available on paid Claude plans.

    connector url
    https://api.cospark.so/api/mcp/cospark

What this looks like in practice

Same conversation, now with footage in it.

Script to finished cut

Ask Claude for three hooks, pick one, and tell it to shoot the winner. It generates the talking-head clip, polls the run, and gives you back a link to the workspace.

  • generate_ugc_video
  • get_ugc_video_status
  • create_workspace

Ads from the repo you are in

Claude Code can read your product page copy, pricing, and screenshots, then use them as the brief — no re-explaining the product to a second tool.

  • upload_media
  • generate_video_with_references
  • compose_timeline

Revisions without a re-render

Tell Claude the second beat drags. It reads the timeline, trims the item by ID against the current revision, and leaves the rest of the cut untouched.

  • read_timeline
  • edit_timeline
  • inspect_media

Worth knowing

Two details that change how the session feels.

Nothing blocks

Video tools return a run ID immediately and Claude polls for the result, so a four-minute render does not freeze the conversation. You can keep working while it finishes.

Your account, your plan

Generations run against the Cospark account you signed in with, at your own plan limits. Anything Claude makes shows up in your workspace list in the browser.

Questions and answers

Specific to Claude.

Ready to turn your next product into ads ready to test?

Start with one product or brief. Cospark turns it into a complete, editable campaign you can launch, learn from, and iterate on.