Short Video Agent Kit MCP Server

Provider-neutral short-form AI video toolkit for agents: Sora, Gemini Veo, xAI/Grok, Seedance. The short video agent kit mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

• 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

Its toolset

Everything the assistant can do here goes through one of these:

• openai_sora — gemini_veo
• xai_grok — seedance_piapi
• Dry — run is the default
• short_video_agent_manifest — Install/runtime guidance for Codex, Claude, Cursor, Hermes and OpenClaw
• short_video_connection_status — Provider readiness without API keys
• short_video_privacy_audit — Prompt, output and reference-asset boundaries
• short_video_build_payload — Provider-specific payload without paid generation
• short_video_generate — Dry-run by default, live only when explicitly requested

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at args on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 6 environment variables: OPENAI_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, XAI_API_KEY, PIAPI_KEY, SEEDANCE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Short Video Agent Kit's toolset — openai_sora, xai_grok, Dry and 5 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the short video agent kit mcp server does with a few real requests.