Developers

Your video studio, inside your agent.

Bring Clipstorm into Claude, ChatGPT, Cursor, or your terminal. Ask for a short and it runs the whole line, then lands in your review queue to approve.

Get a keyAPI reference
Input
An idea, from your agent or a script.
Protocols
MCP (tools) and a REST API (OpenAPI).
Auth
A per-workspace API key, or OAuth for hosted connectors.
Output
A vertical short in your review queue.
Works with
Claude, ChatGPT, Cursor, and any MCP client.

Connect

Three steps to your first agent-made short

  1. 01

    Add the connector

    Add the MCP server to your agent, then click Authenticate to sign in and pick a workspace. No key to copy.

  2. 02

    Or use a key

    Prefer a key or the REST API? Create one in Settings → Agent access. It binds to one workspace and shows once.

  3. 03

    Ask for a short

    Describe the video. Your brand, voice, and sources are already set, so you never re-specify them.

# MCP with sign-in (no key): add it, then run /mcp and click Authenticate
claude mcp add clipstorm --transport http https://www.clipstorm.video/api/mcp

# MCP with a key (Claude Code, Cursor, any MCP client)
claude mcp add clipstorm --transport http https://www.clipstorm.video/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

# REST
curl https://www.clipstorm.video/api/v1/videos -H "Authorization: Bearer YOUR_KEY"

Capabilities

What your agent can do

  • Create a video from an idea; it renders and lands in your review queue.
  • List your videos and check any one's status and link.
  • Everything inherits the workspace brand, voice, writer, and sources.

Two ways in

MCP for agents, REST for scripts

MCP server
Tools for workspace setup, script authoring, creating videos, and scheduling, for agents like Claude and ChatGPT. Connect with a key or OAuth.
REST API
Versioned /api/v1 endpoints with an OpenAPI spec, for scripts and your own automations. Same contract as the tools.

Key Takeaways

What to remember

  • Drive Clipstorm from where you already work, over MCP or REST.
  • One key binds to one workspace; videos use that workspace's brand and voice.
  • Creating is async: the short arrives in your review queue, never auto-posts.

FAQ

Questions people ask

How do I connect Clipstorm to my AI agent?
Create an access key in Settings, then add the MCP server (or call the REST API) with it as a Bearer token. Claude, ChatGPT, Cursor, and any MCP client can connect.
What can the agent do?
It can set up your workspace (brand, voice, writer, sources), draft and submit scripts, create videos from an idea, and reschedule, publish, or cancel approved posts. Every video still lands in your review queue to approve in the Clipstorm app.
Is it MCP or a REST API?
Both. The MCP server exposes tools for setup, script authoring, creating videos, and scheduling; the REST API (with an OpenAPI spec) mirrors them for scripts and your own automations. They share one contract.
How does authentication work?
A per-workspace API key for terminals, or OAuth for hosted connectors. Either way the key is bound to one workspace, and videos inherit that workspace's brand, voice, and sources.
Does it use my brand and voice?
Yes. A video made from your agent uses the same brand kit, voice, writer, and sources as the Clipstorm app, so you never re-specify them in the prompt.

Keep reading

What Does Clipstorm Do?

The full line: script, voiceover, b-roll, captions, one review queue, then publishing to three platforms.

How to Automate Short-Form Video Posting

Set cadence and windows once, keep a queue of finished shorts flowing to your schedule.

Short-Form Video Guides

Practical guides to making vertical video with AI for YouTube, Instagram, and Facebook.

Now rolling

Connect your agent.

Create a key and bring Clipstorm into your chat in minutes.

Get a keyRead the guides