Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
Google's agent-first editor — add Brollvia as a custom MCP server.
Standard MCP connection — this guide follows Google's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
Google · Editors & IDEs · Server URL: https://brollvia.com/mcp
Google Antigravity is an agent-first development environment built around delegating work to autonomous agents — and its agents can use MCP servers. Adding Brollvia gives those agents a licensed stock library: they can search footage, photos, music and SFX, build shot-list collections and download licensed originals as steps inside a larger mission, instead of sending you off to a browser tab.
Antigravity is the newest client on this page and the one we have had the least time with: this is a standard listing, not a verified one. The setup follows Antigravity's documented custom-MCP configuration (an mcp_config.json with a "serverUrl" entry); the only badge we award before running a client against production ourselves is none — Claude earned the verified one.
Add to ~/.gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"brollvia": {
"serverUrl": "https://brollvia.com/mcp"
}
}
}Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Build the launch video: use Brollvia to source five licensed clips of solar farms at golden hour and assemble them into a collection.
Find a licensed ambient track for the waiting screen and download it.
Match this script to B-roll, beat by beat, and license the picks.
Same vendor, different shape: the CLI is a terminal agent you drive command by command; Antigravity is an editor built around missions and multiple agents working in parallel. Both speak MCP — Antigravity through its mcp_config.json with "serverUrl", the CLI through settings.json with "httpUrl".
Not yet — standard status. Antigravity launched recently and our verification run has not happened; the configuration follows Google's documented format for custom MCP servers. Claude remains the only client we badge as verified live.
Everything the MCP tools expose: search and similar-search, script-to-B-roll matching, collections as shot lists, licensed downloads under your plan, and licence lookups. The agent works with your sign-in and your plan — it cannot exceed either.
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.
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.