How to integrate Shotstack MCP with LangChain

Connect LangChain to Shotstack MCP. Create a video slideshow from uploaded images, generate a branded video intro with logo, and more using natural language, with authentication handled for you.

Shotstack logoShotstack
Api Key

Shotstack is a cloud platform for programmatically generating videos, images, and audio. Automate creative content production at scale with flexible RESTful APIs.

23 Tools

Introduction

This guide walks you through connecting Shotstack to LangChain using the Composio tool router. By the end, you'll have a working Shotstack agent that can render videos, check render status, create and update templates, upload and inspect media, and fetch generated assets through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Shotstack account through Composio's Shotstack MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Shotstack with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Shotstack project to Composio
  • Create a Tool Router MCP session for Shotstack
  • Initialize an MCP client and retrieve Shotstack tools
  • Build a LangChain agent that can interact with Shotstack
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Shotstack MCP server, and what's possible with it?

The Shotstack MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Shotstack account. It provides structured and secure access to powerful video, image, and audio automation features—so your agent can create dynamic media content, edit assets, manage rendering jobs, and retrieve results at scale on your behalf.

  • Automated video and image generation: Let your agent assemble and render videos or images programmatically using templates, custom assets, and dynamic data.
  • Media editing and composition: Enable your agent to cut, trim, overlay, and combine media clips—adding text, transitions, or audio tracks as needed.
  • Batch rendering and job management: Have your agent submit, track, and manage multiple rendering jobs, so you can scale creative automation for campaigns or client deliverables.
  • Asset and template organization: Allow your agent to upload, list, and organize reusable templates and media assets, keeping your creative workflow streamlined.
  • Result retrieval and download: Automatically fetch completed renders and download media files, making finished content instantly available for distribution or review.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Shotstack functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Shotstack tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['shotstack']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Shotstack tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Shotstack tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "shotstack-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Shotstack MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Shotstack tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Shotstack related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Shotstack and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['shotstack']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "shotstack-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Shotstack related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Shotstack through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Shotstack action and event your agent gets out of the box.

Create Template

Create a named Shotstack template from timeline and output settings for reuse in media editing and rendering.

Create Template (v2)

Tool to save an Edit as a re-usable template.

Delete Ingested Media

Delete an ingested source file from the production Ingest API by its ingest ID.

Delete Template

Delete a Shotstack template by ID in the stage environment.

Delete Shotstack Workflow

Tool to delete a specific Shotstack workflow.

Fetch Source

Queue a remote media file for ingestion as a source asset in the production Ingest API.

Get Asset

Retrieve details of a hosted asset by asset ID in the Shotstack staging environment, including videos, images, audio files, thumbnails, and poster images.

Get Assets by Render ID

Retrieve hosted assets by render ID in the Shotstack staging environment, including files such as video, thumbnail, and poster images.

Get Render Callback

Request callback details for a specific render job, including the callback URL and delivery status, attempts, response and last-attempt time.

Get Render Status

Retrieve the status and details of a Shotstack render job by render ID in the selected environment.

Get Source Details

Retrieve details and status of a source asset by ID from the production Ingest API.

Get Template

Retrieve a template's details and metadata by ID from the Shotstack staging environment.

Get Template By Version

Tool to retrieve a template by template id and API version.

Get Upload URL

Tool to request a signed URL for direct file upload to Shotstack.

Inspect Media

Tool to inspect media metadata.

List Sources

Request a list of ingested source assets from the production Ingest API, with optional pagination parameters.

List Sources (with Environment)

Tool to list all ingested source files with environment selection.

List Templates

List Shotstack templates for the account in the stage environment.

List Templates with Environment

Tool to list all Shotstack templates for the specified environment.

Request Upload URL

Request a signed URL for direct file upload to the Shotstack staging environment.

Render Video

Tool to initiate a new video render job.

Transfer Asset

Transfer a file from a publicly available URL to one or more production Serve API destinations, including Shotstack hosting or other configured destinations.

Update Template

Update a stage-environment template by ID, providing both its name and complete edit configuration.

FAQ

Frequently asked questions

Start with Shotstack.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Shotstack tool your agent needs.Free to start.

Start building