Brollvia MCP for Gemini

Gemini CLI — Google's terminal agent, connected via settings.json.

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

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

Start free Developers

Why connect Gemini to Brollvia

This page is about the Gemini CLI, Google's open-source terminal agent — not the Gemini app. The CLI reads MCP servers from its settings file, supports remote HTTP servers with OAuth, and can then call Brollvia's tools from your shell session: search the library, assemble shot lists, license and download footage as part of a scripted workflow.

The caveat matters enough to repeat in the notes: the consumer Gemini app (gemini.google.com, Gemini Advanced) does not accept custom MCP servers — there is nowhere in it to paste this URL. Within the CLI, the flow below is Google's documented setup; we have not live-verified it ourselves yet, so this page carries the standard status, not the verified badge (that is Claude's, for now).

Connect Brollvia to Gemini

  1. Install the Gemini CLI and sign in to it as usual.
  2. Open ~/.gemini/settings.json (create it if it does not exist).
  3. Add the mcpServers entry below — Gemini CLI's remote key is "httpUrl".
  4. Start the CLI and run /mcp to confirm brollvia is listed.
  5. Run /mcp auth brollvia and complete the OAuth sign-in in your browser, approving the scopes.
  6. Ask Gemini for footage in plain language — it will call the Brollvia tools.

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "brollvia": {
      "httpUrl": "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:

Search Brollvia for licensed timelapse footage of clouds over mountains and save the best download link.
Create a shot list for a 30-second coffee ad from this script and fill it with licensed clips.
Download the WAV of a gentle rain loop from Brollvia and confirm its licence.

Good to know

  • Gemini CLI only: the Gemini app and Gemini Advanced do not take custom MCP servers — no URL field exists there.
  • Gemini CLI uses "httpUrl" for remote servers in settings.json ("url" is used by some other clients; the CLI also accepts "url" in recent versions, but httpUrl is the documented key).
  • API-key fallback: add "headers": { "Authorization": "Bearer <redacted>" } to the entry if OAuth is impractical in your environment.

Gemini + Brollvia: questions

Can I add Brollvia to the Gemini app?

No — and any guide implying otherwise is out of date. The consumer Gemini app has no custom-MCP or connector-by-URL feature. Google's MCP story for individuals is the Gemini CLI (this page) and Antigravity; in the app, your route to Brollvia is the ordinary website.

What does /mcp auth do?

It runs the OAuth flow for that server: the CLI opens Brollvia's authorize page, you sign in and approve scopes, and the CLI stores the resulting tokens (refresh tokens rotate; revoke any time from Brollvia's Connected apps). Until you auth, the server may list with limited or no tools.

Is the Gemini CLI connection verified by Brollvia?

Not live yet. The setup follows Google's own Gemini CLI documentation and our server implements the standard discovery the CLI performs. When we complete a production run, this page gets the verified badge — until then it stays honestly labelled standard.

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.