mcp.film

mcp.film / Editing & Post / Shotstack MCP

Shotstack MCP

OfficialRemoteby Shotstackfreemiumverified Aug 28, 2026

Cloud video editing, Studio previews, and template rendering over Shotstack's hosted MCP.

What it does

Shotstack's MCP server exposes its cloud video editing API to agents: render Edit JSON timelines, save reusable templates, render merge-field variants, poll render status, and open an interactive Studio canvas so a human can preview a cut before it burns credits. For filmmaker-agents it is the programmable render farm lane — fast campaign variants, data-driven video, and cloud assembly jobs that should not depend on a local NLE being open. A `get_shotstack_guide` tool ships the Edit JSON conventions so the agent authors valid timelines without guessing at the schema.

Connect

Remote endpoint (Streamable HTTP)
https://mcp.shotstack.io/

Remote headers required: x-api-key. Use the local stdio command when your client cannot attach custom MCP headers.

Claude Code
claude mcp add --transport http shotstack https://mcp.shotstack.io
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "shotstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.shotstack.io/",
        "--header",
        "x-api-key:YOUR_KEY"
      ]
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "shotstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.shotstack.io/",
        "--header",
        "x-api-key:YOUR_KEY"
      ]
    }
  }
}
Auth: oauth — https://app.shotstack.io — OAuth is the default; headless clients skip it by sending the same key as an x-api-key header

Tools you'll see

studiorender_videoget_render_statuscreate_studio_linkget_shotstack_guidecreate_templatelist_templatesget_templaterender_templatedelete_template

Field notes

Rebuilt around the hosted endpoint since the last check: npm @shotstack/shotstack-mcp-server 1.1.0 now carries a deprecation notice — "This local stdio server is deprecated. Use the hosted Shotstack MCP server instead" — so the old `-e SHOTSTACK_API_KEY -- npx` recipe listed here is dead and stdio-only clients must bridge through mcp-remote. Shotstack calls the hosted server beta and warns tools may change without notice. The endpoint answers an unauthenticated probe with 401, alive and gated. There is still no readable source: npm points at github.com/shotstack/shotstack-mcp-server, which 404s to both an anonymous fetch and the GitHub API, so there are no stars or commits to judge — trust the vendor docs and the live endpoint, not GitHub signals. Agents should call `get_shotstack_guide` before composing Edit JSON, prefer `studio` over `render_video` when a human is watching, and pass real public HTTPS asset URLs rather than inventing them.

Pairs well with