mcpField
S
Short Video Agent Kit

Short Video Agent Kit

Local
github.comAI & Agents3Updated 2w ago

About Short Video Agent Kit

Short Video Agent Kit is an agent-oriented CLI and MCP toolkit for short-form video generation across several providers. It builds provider-specific payloads and defaults to dry runs, with live generation requiring explicit opt-in.

Key features

  1. 01One interface for multiple providers
  2. 02Build and inspect provider payloads
  3. 03Dry-run by default
  4. 04Generate video with explicit opt-in
  5. 05Check connection status and privacy boundaries

Use cases

  1. 01Prepare video requests for different providers
  2. 02Inspect payloads before generation
  3. 03Review plans before paid provider calls

MCP support

The MCP server exposes tools for provider status, privacy audits, payload building, and video generation. Generation defaults to dry-run; live calls require explicit opt-in.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"short-video-agent-kit": {
"command": "npx",
"args": [
"-y",
"short-video-agent-kit"
],
"env": {
"SHORT_VIDEO_DRY_RUN": "<SHORT_VIDEO_DRY_RUN>",
"OPENAI_API_KEY": "<OPENAI_API_KEY>",
"GEMINI_API_KEY": "<GEMINI_API_KEY>",
"XAI_API_KEY": "<XAI_API_KEY>"
}
}
}
}
Run commandnpx -y short-video-agent-kit
Environment variables to set
SHORT_VIDEO_DRY_RUNSet to false only when the agent should call paid video providers. Defaults to dry-run behavior.
OPENAI_API_KEYSecretOptional API key for OpenAI/Sora provider calls.
GEMINI_API_KEYSecretOptional API key for Gemini Veo provider calls.
XAI_API_KEYSecretOptional API key for xAI/Grok provider calls.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmshort-video-agent-kit0.1.7

Tools

5

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
clientstringNo
response_formatenumNojson | markdown

Details

From the project README

Short Video Agent Kit

Short Video Agent Kit
One agent-first CLI + MCP for short-form AI video.
Sora · Veo · xAI · Seedance — dry-run by default, paid generation when explicitly enabled.

npm version npm downloads License MIT Built for MCP

GitHub stars CI status Part of the Delx agent stack Category

⭐ If this agent-first tool helps your workflow, please star the repo. Stars make this tooling easier for other builders to discover and help Delx keep shipping open infrastructure.
🧱 Part of the Delx agent stack — 15 open-source MCP servers across body, reach and coordination.


HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y -p short-video-agent-kit short-video-mcp --http
# GET  http://127.0.0.1:3033/health
# POST http://127.0.0.1:3033/mcp   (sessionless)

Env: SHORT_VIDEO_MCP_HOST, SHORT_VIDEO_MCP_PORT, SHORT_VIDEO_MCP_TRANSPORT=http.

Provider-neutral short-form AI video toolkit for agents. It gives Codex, Claude, Cursor, Hermes, OpenClaw and other MCP clients one interface for building dry-run payloads and, when explicitly enabled, generating vertical video through Sora/OpenAI, Gemini Veo, xAI/Grok and Seedance/PiAPI-style providers.

Use it when an agent needs one safe interface for prompt-to-video payload validation and optional paid generation across multiple providers.

Why It Is Agent-First

Video generation can be expensive and prompt-sensitive. This package makes agents start with safe steps:

  • inspect provider readiness
  • return privacy boundaries
  • build payloads without spending credits
  • require --live or SHORT_VIDEO_DRY_RUN=false before provider calls
  • keep prompts and outputs in local user-controlled paths

Install

npm install -g short-video-agent-kit

Or run directly:

npm exec --yes --package=short-video-agent-kit -- short-video-agent-kit doctor

Quickstart

No API key needed to try it — generation is dry-run by default, so the kit returns the exact provider-neutral plan it would send without spending a credit.

Build a Sora plan for an 8-second vertical teaser:

short-video-agent-kit generate \
  --provider openai_sora \
  --prompt "Vertical 8-second product teaser for a minimalist water bottle, soft studio light, slow dolly-in" \
  --output ./output/teaser.mp4

Real output (no provider call, no credits spent):

