Brollvia
Sign inJoin free

MCP client guide · October 2026

Brollvia MCP for Claude

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

Verified liveLive-verified by the Brollvia team: connected to the production Brollvia server over OAuth and used to search and license real footage, end to end.

Anthropic · AI assistants · Server URL: https://brollvia.com/mcp

Start free Developers

Why connect Claude to Brollvia

Claude connects to remote MCP servers as "connectors": in Claude.ai and Claude Desktop you add a custom connector by URL, sign in with OAuth, and Claude can then call Brollvia's tools mid-conversation — search the library, build shot lists, license and download footage, and pull the licence record for anything it fetches. No config files, no API keys to paste, nothing running locally.

Claude is the one client on this page we can vouch for personally: the Brollvia team connected the production server to Claude over the full OAuth flow — discovery, dynamic registration, consent, token exchange — and licensed real footage through it. That is what the "Verified live" badge means everywhere it appears on this site, and why it appears only here.

Connect Brollvia to Claude

  1. Open Claude.ai (or Claude Desktop) and go to Settings → Connectors.
  2. Choose "Add custom connector", name it Brollvia.
  3. Paste the MCP server URL: https://brollvia.com/mcp
  4. Click Add, then Connect — Claude opens Brollvia's sign-in.
  5. Sign in to Brollvia and approve the requested scopes (read, download, collections:write) on the consent screen.
  6. Back in Claude, start a chat and ask for footage — Claude calls Brollvia's tools directly.

Older Claude Desktop builds without the Connectors UI can use the mcp-remote bridge in claude_desktop_config.json instead:

{
  "mcpServers": {
    "brollvia": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "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:

Find me three licensed clips of a rainy Tokyo alley at night and add them to a collection called "Neo Noir".
Here is my script — break it into shots and match each beat to B-roll from the library.
License that drone shot of the coastline for my project and show me the licence record.
Find B-roll that looks like this frame — same palette, golden hour, wide shot.

Good to know

  • Custom connectors are a paid-plan feature in Claude (Pro, Max, Team, Enterprise) as of October 2026.
  • You approve scopes once; revoke any time in Brollvia under Settings → Developer → Connected apps, or in Claude's connector settings.
  • Downloads follow your Brollvia plan exactly as on the web — Claude cannot spend past your plan, and every download writes the same licence record.

Claude + Brollvia: questions

What does "Verified live" actually mean here?

That the Brollvia team ran this exact flow against the production server — OAuth sign-in, tool calls, a real licensed download — and it worked end to end. No other client on this site carries the badge, because we have not done that run for them yet; they speak standard MCP and their guides follow the vendor's own documentation.

Claude.ai or Claude Desktop — does it matter?

Both speak the same connector protocol and both work. Claude.ai is the fastest path (pure OAuth, nothing local). Claude Desktop adds the option of the mcp-remote bridge config shown above for older builds. Your Brollvia sign-in and scopes are shared either way.

What can Claude do once connected?

Search and preview the whole library, match a script to shots with suggest_broll_for_script, create and fill collections as shot lists, license and download originals under your plan, and fetch the licence record for any download. Generation credits and account settings stay on the website.

How do I disconnect Claude?

Either side works: remove the connector in Claude's Settings → Connectors, or revoke the app in Brollvia under Settings → Developer → Connected apps. Revoking on Brollvia kills the tokens immediately, even mid-conversation.

Other clients

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

One URL connects them all

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

Start freeSee pricingTry packsDevelopers & MCP