How to Use the Wistia MCP in Claude Code

Q: How can I automate video uploads with Claude Code and Wistia?

You use the uploadvideoviaurl tool in your script, passing the URL, project ID, and name. This is perfect for CI/CD pipelines where you need to programmatically host content.

Q: Can I list all Wistia assets using Claude Code?

Yes. You run listwistiamedias in your terminal script, which gives you a stream of every media asset ID and name in your entire account.

Q: If I run a cleanup script with Claude Code, will it delete my projects?

Only if the script executes deletewistiaproject. All other read or update calls are non-destructive. Always test deletion in staging first.

Q: How do I get a full project inventory using Claude Code and Wistia?

First, call listwistiaprojects to get the IDs. Then, you can loop through those IDs calling getprojectdetails for every single one.

Run headless Wistia automation scripts with Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Wistia MCP to Claude Code

Create your Vinkius account to connect Wistia to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Wistia with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Manage project lifecycles

Start a new campaign folder using `create_new_project` and immediately capture the resulting project ID. You can then pass this ID to subsequent tools for targeted actions. When your video content is retired, pipe the command through `delete_wistia_project`. This executes the deletion of the whole Wistia project structure from a script.

Batch process and update assets

To ingest external videos into a CI/CD pipeline, use `upload_video_via_url`, passing the source URL to your shell script. This makes automating video hosting straightforward. For cleanup or standardization, call `update_media_metadata`. You pass the hashed ID and the required JSON payload directly from your terminal script.

Gather comprehensive analytics

Run a scheduled job that calls `get_engagement_statistics` for all active videos. This pulls raw viewer data that you can then pipe into other services or log files. Need project context? Run `list_wistia_projects` first, and then loop through the resulting IDs to call `get_project_details` for each one.

Setup guide

Set up Wistia MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see wistia-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Wistia transactions." It will automatically discover and invoke the available Wistia tools.

Terminal

claude mcp add --transport http wistia-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Wistia MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "wistia-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Wistia. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Wistia now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Wistia MCP in Claude Code

You use the `upload_video_via_url` tool in your script, passing the URL, project ID, and name. This is perfect for CI/CD pipelines where you need to programmatically host content.

Yes. You run `list_wistia_medias` in your terminal script, which gives you a stream of every media asset ID and name in your entire account.

This server touches engagement and metadata. Your scripts access viewer statistics, project details, and asset attributes for your Wistia content.

Only if the script executes `delete_wistia_project`. All other read or update calls are non-destructive. Always test deletion in staging first.

First, call `list_wistia_projects` to get the IDs. Then, you can loop through those IDs calling `get_project_details` for every single one.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.