Brollvia MCP for Cline

The VS Code agent extension — MCP servers panel, remote HTTP with OAuth.

Standard MCP connection — this guide follows Cline's documented MCP setup. We have not live-verified this client yet, so it does not carry the verified badge.

Cline · Editors & IDEs · Server URL: https://brollvia.com/mcp

Start free Developers

Why connect Cline to Brollvia

Cline, the autonomous coding agent that lives in VS Code (and several other editors), has first-class MCP support with its own servers panel: add Brollvia as a remote server and Cline can search the licensed library, assemble shot-list collections and download footage while it works through a task list — handy when the "task" is a video pipeline, a course build or a content site that needs real, licensed media rather than placeholders.

Standard status applies: the steps follow Cline's documented MCP configuration (cline_mcp_settings.json), and our server implements the protocol — but the live verification run belongs to Claude for now. Cline's remote-server OAuth support is recent; if your build predates it, the API-key header variant in the notes is the documented alternative.

Connect Brollvia to Cline

  1. In VS Code with Cline installed, open the Cline panel and click the MCP Servers icon.
  2. Choose "Configure MCP Servers" to open cline_mcp_settings.json.
  3. Paste the configuration below and save.
  4. Back in the MCP Servers panel, brollvia appears — toggle it on if needed.
  5. When Cline first connects, complete the OAuth sign-in in your browser and approve the scopes (older builds: use the API-key header from the notes).
  6. Give Cline a task involving footage — it can now call Brollvia's tools.

Paste into cline_mcp_settings.json (via Cline's MCP Servers panel → Configure):

{
  "mcpServers": {
    "brollvia": {
      "url": "https://brollvia.com/mcp",
      "disabled": false
    }
  }
}

What to ask once you are connected

Real prompts, using the real tools — search, script-to-B-roll, collections and licence lookups:

Use Brollvia to find and download three licensed clips of a bakery at dawn for the landing page hero.
Make a shot list collection for episode 4 from this outline, then license the picks.
Check which of these downloaded files have licence records and list the verification links.

Good to know

  • Cline stores MCP settings in cline_mcp_settings.json, managed from its own panel — editing it through the panel avoids path mistakes.
  • Remote OAuth in Cline is a recent addition; on older builds use "headers": { "Authorization": "Bearer <redacted>" } in the entry instead.
  • "alwaysAllow" per-tool lists exist in Cline's schema; leaving downloads to prompt-for-approval is the safer default for a licensing tool.

Cline + Brollvia: questions

Where exactly is the config file?

Cline manages it: MCP Servers panel → "Configure MCP Servers" opens cline_mcp_settings.json in the right location for your install (it lives in the extension's global storage, not your project). Pasting the snippet there — rather than hand-hunting the path — is the reliable route.

Does Cline support OAuth, or do I need an API key?

Recent Cline builds support OAuth for remote servers and will open the browser flow on first connect. If yours does not prompt, it predates the feature: either update Cline, or add the Authorization header with a Brollvia API key (Settings → Developer on Brollvia) — same scopes, same quotas.

Is Cline verified with Brollvia?

Not live yet — standard status. The configuration is Cline's documented remote-server shape. Claude is currently the only client with a completed production verification; this page will say so plainly until that changes.

Other clients

Same server, same URL — every guide below is that client's real setup. The full grid lives on the MCP hub.

Brollvia MCP for Claude

Anthropic

Claude.ai connectors and Claude Desktop — the client we run against production ourselves.

One URL connects them all

Start free, upgrade when the work does. Every download writes a licence record you can verify in public.