Brollvia MCP for Cursor

Remote MCP in mcp.json — OAuth connect, then footage inside the agent chat.

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

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

Start free Developers

Why connect Cursor to Brollvia

Cursor supports remote MCP servers with OAuth: add Brollvia to mcp.json (globally in ~/.cursor/mcp.json or per-project in .cursor/mcp.json), and Cursor's agent can search the library, fill shot-list collections and license downloads without leaving the editor. For video-adjacent code — players, pipelines, templates, automation — that puts a licensed library inside the same agent loop as your build tools.

We have not live-verified Brollvia inside Cursor yet (Claude holds the verified badge). The flow below is Cursor's documented remote-server setup and our server implements the OAuth discovery it performs; should the one-click connect stall, the API-key header variant in the notes is the standard fallback.

Connect Brollvia to Cursor

  1. Open Cursor Settings → MCP (or edit ~/.cursor/mcp.json directly).
  2. Choose "Add new global MCP server" and paste the configuration below.
  3. Save — Cursor lists brollvia with a connect action.
  4. Click connect and complete the OAuth sign-in in your browser, approving the scopes.
  5. Open the agent chat and ask for footage; Brollvia tools appear alongside your other MCP tools.

Global: ~/.cursor/mcp.json — or per-project: .cursor/mcp.json in your repo:

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

Find licensed B-roll of a barista pouring latte art and download the best match into this project's media folder.
Make a Brollvia collection called "Onboarding v2" with five upbeat office clips.
What licence covers that clip? Show me the verification link.

Good to know

  • Cursor supports one-click MCP installs from links; the manual JSON above is the same result, typed.
  • API-key fallback: add "headers": { "Authorization": "Bearer <redacted>" } to the server entry if OAuth is unavailable in your setup.
  • Per-project config travels with the repo — teammates get the server entry (not your sign-in; each person OAuths as themselves).

Cursor + Brollvia: questions

Global or project config — which should I use?

Global (~/.cursor/mcp.json) if Brollvia is part of your personal toolkit everywhere; project (.cursor/mcp.json) if the repo's workflow assumes a stock library and the whole team should see the entry. Either way the OAuth sign-in is per-person — committing the file never shares your account.

Does Cursor support OAuth for remote MCP servers?

Yes — remote servers that advertise OAuth discovery get a connect flow in Cursor's MCP settings, which is why the snippet needs no headers. Brollvia's server publishes standard OAuth metadata and uses PKCE, the same flow verified with Claude's connectors.

The tools are not showing up in chat. What gives?

Three usual causes: the server shows an error state in Settings → MCP (re-connect to redo OAuth), the chat is not in agent mode, or the mcp.json file has a syntax slip — Cursor is quiet about parse failures, so validate the JSON. The configuration above is known-good shape for Cursor.

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.