{
  "ok": true,
  "dry_run": true,
  "next_step": "Pass --live or set SHORT_VIDEO_DRY_RUN=false to call the provider API.",
  "provider": "openai_sora",
  "endpoint": "POST /v1/videos",
  "payload": {
    "model": "sora-2",
    "prompt": "Vertical 8-second product teaser for a minimalist water bottle, soft studio light, slow dolly-in",
    "seconds": "8",
    "size": "720x1280"
  }
}

Same prompt, different provider — the plan re-targets the endpoint and parameter shape for you. payload returns just the plan (no dry_run wrapper):

short-video-agent-kit payload --provider gemini_veo --prompt "Same teaser, 9:16, cinematic"
{
  "provider": "gemini_veo",
  "endpoint": "POST /models/{model}:predictLongRunning",
  "payload": {
    "instances": [
      {
        "prompt": "Same teaser, 9:16, cinematic"
      }
    ],
    "parameters": {
      "aspectRatio": "9:16",
      "durationSeconds": 8
    }
  }
}

Check which providers are wired up (keys are detected, never printed):

short-video-agent-kit doctor
{
  "ok": false,
  "dry_run": true,
  "providers": {
    "openai_sora": { "configured": false, "env_keys": ["OPENAI_API_KEY"], "models": ["sora-2"] },
    "gemini_veo": { "configured": false, "env_keys": ["GEMINI_API_KEY", "GOOGLE_API_KEY"], "models": ["veo-3.1-fast-generate-preview"] },
    "xai_grok": { "configured": false, "env_keys": ["XAI_API_KEY"], "models": ["grok-imagine-video", "grok-imagine-image"] },
    "seedance_piapi": { "configured": false, "env_keys": ["PIAPI_KEY", "SEEDANCE_API_KEY"], "models": ["seedance-2-fast-preview"] }
  },
  "output_dir": "./output",
  "next_steps": [
    "Set one provider key: OPENAI_API_KEY, GEMINI_API_KEY, XAI_API_KEY or PIAPI_KEY."
  ]
}

When you are ready to actually render, set a provider key and re-run generate with --live (or SHORT_VIDEO_DRY_RUN=false).

CLI

short-video-agent-kit manifest --client codex
short-video-agent-kit doctor
short-video-agent-kit privacy-audit
short-video-agent-kit payload --provider gemini_veo --prompt-file prompt.txt
short-video-agent-kit generate --provider openai_sora --prompt "Vertical product teaser" --output ./output/teaser.mp4
short-video-agent-kit generate --provider openai_sora --prompt-file prompt.txt --output ./output/teaser.mp4 --live

Supported providers:

  • openai_sora
  • gemini_veo
  • xai_grok
  • seedance_piapi

MCP

short-video-mcp

HTTP transport:

SHORT_VIDEO_MCP_TRANSPORT=http short-video-mcp

Hermes-style config:

mcp_servers:
  short_video:
    command: npx
    args: ["-y", "short-video-agent-kit"]
    sampling:
      enabled: false

Recommended first calls:

  1. short_video_connection_status
  2. short_video_privacy_audit
  3. short_video_build_payload
  4. short_video_generate

Agent Surfaces

ToolPurpose
short_video_agent_manifestInstall/runtime guidance for Codex, Claude, Cursor, Hermes and OpenClaw
short_video_connection_statusProvider readiness without API keys
short_video_privacy_auditPrompt, output and reference-asset boundaries
short_video_build_payloadProvider-specific payload without paid generation
short_video_generateDry-run by default, live only when explicitly requested

Copy-Paste Agent Prompt

Use short-video-agent-kit. First call short_video_connection_status and short_video_privacy_audit.
Build the payload before generation. Only set live=true if I explicitly confirm a paid provider call.

Configuration

Copy .env.example to .env and fill only the provider keys you plan to use. .env, output/ and .agent-data/ are ignored by Git.

Safety Model

  • Dry-run is the default.
  • API keys are never returned by tools.
  • Paid generation requires --live, MCP live=true, or SHORT_VIDEO_DRY_RUN=false.
  • Reference images must be user-owned or licensed.
  • Outputs are written to local paths controlled by the user.

Development

npm install
npm test
npm run check

📧 Contact & Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.