Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
Remote MCP in mcp.json — OAuth connect, then footage inside the agent chat.
Standard MCP connection — this guide follows Anysphere's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
Anysphere · Editors & IDEs · Server URL: https://brollvia.com/mcp
Cursor supports remote MCP servers with OAuth: add Brollvia to mcp.json (globally in ~/.cursor/mcp.json or per-project in .cursor/mcp.json), and Cursor's agent can search the library, fill shot-list collections and license downloads without leaving the editor. For video-adjacent code — players, pipelines, templates, automation — that puts a licensed library inside the same agent loop as your build tools.
We have not live-verified Brollvia inside Cursor yet (Claude holds the verified badge). The flow below is Cursor's documented remote-server setup and our server implements the OAuth discovery it performs; should the one-click connect stall, the API-key header variant in the notes is the standard fallback.
Global: ~/.cursor/mcp.json — or per-project: .cursor/mcp.json in your repo:
{
"mcpServers": {
"brollvia": {
"url": "https://brollvia.com/mcp"
}
}
}Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Find licensed B-roll of a barista pouring latte art and download the best match into this project's media folder.
Make a Brollvia collection called "Onboarding v2" with five upbeat office clips.
What licence covers that clip? Show me the verification link.
Global (~/.cursor/mcp.json) if Brollvia is part of your personal toolkit everywhere; project (.cursor/mcp.json) if the repo's workflow assumes a stock library and the whole team should see the entry. Either way the OAuth sign-in is per-person — committing the file never shares your account.
Yes — remote servers that advertise OAuth discovery get a connect flow in Cursor's MCP settings, which is why the snippet needs no headers. Brollvia's server publishes standard OAuth metadata and uses PKCE, the same flow verified with Claude's connectors.
Three usual causes: the server shows an error state in Settings → MCP (re-connect to redo OAuth), the chat is not in agent mode, or the mcp.json file has a syntax slip — Cursor is quiet about parse failures, so validate the JSON. The configuration above is known-good shape for Cursor.
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.
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.