Wistia for AI agents
Wistia hosts and manages marketing video content, used by marketing teams running video, webinars, and audience analytics on their own branded player. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Wistia.
Get analytics for a video
Pull play and engagement stats for a video, a read-only report.
Search video content
Find videos matching a keyword or tag across the account.
Confirm before deleting media
Check with the user before deleting a video, since it also removes its embedded links and stats.
10 Wistia actions, graded by risk.
Every Wistia action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- wistia.get_mediaGet Media
- wistia.search_contentSearch Content
- wistia.get_analytics_summaryGet Analytics Summary
write
5Create and change things. Allow, or ask the user first.
- wistia.update_mediaUpdate Media
- wistia.create_folderCreate Folder
- wistia.update_folderUpdate Folder
- wistia.import_media_from_urlImport Media from URL
- wistia.set_media_archived_stateSet Media Archived State
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- wistia.delete_mediaDelete Media
- wistia.delete_folderDelete Folder
Wistia in three steps.
- 01Your users connect WistiaThey add their Wistia api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Folder” can wait for the user, and “delete Media” can be denied outright.
- 03Any agent can actYour agent calls Wistia through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('wistia', { read: 'allow', write: 'ask', // create_folder destructive: 'deny', // delete_media }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Wistia connects.
Users add their Wistia api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Wistia connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Wistia from any agent.
Wistia and Arc0, answered.
Can I use Wistia with Claude, ChatGPT or Cursor?
Yes. Connect Wistia to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Wistia actions you allow.
How do users connect Wistia?
Users add their Wistia api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Wistia actions can my agent take?
10 in total: 3 read, 5 write and 2 destructive, such as “create Folder”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Wistia?
Yes. Actions like “delete Media” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Wistia too?
Yes. The same Wistia connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Wistia into your agent.
Your users connect Wistia once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan