How to integrate Wistia MCP with Claude Code

Manage your Wistia directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Wistia logoWistia
Api Key

Wistia is a video marketing platform for hosting, managing, and analyzing videos. Use it to publish polished video experiences and track audience engagement.

10 Tools

Introduction

Manage your Wistia directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Wistia with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Wistia to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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

The Wistia MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Wistia account. It provides structured and secure access to your media, folders, content, and performance analytics, so your agent can organize videos, import media, update content, search your account, and review performance on your behalf.

  • Media search and details: Have your agent search media, folders, channels, and channel episodes, then retrieve detailed information about specific media.
  • Video importing and updates: Let the agent import media from a public web address and update its name, description, tags, or still image.
  • Folder organization: Direct your agent to create, rename, describe, publish, update, or delete folders that organize your media.
  • Performance reporting: Instruct your agent to review account-wide or individual media performance over a selected date range.
  • Media archiving and cleanup: Have your agent archive or restore media, move restored items into a folder, and delete media you no longer need.

Connecting Wistia via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Wistia) for even more tool search precision. It's secure and reliable.

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, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Wistia account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['wistia'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http wistia-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Wistia. This URL will be used to connect Claude Code to Wistia.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Wistia
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Wistia MCP to Claude Code

bash
claude mcp add --transport http wistia-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (wistia-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Wistia MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your wistia-composio entry in the list
  • This confirms that Claude Code can now access Wistia tools

If everything is wired up, you should see your wistia-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Wistia

The first time you try to use Wistia tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Wistia
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Wistia authorization flow
  • Return to the terminal and start using Wistia through Claude Code

Once authenticated, you can ask Claude Code to perform Wistia operations in natural language. For example:

  • "List recent Wistia video engagement stats"
  • "Upload webinar recording to Wistia project"
  • "Create Wistia channel for product demos"

Complete Code

Here's the complete code to get you started with Wistia and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['wistia'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http wistia-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Wistia with Claude Code using Composio's MCP server. Now you can interact with Wistia directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Wistia operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Wistia operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

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

Create Folder

Create a Wistia folder for organizing media, optionally make it public, and optionally set the specified email as its owner.

Delete Folder

Delete a Wistia folder by hashed ID.

Delete Media

Delete one Wistia media item by hashed ID.

Get Analytics Summary

Return account-wide or single-media Wistia performance metrics for an inclusive start date and exclusive end date.

Get Media

Return detailed metadata, assets, folder placement, tags, and processing state for one Wistia media item.

Import Media from URL

Start importing a publicly reachable media URL into Wistia, optionally into a folder.

Search Content

Search the connected Wistia account for media, folders, subfolders, channels, and channel episodes by text and optional filters.

Set Media Archived State

Archive one or more media items, or restore archived media into a destination folder, and wait for Wistia's background job to finish.

Update Folder

Update a Wistia folder's name, description, public visibility, or anonymous transfer settings.

Update Media

Update a Wistia media item's name, description, tags, or still image reference.

FAQ

Frequently asked questions

With a standalone Wistia MCP server, the agents and LLMs can only access a fixed set of Wistia tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Wistia and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code 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 Wistia tools.

Yes, absolutely. You can configure which Wistia 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.

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 Wistia data and credentials are handled as safely as possible.

Start with Wistia.It takes 30 seconds.

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

Start building