# How to integrate Shotstack MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Shotstack MCP with Vercel AI SDK v6", "toolkit": "Shotstack", "toolkit_slug": "shotstack", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/shotstack/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/shotstack/framework/ai-sdk.md", "updated_at": "2026-05-12T10:26:06.027Z" } ``` ## Introduction This guide walks you through connecting Shotstack to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Shotstack agent that can create a video slideshow from uploaded images, generate a branded video intro with logo, combine multiple video clips into one file through natural language commands. This guide will help you understand how to give your Vercel AI SDK 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. ## Also integrate Shotstack with - [OpenAI Agents SDK](https://composio.dev/toolkits/shotstack/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/shotstack/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/shotstack/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/shotstack/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/shotstack/framework/codex) - [OpenClaw](https://composio.dev/toolkits/shotstack/framework/openclaw) - [Hermes](https://composio.dev/toolkits/shotstack/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/shotstack/framework/cli) - [Google ADK](https://composio.dev/toolkits/shotstack/framework/google-adk) - [LangChain](https://composio.dev/toolkits/shotstack/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/shotstack/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/shotstack/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/shotstack/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Shotstack integration - Using Composio's Tool Router to dynamically load and access Shotstack tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SHOTSTACK_CREATE_TEMPLATE` | Create Template | Tool to create a new template for video editing. Use when you want to save a reusable timeline configuration as a template. Template changes do not retroactively affect past renders. | | `SHOTSTACK_CREATE_TEMPLATE2` | Create Template (v2) | Tool to save an Edit as a re-usable template. Templates can be retrieved and modified before rendering. Use when you want to create a template with merge fields for dynamic content. | | `SHOTSTACK_DELETE_INGESTED_MEDIA` | Delete Ingested Media | Tool to delete an ingested media asset. Use when you've confirmed the ingest ID and need to remove the file from Shotstack storage. | | `SHOTSTACK_DELETE_TEMPLATE2` | Delete Template | Tool to delete a specific Shotstack template by its ID. Use when you need to remove a template permanently. | | `SHOTSTACK_DELETE_WORKFLOW` | Delete Shotstack Workflow | Tool to delete a specific Shotstack workflow. Use when you need to permanently remove a workflow after confirming its ID. | | `SHOTSTACK_FETCH_SOURCE` | Fetch Source | Tool to fetch a remote media file and store it as a source asset. Operation is asynchronous — poll SHOTSTACK_GET_INGEST_STATUS or SHOTSTACK_INSPECT_MEDIA until the asset is ready before passing it to SHOTSTACK_RENDER_VIDEO or other downstream tools. Use when you need to ingest a file before rendering. | | `SHOTSTACK_GET_ASSETS` | Get Asset | Tool to fetch details of a hosted asset by its unique identifier. Use when you need to retrieve information about videos, images, audio files, thumbnails, or poster images hosted on Shotstack's CDN. | | `SHOTSTACK_GET_ASSETS_RENDER` | Get Assets by Render ID | Tool to retrieve hosted assets by render ID. Use when you need to fetch one or more files (video, thumbnail, poster image) generated by a specific render job. | | `SHOTSTACK_GET_RENDER_CALLBACK` | Get Render Callback | Tool to retrieve the webhook/callback URL configuration for a specific render job. Returns only callback settings (URL, method, headers), not render status or output URLs — use a separate render-status check to obtain final results. | | `SHOTSTACK_GET_RENDER_STATUS` | Get Render Status | Tool to retrieve the current status and details of a Shotstack render job by render ID. Use when polling a render until done or failed, typically after creating a render with SHOTSTACK_RENDER_VIDEO. | | `SHOTSTACK_GET_SOURCE` | Get Source Details | Tool to fetch the details of a specific source asset. Use when you need to inspect a source after uploading, check its status, or diagnose ingest/render failures—such as unsupported codecs, corrupt files, or bad URLs—before retrying. | | `SHOTSTACK_GET_TEMPLATE` | Get Template | Tool to retrieve details of a specific template. Use when you have the ID of an existing template and need its metadata. | | `SHOTSTACK_GET_TEMPLATE_BY_VERSION` | Get Template By Version | Tool to retrieve a template by template id and API version. Use when you need to fetch template details from a specific Edit API version. | | `SHOTSTACK_GET_UPLOAD_URL` | Get Upload URL | Tool to request a signed URL for direct file upload to Shotstack. Use when you need to upload a file to Shotstack storage. The response returns a signed URL that you use to upload the file using a PUT request with the binary file. | | `SHOTSTACK_INSPECT_MEDIA` | Inspect Media | Tool to inspect media metadata. Use before rendering to retrieve duration, resolution, frame rate, and format of an online media file — clip timecodes, trim points, and audio sync calculations depend on these values. Mixing assets without prior inspection can cause letterboxing, jitter, or audio sync issues in the final output. | | `SHOTSTACK_LIST_SOURCES` | List Sources | Tool to list all source assets. Use when you need to retrieve source entries with optional pagination. | | `SHOTSTACK_LIST_SOURCES2` | List Sources (with Environment) | Tool to list all ingested source files with environment selection. Use when you need to retrieve sources from stage (sandbox) or v1 (production) environment with optional pagination. | | `SHOTSTACK_LIST_TEMPLATES` | List Templates | Tool to list all Shotstack templates for the account. Use after creating or updating templates to view your available templates. | | `SHOTSTACK_LIST_TEMPLATES2` | List Templates with Environment | Tool to list all Shotstack templates for the specified environment. Use when you need to retrieve templates from a specific environment (stage or production). | | `SHOTSTACK_POST_UPLOAD` | Request Upload URL | Tool to request a signed URL for direct file upload. Use when you need to upload a file to Shotstack storage. The response returns a signed URL that expires in one hour. | | `SHOTSTACK_RENDER_VIDEO` | Render Video | Tool to initiate a new video render job. Use when you have defined a timeline and output settings and want to start rendering. | | `SHOTSTACK_TRANSFER_ASSET` | Transfer Asset | Tool to transfer a file from any publicly available URL to one or more Serve API destinations. Use when you need to copy a file from an external source to Shotstack's hosting service or other configured destinations. | | `SHOTSTACK_UPDATE_TEMPLATE` | Update Template | Tool to update an existing template by its ID. Use when you need to modify a template's name or edit configuration. Both name and complete template definition must be provided. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Shotstack MCP server is an implementation of the Model Context Protocol that connects your AI agent to Shotstack. It provides structured and secure access so your agent can perform Shotstack operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client 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 mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Shotstack-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["shotstack"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Shotstack tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to shotstack, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Shotstack tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["shotstack"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to shotstack, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); 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; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Shotstack agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Shotstack MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/shotstack/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/shotstack/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/shotstack/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/shotstack/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/shotstack/framework/codex) - [OpenClaw](https://composio.dev/toolkits/shotstack/framework/openclaw) - [Hermes](https://composio.dev/toolkits/shotstack/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/shotstack/framework/cli) - [Google ADK](https://composio.dev/toolkits/shotstack/framework/google-adk) - [LangChain](https://composio.dev/toolkits/shotstack/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/shotstack/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/shotstack/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/shotstack/framework/crew-ai) ## Related Toolkits - [Youtube](https://composio.dev/toolkits/youtube) - YouTube is a leading video-sharing platform for uploading, streaming, and discovering content. It empowers creators and businesses to reach global audiences and monetize their work. - [Amara](https://composio.dev/toolkits/amara) - Amara is a collaborative platform for creating and managing subtitles and captions for videos. It helps make content accessible and multilingual for global audiences. - [Cats](https://composio.dev/toolkits/cats) - Cats is an API with a huge library of cat images, breed data, and cat facts. It makes finding adorable cat photos and trivia effortless for your apps and users. - [Chatfai](https://composio.dev/toolkits/chatfai) - Chatfai is an AI platform that lets users talk to AI versions of fictional characters from books, movies, and games. It offers an engaging, interactive experience for fans to chat, roleplay, and explore creative dialogues. - [Cincopa](https://composio.dev/toolkits/cincopa) - Cincopa is a multimedia platform for uploading, managing, and customizing videos, images, and audio. It helps you deliver engaging media experiences with robust APIs and flexible integrations. - [Dungeon fighter online](https://composio.dev/toolkits/dungeon_fighter_online) - Dungeon Fighter Online (DFO) is an arcade-style, side-scrolling action RPG packed with dynamic combat and progression. Play solo or with friends to battle monsters, complete quests, and upgrade your characters. - [Elevenlabs](https://composio.dev/toolkits/elevenlabs) - Elevenlabs is an advanced AI voice generation platform for lifelike, multilingual speech synthesis. Perfect for creating natural voices for videos, apps, and business content in seconds. - [Elevenreader](https://composio.dev/toolkits/elevenreader) - Elevenreader is an AI-powered text-to-speech service by ElevenLabs that converts written content into lifelike audio. It enables fast, natural audio generation from any text. - [Epic games](https://composio.dev/toolkits/epic_games) - Epic Games is a leading video game publisher and digital storefront, known for Fortnite and Unreal Engine. It lets gamers access, manage, and purchase games all in one place. - [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools. - [Giphy](https://composio.dev/toolkits/giphy) - Giphy is the largest online library for searching and sharing GIFs and stickers. Instantly add vibrant animated content to your apps, chats, and workflows. - [Headout](https://composio.dev/toolkits/headout) - Headout is a global platform for booking travel experiences, tours, and entertainment. It helps users discover and secure activities at top destinations, all in one place. - [Imagekit io](https://composio.dev/toolkits/imagekit_io) - ImageKit.io is a cloud-based media management platform for image and video delivery. Instantly optimize, transform, and deliver visuals globally via a lightning-fast CDN. - [Listennotes](https://composio.dev/toolkits/listennotes) - Listennotes is a powerful podcast search engine with a massive global database. Discover, search, and curate podcasts from around the world in seconds. - [News api](https://composio.dev/toolkits/news_api) - News api is a REST API for searching and retrieving live news articles from across the web. Instantly access headlines, coverage, and breaking stories from thousands of sources. - [RAWG Video Games Database](https://composio.dev/toolkits/rawg_video_games_database) - RAWG Video Games Database is the largest video game discovery and info service. Instantly access comprehensive details, ratings, and release dates for thousands of games. - [Seat geek](https://composio.dev/toolkits/seat_geek) - SeatGeek is a live event platform offering APIs for concerts, sports, and theater data. Instantly access events, venues, and performers info for smarter ticketing and discovery. - [Spotify](https://composio.dev/toolkits/spotify) - Spotify is a streaming service for music and podcasts with millions of tracks from artists worldwide. Enjoy personalized playlists, recommendations, and seamless listening across all your devices. - [Ticketmaster](https://composio.dev/toolkits/ticketmaster) - Ticketmaster is a global platform for event discovery, ticket sales, and live entertainment management. Get real-time access to events and streamline ticketing for fans and organizers. - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Shotstack MCP? With a standalone Shotstack MCP server, the agents and LLMs can only access a fixed set of Shotstack tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Shotstack and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Shotstack tools. ### Can I manage the permissions and scopes for Shotstack while using Tool Router? Yes, absolutely. You can configure which Shotstack scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Shotstack data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)