The GTM MCP Directory
Directory / Video Prospecting / Wistia

Wistia

Official MCP Free to start Video Prospecting RESEARCHED Checked 2026-09-07
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: wistia.com · entry id 08-wistia · source 08-video-prospecting.md line 281

What it does
A video hosting and marketing platform for business (player, channels, webinars, analytics, lead capture) with a REST API; sales and marketing teams use it for hosted demo and follow-up video with per-viewer engagement data.
AI features, separated from automation with an AI label on it
Not the product's centre; the vendor markets analytics and lead-gen automation. The MCP server is a connectivity layer over the existing API (media, folders, channels, webinars, captions, customizations, tags, analytics, stats, sharing, remix and account toolsets), not an AI feature.
RevOps role
A hosted-video layer under sales follow-up and marketing; the MCP gives an agent read and write over media and viewer analytics, which is engagement signal, not video generation.
MCP server
Status bucket
Official MCP
Auth
oauth or an access token as an Authorization Bearer header. The docs state "If you use an access token you need to add the Authorization: Bearer <token> in your configuration." An optional toolsets query parameter (for example ?toolsets=media,analytics) restricts the exposed tools; "By default the server exposes every tool it has, which is a lot of them." The docs also state "Currently, the Wistia MCP server is only available to owners and managers of an account."
Parsed URLs
2 found in the mcp_url field
Endpoint probe
not probed yet

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-09-07 and the MCP URL has not been probed live yet.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://api.wistia.com/mcp/api (docs: https://docs.wistia.com/docs/mcp-server-guide; registry name io.github.wistia/wistia-api-mcp)

What this server exposes

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Free to start
Can a solo operator reach it
Yes, without talking to anyone

api_gate, verbatim from the file:

free - the pricing page lists Free at $0/month ("25 GB storage", "1 user only", "Wistia Branding"), Business $79/month, Business + Lead gen $329/month and Enterprise custom; the MCP guide says custom connectors work across Free, Pro, Max, Team and Enterprise plans, and the API docs authenticate with an account access token with no plan condition stated.

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

On GitHub

github.com/wistia tied to the vendor by rule 3, account website https://wistia.com has the vendor's domain, confidence strong

Public repositories
58, forks excluded, as read on 2026-09-08
Mention MCP
1 of them
Look like CLIs
3 of them
Latest push
2026-09-08

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
wistia-typescript-sdkSDK02026-09-08v2026.7.0
digestabot-demodocs or examplesDemonstration repo for https://github.com/chainguard-dev/digestabot/pull/7402026-09-08
homebrew-tapinfrastructureHomebrew Tap for Wistia Desktop02026-09-04
json-mask-rubySDKGoogle partial-response / JSON Mask field selectors for Ruby: filter JSON-compatible Hashes and Arrays without changing...02026-09-04
elixir_nsqotherAn NSQ client for Elixir and Erlang, written in Elixir.922026-09-041.2.0

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

Jobs it can do

No job tag on this entry.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

Sources

5 source URLs. Raw sources field, verbatim:

https://docs.wistia.com/docs/mcp-server-guide, https://wistia.com/pricing, https://docs.wistia.com/docs/making-api-requests, https://api.wistia.com/mcp/api, https://github.com/wistia/agent-plugins

Notes, verbatim from the file
Verified 2026-09-07: POST of an MCP initialize to https://api.wistia.com/mcp/api returned HTTP 401 with JSON reading "unauthorized"; the control POST to /zzz-not-a-route returned 403 with an empty body. The statuses differ, so the 401 is specific to the MCP route rather than a blanket wall, but the control did not return 404, so this is recorded as a live auth-gated server on the vendor's host with a weaker control than the standard 404. The plan names in the MCP guide (Free, Pro, Max, Team) do not match the plan names on the current pricing page (Free, Business, Business + Lead gen, Enterprise); the guide is older than the price list. Like Vidyard in this file, Wistia is a hosting platform with a sales use case, not a purpose-built prospecting-video tool, which keeps headline finding 6 in INDEX.md intact. 2026-09-07: https://api.wistia.com/mcp/api returned 401 to an MCP initialize POST (https://api.wistia.com/mcp/api). 2026-09-09 (P6-04 repo sweep): first-party repository recorded at https://github.com/wistia/agent-plugins, the org wistia (profile site wistia.com), last push 2026-09-02. Its README states the plugins connect an agent to Wistia through Wistia's hosted MCP server, so this is the vendor's own client-side wiring, not the server source. The official registry entry io.github.wistia/wistia-api-mcp lists the remote https://api.wistia.com/mcp/api and no repository. No public server source was found.
Provenance
Entry id
08-wistia
Source file
08-video-prospecting.md
Source line
281
Tier
RESEARCHED
last_checked
2026-09-07
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.