Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
Copilot agent mode with the library one prompt away, via .vscode/mcp.json.
Standard MCP connection — this guide follows Microsoft's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
Microsoft · Editors & IDEs · Server URL: https://brollvia.com/mcp
VS Code's Copilot agent mode speaks MCP natively: add Brollvia as an HTTP server in an mcp.json file and the agent in your editor can search a licensed stock library, build shot lists as collections and download footage while you work — useful if your "editing" is really pipelines, templates, web players or batch tooling built in the IDE.
This client follows the standard path: Microsoft documents the flow, our server implements the protocol and OAuth discovery it expects, but we have not run a live verification inside VS Code yet (Claude is the verified client). If the Start button's OAuth prompt gives you any trouble, the API-key header variant in the notes is the documented fallback for config-file clients.
Save as .vscode/mcp.json (workspace) or in your user profile via the Command Palette:
{
"servers": {
"brollvia": {
"type": "http",
"url": "https://brollvia.com/mcp"
}
}
}Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Use Brollvia to find three licensed clips of a workshop build for the hero section, and download the best one into ./assets.
Build a shot list collection for this launch video from the script in ./script.md.
Find a licensed music track, 90 seconds, upbeat corporate — and show me the licence terms.
VS Code's MCP configuration schema uses its own top-level "servers" object with a "type": "http" entry — most other clients copied the "mcpServers" shape instead. Paste the snippet exactly as shown; renaming the key is the most common reason a VS Code setup silently does nothing.
MCP support in VS Code reached general availability in the 1.102 release line (mid-2025). Older builds may hide the Start action or the agent-mode tools picker entirely — update first if the steps above do not match your UI.
Yes. Config-file clients may send a static Authorization header with a Brollvia API key (created under Settings → Developer). OAuth is preferred — scoped, revocable per app, no secret sitting in a JSON file — but the key path is fully supported and shares the same scopes and quotas.
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.
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.
Cline
The VS Code agent extension — MCP servers panel, remote HTTP with OAuth.
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.