Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
The VS Code agent extension — MCP servers panel, remote HTTP with OAuth.
Standard MCP connection — this guide follows Cline's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
Cline · Editors & IDEs · Server URL: https://brollvia.com/mcp
Cline, the autonomous coding agent that lives in VS Code (and several other editors), has first-class MCP support with its own servers panel: add Brollvia as a remote server and Cline can search the licensed library, assemble shot-list collections and download footage while it works through a task list — handy when the "task" is a video pipeline, a course build or a content site that needs real, licensed media rather than placeholders.
Standard status applies: the steps follow Cline's documented MCP configuration (cline_mcp_settings.json), and our server implements the protocol — but the live verification run belongs to Claude for now. Cline's remote-server OAuth support is recent; if your build predates it, the API-key header variant in the notes is the documented alternative.
Paste into cline_mcp_settings.json (via Cline's MCP Servers panel → Configure):
{
"mcpServers": {
"brollvia": {
"url": "https://brollvia.com/mcp",
"disabled": false
}
}
}Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Use Brollvia to find and download three licensed clips of a bakery at dawn for the landing page hero.
Make a shot list collection for episode 4 from this outline, then license the picks.
Check which of these downloaded files have licence records and list the verification links.
Cline manages it: MCP Servers panel → "Configure MCP Servers" opens cline_mcp_settings.json in the right location for your install (it lives in the extension's global storage, not your project). Pasting the snippet there — rather than hand-hunting the path — is the reliable route.
Recent Cline builds support OAuth for remote servers and will open the browser flow on first connect. If yours does not prompt, it predates the feature: either update Cline, or add the Authorization header with a Brollvia API key (Settings → Developer on Brollvia) — same scopes, same quotas.
Not live yet — standard status. The configuration is Cline's documented remote-server shape. Claude is currently the only client with a completed production verification; this page will say so plainly until that changes.
Same server, same URL — every guide below is that client's real setup. The full grid lives on the MCP hub.
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
OpenAI
Custom MCP connector via Developer mode, signed in with OAuth.
Microsoft
Copilot agent mode with the library one prompt away, via .vscode/mcp.json.
Anysphere
Remote MCP in mcp.json — OAuth connect, then footage inside the agent chat.
Gemini CLI — Google's terminal agent, connected via settings.json.
Google's agent-first editor — add Brollvia as a custom MCP server.
Anthropic
One `claude mcp add` command, OAuth in the terminal flow.
Windsurf (Codeium)
Cascade gains a licensed library via mcp_config.json.
Zed
MCP "context servers" in settings.json — remote URL, OAuth sign-in.
JetBrains
IntelliJ, WebStorm, PyCharm & co. — MCP in AI Assistant settings, no config file.
OpenAI
Muse — TOML config or one command, OAuth for remote servers.
Start free, upgrade when the work does. Every download writes a licence record you can verify in public.