Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
Custom MCP connector via Developer mode, signed in with OAuth.
Standard MCP connection — this guide follows OpenAI's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
OpenAI · AI assistants · Server URL: https://brollvia.com/mcp
ChatGPT reaches custom MCP servers through its Connectors system: with Developer mode enabled, you can add your own connector by URL — including Brollvia — and ChatGPT can then search the library, assemble shot lists and license footage inside the conversation, signing in through Brollvia's OAuth flow rather than a pasted key.
An honesty note we put on every client page except one: we have not yet completed a live verification run of the Brollvia server inside ChatGPT (Claude is the verified client today). The steps below are OpenAI's documented connector flow, which our OAuth server is built to — discovery, dynamic client registration, PKCE — and the connection should work exactly as described; if it does not, tell us and this page gets corrected or the badge question gets revisited.
Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Search Brollvia for licensed aerial shots of Icelandic waterfalls and shortlist the five strongest.
Turn this treatment into a shot list and fill it with licensed B-roll.
Download the ProRes-ready version of that clip and give me its licence verification link.
Find me SFX for a rain-and-thunder transition, licensed and ready to use.
OpenAI gates user-added MCP servers behind Developer mode in ChatGPT settings — it is their control for custom connectors, separate from the curated connector directory. Turning it on does not change your account otherwise; it simply unlocks the "create connector" form these steps use.
OAuth. ChatGPT discovers Brollvia's authorization server metadata, registers itself dynamically and runs an authorization-code + PKCE flow — you sign in on Brollvia and approve scopes. No key is pasted into ChatGPT, and you can revoke the connection from Brollvia's Connected apps page.
Not live yet — and this page says so rather than implying otherwise. Our OAuth implementation is the same one verified end-to-end with Claude's connector system, and ChatGPT's flow follows the same standards. When we complete a production run in ChatGPT, this page gains the verified badge.
The same tools every MCP client gets: search, similar-frame search, script-to-B-roll, collections as shot lists, licensed downloads under your plan, and licence-record lookups. Plan limits apply identically to the website.
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.
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.
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.