How do I find my Wistia API Token?

Log in to Wistia, navigate to **Account Settings** > **API**, and generate a new token or copy an existing one from the list.

What is a 'hashed_id'?

A `hashed_id` is a unique, short identifier assigned to every video and project in Wistia, typically found in the URL when viewing an asset.

INSTANT PLUG AND PLAY

Wistia MCP Server for CrewAIGive CrewAI instant access to 9 tools to Create Project, Get Account Analytics, Get Project Details, and more

Name: Wistia
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Wistia through Vinkius, pass the Edge URL in the `mcps` parameter and every Wistia tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Wistia app connector for CrewAI is a standout in the Industry Titans category — giving your AI agent 9 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Wistia Specialist",
    goal="Help users interact with Wistia effectively",
    backstory=(
        "You are an expert at leveraging Wistia tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Wistia "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Wistia MCP Server

Connect your Wistia video marketing account to any AI agent to automate your media library management and performance monitoring through natural conversation. Wistia provides a premier platform for B2B video hosting, delivery, and detailed engagement tracking.

When paired with CrewAI, Wistia becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Wistia tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Media Orchestration — List and retrieve detailed metadata for your videos (medias), including titles, descriptions, and statuses.
Project Management — Organize your content by creating and managing hierarchical projects (folders) directly from the AI interface.
Engagement Analytics — Retrieve real-time performance stats for specific videos or get an aggregated overview of your account-wide metrics.
Metadata Control — Programmatically update video details and manage captions to ensure your media library is always optimized.
Asset Delivery — Fetch player configurations and thumbnail URLs to streamline content distribution across your digital channels.

The Wistia MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 9 Wistia tools available for CrewAI

When CrewAI connects to Wistia through Vinkius, your AI agent gets direct access to every tool listed below — spanning video-hosting, video-marketing, engagement-analytics, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_project

Create a new project

get_account_analytics

Get account-wide stats

get_project_details

Get metadata for a project

get_video_details

Get metadata for a video

get_video_stats

Get video analytics

list_projects

List your Wistia projects

list_video_captions

List captions for a video

list_videos

List all videos (medias)

update_video_details

Modify video metadata

Connect Wistia to CrewAI via MCP

Follow these steps to wire Wistia into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from Wistia

Why Use CrewAI with the Wistia MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Wistia through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Wistia + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Wistia MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Wistia for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Wistia, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Wistia tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Wistia against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Wistia in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Wistia immediately.

"List all active projects in my Wistia account."

"Show the engagement stats for video ID 'vid123'."

Troubleshooting Wistia MCP Server with CrewAI

Common issues when connecting Wistia to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Wistia + CrewAI FAQ

Common questions about integrating Wistia MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.