3,400+ MCP servers ready to use
Vinkius

Shotstack MCP Server for VS Code CopilotGive VS Code Copilot instant access to 10 tools to Create Video Template, Get Hosted Asset Details, Get Render Status, and more

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this App Connector for VS Code Copilot

The Shotstack app connector for VS Code Copilot is a standout in the Industry Titans category — giving your AI agent 10 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Shotstack and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "shotstack": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Shotstack
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Shotstack MCP Server

Connect your Shotstack account to any AI agent and take full control of your high-volume video editing and media orchestration through natural conversation. Shotstack provides a powerful API-first platform for rendering videos, managing cloud templates, and ingesting assets directly from your chat interface.

GitHub Copilot Agent mode brings Shotstack data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Video Rendering Orchestration — Trigger professional video renders from JSON-based templates or custom edits programmatically.
  • Template Lifecycle Management — Create and monitor cloud-based video templates to ensure consistent automated outputs directly from the AI interface.
  • Asset & Ingest Control — Ingest source media and manage your hosted assets to maintain a clear overview of your production resources.
  • Render Intelligence — Retrieve real-time render statuses and detailed metadata to track the progress of your video pipeline via natural language.
  • Operational Monitoring — List available renders, templates, and source assets using simple AI commands to ensure your production is optimized.

The Shotstack MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 10 Shotstack tools available for VS Code Copilot

When VS Code Copilot connects to Shotstack through Vinkius, your AI agent gets direct access to every tool listed below — spanning video-rendering, cloud-api, media-automation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_video_template

Save an edit as a reusable template

get_hosted_asset_details

Get details for a hosted file

get_render_status

Check the status of a render job

ingest_media_source

Upload or fetch a source asset

list_assets_from_render

) associated with a specific job ID. Find all files created by a specific render

list_hosted_assets

List all hosted media files

list_ingested_sources

List all ingested media sources

list_recent_renders

List recent render history

list_templates

List available video templates

render_video

Returns a render ID. Start a new video render job

Connect Shotstack to VS Code Copilot via MCP

Follow these steps to wire Shotstack into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Shotstack

Ask Copilot: "Using Shotstack, help me...". 10 tools available

Why Use VS Code Copilot with the Shotstack MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Shotstack through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Shotstack + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Shotstack MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Shotstack in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Shotstack immediately.

01

"Check the status of my latest video render in Shotstack."

02

"List all video templates in my Shotstack account."

03

"List all hosted assets in my Shotstack Serve account."

Troubleshooting Shotstack MCP Server with VS Code Copilot

Common issues when connecting Shotstack to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Shotstack + VS Code Copilot FAQ

Common questions about integrating Shotstack MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.