Brollvia MCP for Claude
Anthropic
Claude.ai connectors and Claude Desktop — the client we run against production ourselves.
MCP client guide · October 2026
IntelliJ, WebStorm, PyCharm & co. — MCP in AI Assistant settings, no config file.
Standard MCP connection — this guide follows JetBrains's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.
JetBrains · Editors & IDEs · Server URL: https://brollvia.com/mcp
JetBrains IDEs — IntelliJ IDEA, WebStorm, PyCharm, PhpStorm, Rider and the rest — gained an MCP client in the AI Assistant during the 2025.2 release line: you register a remote server in Settings with a name and URL, and the AI chat's agent mode can then use its tools. Adding Brollvia gives that agent a licensed media library for the projects where code meets content — players, pipelines, media tooling, documentation with real footage.
There is no config file to paste here (JetBrains uses a settings form), which is why this page's guide is a click path. Status is standard: the flow is JetBrains' documented one and our server implements the protocol, but a live production verification in a JetBrains IDE has not been run yet — Claude remains the verified client.
Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:
Search Brollvia for licensed footage of an orchestra tuning up and download the best clip for the demo.
Turn this README's feature list into a Brollvia shot list collection.
Find a licensed ambient music loop for the loading screen and show me its licence terms.
The platform-wide AI Assistant MCP client applies across the IntelliJ-platform IDEs (IDEA, WebStorm, PyCharm, PhpStorm, Rider, GoLand and siblings) on the 2025.2+ line. The settings path in the steps is the shared one; minor label differences between builds are normal.
Because JetBrains' MCP client is configured through its Settings UI, not a file — inventing a JSON block would send you hunting for a file that does not exist. Where a client genuinely uses a file, its page shows the real file and the real key names; where it uses a form, the page shows the form path.
The settings form registers the server by URL and JetBrains runs OAuth against servers that advertise it — Brollvia does. You sign in on Brollvia and approve scopes; revocation lives in Brollvia's Connected apps as with every OAuth client here.
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.
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.
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.