Brollvia
Sign inJoin free

MCP client guide · October 2026

Brollvia MCP for Claude Code

One `claude mcp add` command, OAuth in the terminal flow.

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

Anthropic · CLI & terminal agents · Server URL: https://brollvia.com/mcp

Start free Developers

Why connect Claude Code to Brollvia

Claude Code, Anthropic's terminal agent, takes remote MCP servers with a single command and handles OAuth itself: add Brollvia over HTTP transport, authenticate from the /mcp menu, and Claude Code can search a licensed library, build shot lists and download footage as part of the same session where it is writing your pipeline, your templates or your edit tooling.

Same vendor as the verified client, different surface: our live verification was done in Claude's connector UI, not in Claude Code, so this page is listed as standard. The transport and OAuth flow are the same standards-based machinery — and if you connect it and something disagrees with these steps, we want the report.

Connect Brollvia to Claude Code

  1. Run the add command below in your terminal.
  2. Start Claude Code (claude) in your project.
  3. Open /mcp, select brollvia, and choose Authenticate.
  4. Complete the OAuth sign-in in your browser and approve the scopes.
  5. Ask Claude Code for footage — Brollvia appears in its available tools.

One command (add --scope user to make it available in every project):

claude mcp add --transport http brollvia 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 licensed drone footage of a lighthouse in a storm, download the best one to ./media.
Read script.txt, turn it into a Brollvia shot list, and license the picks under my Pro plan.
Check the licence on the last clip you downloaded and print its verification URL.

Good to know

  • Default scope is the current project; --scope user makes the server available everywhere, --scope project writes a shareable .mcp.json.
  • Authentication state is managed by Claude Code; /mcp shows connection health and lets you re-authenticate or clear it.
  • Everything runs under your Brollvia account and plan — the terminal is just another window onto the same library and licence records.

Claude Code + Brollvia: questions

Why is this page "standard" if Claude is verified?

Because the badge describes the exact surface we tested: Claude's connector UI against the production server, end to end. Claude Code shares the protocol and the vendor but is a different client build with its own auth plumbing; until we run it live, it stays standard — the badge has to mean something.

Does Claude Code need an API key?

No. The HTTP transport triggers Claude Code's built-in OAuth support against Brollvia's discovery endpoints — you sign in in a browser and approve scopes. (Config-file clients without OAuth can use API keys; Claude Code does not need that path.)

Where is the config stored?

Claude Code manages it (~/.claude.json and project .mcp.json for project scope). `claude mcp list` shows configured servers; `claude mcp remove brollvia` removes this one. Your Brollvia tokens can also be revoked server-side in Connected apps at any time.

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.

Start freeSee pricingTry packsDevelopers & MCP