# How to integrate Shotstack MCP with Google ADK

```json
{
  "title": "How to integrate Shotstack MCP with Google ADK",
  "toolkit": "Shotstack",
  "toolkit_slug": "shotstack",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/shotstack/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/shotstack/framework/google-adk.md",
  "updated_at": "2026-05-12T10:26:06.027Z"
}
```

## Introduction

This guide walks you through connecting Shotstack to Google ADK 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 Google ADK 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)
- [LangChain](https://composio.dev/toolkits/shotstack/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/shotstack/framework/ai-sdk)
- [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:
- Get a Shotstack account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Shotstack
- Build an agent that connects to Shotstack through MCP
- Interact with Shotstack using natural language

## What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.
Key features include:
- Gemini Integration: Native support for Google's Gemini models
- MCP Toolset: Built-in support for Model Context Protocol tools
- Streamable HTTP: Connect to external services through streamable HTTP
- CLI and Web UI: Run agents via command line or web interface

## 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 starting, make sure you have:
- A Google API key for Gemini models
- A Composio account and API key
- Python 3.9 or later installed
- Basic familiarity with Python

### 1. Getting API Keys for Google and Composio

Google API Key
- Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key.
- Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
- Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

### 2. Install dependencies

Inside your virtual environment, install the required packages.
What's happening:
- google-adk is Google's Agents Development Kit
- composio connects your agent to Shotstack via MCP
- python-dotenv loads environment variables
```bash
pip install google-adk composio python-dotenv
```

### 3. Set up ADK project

Set up a new Google ADK project.
What's happening:
- This creates an agent folder with a root agent file and .env file
```bash
adk create my_agent
```

### 4. Set environment variables

Save all your credentials in the .env file.
What's happening:
- GOOGLE_API_KEY authenticates with Google's Gemini models
- COMPOSIO_API_KEY authenticates with Composio
- COMPOSIO_USER_ID identifies the user for session management
```bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email
```

### 5. Import modules and validate environment

What's happening:
- os reads environment variables
- Composio is the main Composio SDK client
- GoogleProvider declares that you are using Google ADK as the agent runtime
- Agent is the Google ADK LLM agent class
- McpToolset lets the ADK agent call MCP tools over HTTP
```python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
```

### 6. Create Composio client and Tool Router session

What's happening:
- Authenticates to Composio with your API key
- Declares Google ADK as the provider
- Spins up a short-lived MCP endpoint for your user and selected toolkit
- Stores the MCP HTTP URL for the ADK MCP integration
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["shotstack"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
```

### 7. Set up the McpToolset and create the Agent

What's happening:
- Connects the ADK agent to the Composio MCP endpoint through McpToolset
- Uses Gemini as the model powering the agent
- Lists exact tool names in instruction to reduce misnamed tool calls
```python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Shotstack operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

### 8. Run the agent

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.
What's happening:
- adk run runs the agent in CLI mode
- adk web . opens a web UI for interactive testing
```bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
```

## Complete Code

```python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["shotstack"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Shotstack operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Shotstack with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Shotstack using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Shotstack tools
- Environment variables keep your credentials secure and separate from code
- Clear agent instructions reduce tool calling errors
- The ADK web UI provides an interactive interface for testing and development
You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

## 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)
- [LangChain](https://composio.dev/toolkits/shotstack/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/shotstack/framework/ai-sdk)
- [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 Google ADK?

Yes, you can. Google ADK 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)
