How to Use the Shotstack MCP in Claude

Q: How do I check the progress of a Shotstack job using Claude Desktop?

You use getrenderstatus. You just feed it the render ID returned by rendervideo, and your agent tells you if it's 'processing,' or if it finished.

Q: If I need to find assets from a specific Shotstack job, what tool do I use with Claude Desktop?

You call listassetsfromrender and pass the Job ID. This function pulls all associated files so you know exactly what's in that render output.

Q: Can Shotstack templates be managed using the Claude Desktop MCP Server?

Yep. You can list existing templates with listtemplates. If you need to adjust one, use createvideotemplate to save your changes and make it available for future jobs.

Q: Do I need to manage multiple renders when using Shotstack with Claude Desktop?

No. You can check the entire run history by calling listrecentrenders. This gives you a clear overview of all previous job IDs and their outcomes.

Generate personalized video ads and assets using your local Claude Desktop agent.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Shotstack MCP to Claude Desktop

Create your Vinkius account to connect Shotstack to Claude Desktop — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Shotstack with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Control the Video Pipeline with MCP Server

You start a render job by calling `render_video`. The tool immediately returns a unique ID. From that ID, you can check the status using `get_render_status` until the content is finished. Once complete, you pull all resulting files through `list_assets_from_render`. This lets your agent access every single asset created for that specific job.

Manage Assets and Templates

Need to get media into the system? Use `ingest_media_source` to upload or fetch any source file. You can also check what's already available with `list_hosted_assets`. This helps keep your local development process clean. Before you render, review the options using `list_templates`. If a template needs tweaking, call `create_video_template` to save your edits as a reusable starting point.

Check Render History and Sources

`list_recent_renders` gives you an immediate view of everything that ran. This history keeps track of job IDs so you don't lose context. You can also see every source file uploaded via `list_ingested_sources`. It’s a quick way to verify that all the necessary images and videos are ready for rendering.

Setup guide

Set up Shotstack MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Shotstack MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Shotstack MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under shotstack-mcp.

json

{
  "mcpServers": {
    "shotstack-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Shotstack. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Shotstack now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Shotstack MCP in Claude Desktop

You use `get_render_status`. You just feed it the render ID returned by `render_video`, and your agent tells you if it's 'processing,' or if it finished.

You call `list_assets_from_render` and pass the Job ID. This function pulls all associated files so you know exactly what's in that render output.

Yep. You can list existing templates with `list_templates`. If you need to adjust one, use `create_video_template` to save your changes and make it available for future jobs.

The server manages media source files. Specifically, you're interacting with uploaded assets via `ingest_media_source` and checking them through `list_ingested_sources`.

No. You can check the entire run history by calling `list_recent_renders`. This gives you a clear overview of all previous job IDs and their outcomes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript