Blog · AI & Agents
Letting an AI Agent Find Your Footage: A Guide to MCP for Creators
By George · October 22, 2026 · 2 min read
Somewhere between “AI will replace editors” and “AI is a toy” sits the actually useful thing: an assistant that does the legwork. Finding B-roll is legwork — searching, filtering, shortlisting, downloading, logging licences. MCP (Model Context Protocol) is the standard that lets assistants like ChatGPT and Claude do that legwork inside tools you control.
What MCP is, in one paragraph
MCP is an open protocol that exposes an application's capabilities as tools an AI assistant can call. Brollvia's MCP server offers twelve: search, metadata, similarity, collections and shot lists, licence-checked downloads, trending, topics and more — the full list is in the MCP tools reference.
Why it is safe to let an agent download for you
The agent acts as your account. Downloads check your plan (Free caps, HD vs originals, Pro library), write a normal licence record with a certificate, and every call is audit-logged. An agent cannot exceed your plan, because the server enforces the same rules as the website. The Developers page documents the identical REST API.
Connecting takes a minute
- ChatGPT — add a connector, choose OAuth, sign in, approve. Step-by-step.
- Claude — add a custom connector, choose OAuth, sign in, approve. Step-by-step.
- Cursor / Claude Code — file-based clients use an API key config instead. Step-by-step.
The killer workflow: script in, shot list out
With Pro, paste a script and the agent matches a clip to every beat, saving a shot list you can export to your NLE. It is the fastest first assembly most editors have ever had — and it starts from footage that is already licensed. See Script-to-B-roll.
ai agents api mcp