Brollvia MCP for VS Code

Copilot agent mode with the library one prompt away, via .vscode/mcp.json.

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

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

Start free Developers

Why connect VS Code to Brollvia

VS Code's Copilot agent mode speaks MCP natively: add Brollvia as an HTTP server in an mcp.json file and the agent in your editor can search a licensed stock library, build shot lists as collections and download footage while you work — useful if your "editing" is really pipelines, templates, web players or batch tooling built in the IDE.

This client follows the standard path: Microsoft documents the flow, our server implements the protocol and OAuth discovery it expects, but we have not run a live verification inside VS Code yet (Claude is the verified client). If the Start button's OAuth prompt gives you any trouble, the API-key header variant in the notes is the documented fallback for config-file clients.

Connect Brollvia to VS Code

  1. Use VS Code 1.102 or newer, with Copilot agent mode available.
  2. Create .vscode/mcp.json in your workspace (or run "MCP: Open User Configuration" from the Command Palette for a global setup).
  3. Paste the configuration below — note VS Code's top-level key is "servers", not "mcpServers".
  4. Click the Start action that appears above the brollvia server in the file.
  5. Complete the OAuth sign-in in your browser and approve the scopes.
  6. Open Copilot Chat in Agent mode and ask for footage — Brollvia's tools appear in the tools picker.

Save as .vscode/mcp.json (workspace) or in your user profile via the Command Palette:

{
  "servers": {
    "brollvia": {
      "type": "http",
      "url": "https://brollvia.com/mcp"
    }
  }
}

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 three licensed clips of a workshop build for the hero section, and download the best one into ./assets.
Build a shot list collection for this launch video from the script in ./script.md.
Find a licensed music track, 90 seconds, upbeat corporate — and show me the licence terms.

Good to know

  • Tool use requires Copilot Chat's Agent mode; Ask and Edit modes do not call MCP tools.
  • If OAuth is blocked in your environment, config-file clients can send an API key instead: add "headers": { "Authorization": "Bearer <redacted>" } to the server entry — create the key under Settings → Developer on Brollvia.
  • Workspace config is per-project; user config makes Brollvia available in every window.

VS Code + Brollvia: questions

Why "servers" and not "mcpServers"?

VS Code's MCP configuration schema uses its own top-level "servers" object with a "type": "http" entry — most other clients copied the "mcpServers" shape instead. Paste the snippet exactly as shown; renaming the key is the most common reason a VS Code setup silently does nothing.

Which VS Code versions support MCP?

MCP support in VS Code reached general availability in the 1.102 release line (mid-2025). Older builds may hide the Start action or the agent-mode tools picker entirely — update first if the steps above do not match your UI.

Can I use an API key instead of OAuth?

Yes. Config-file clients may send a static Authorization header with a Brollvia API key (created under Settings → Developer). OAuth is preferred — scoped, revocable per app, no secret sitting in a JSON file — but the key path is fully supported and shares the same scopes and quotas.

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.