Wistia API

io.github.wistiaPublished by GitHub account wistiav0.1.2Updated Oct 24, 2026

Manage Wistia videos, channels, folders, captions, customizations, and analytics via MCP.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant manage Wistia videos, channels, folders, captions, customizations, and analytics via the Wistia API.

What you can do
This server lets an assistant work with content on the Wistia video platform through the Wistia API, covering videos, channels, folders, captions, customizations, and analytics. It is offered as a remote endpoint, so the assistant connects and calls the operations without installing a local package.
When to use it
Use it when you want to manage Wistia videos, channels, folders, captions, or customizations, or review video analytics, directly from a conversation. It suits workflows centered on the Wistia video platform.
Requirements
Network access to the remote endpoint and OAuth authentication. A Wistia API token in Bearer format must be supplied in the Authorization header; the token is obtained from the Wistia account API page. No local runtime or environment variables are needed.
Before you install
It requires a Wistia API token in the Authorization header, which is a sensitive credential to keep private. The server can manage videos, channels, folders, captions, and customizations, which may include creating, changing, or deleting content, so confirm the token's scope and the impact before use.

Installation

In SourceWeft

  1. Open Wistia API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wistia%2Fwistia-api-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wistia-api": {
      "type": "http",
      "url": "https://api.wistia.com/mcp/api"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.