Shotstack

io.shotstackPublished by shotstack.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Generate, edit, and render videos via the Shotstack video editing API.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Shotstack is a remote MCP server that lets an assistant generate, edit and render videos through the Shotstack video editing API.

What you can do
Create and edit video projects through the Shotstack video editing API, describing edits in conversation and having the assistant carry them out. Render finished videos from those projects. The server exposes no tool list, so the exact set of operations is not documented here; the description only states video generation, editing and rendering.
When to use it
Useful when you want an assistant to build or modify video content programmatically through Shotstack, for example assembling clips or producing rendered output, without writing API calls yourself.
Requirements
A remote MCP endpoint at reached over streamable HTTP. OAuth authentication is required, so a Shotstack account and authorization are needed. No environment variables or headers are declared.
Before you install
Rendering and editing act on your Shotstack account and may consume paid API or rendering quota, so check your plan and costs first. The server can create and change video projects and render output, which are write actions. OAuth grants the server access to your Shotstack account; review the scopes before authorizing.

Installation

In SourceWeft

  1. Open Shotstack in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.shotstack%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "shotstack": {
      "type": "http",
      "url": "https://mcp.shotstack.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.