Brollvia
Sign inJoin free

MCP client guide · October 2026

Brollvia MCP for Zed

MCP "context servers" in settings.json — remote URL, OAuth sign-in.

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

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

Start free Developers

Why connect Zed to Brollvia

Zed calls MCP servers "context servers" and configures them in its JSON settings: add Brollvia with a remote URL and the Zed agent panel can search a licensed stock library, build shot-list collections and download footage mid-thread. For developers who live in Zed and produce video-adjacent work — docs, demos, product films — it removes the browser round-trip entirely.

This is a standard listing: Zed's remote context-server support and OAuth handling follow its documentation, our server implements the same protocol verified elsewhere, but we have not run Zed against production ourselves yet. The badge rule on this site is strict — verified means we did it, live — and for now that is Claude only.

Connect Brollvia to Zed

  1. Open Zed settings (Settings → Open Settings, or edit settings.json directly).
  2. Add the context_servers entry below.
  3. Save — Zed starts the context server and brollvia appears in the agent panel's server list.
  4. Authenticate when prompted and complete the OAuth sign-in in your browser, approving the scopes.
  5. Open the agent panel and ask for footage.

Add to your Zed settings.json:

{
  "context_servers": {
    "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 footage of a night train crossing a city and download the strongest clip.
Build a Brollvia collection for the onboarding video with six calm technology shots.
Show me the licence record for the clip you just fetched.

Good to know

  • Zed's schema key is "context_servers" — not "mcpServers"; each ecosystem renamed something, and this is Zed's.
  • Local stdio context servers take a "command" entry instead; Brollvia is remote-only, so the "url" form is the whole config.
  • If OAuth is unavailable in your build, Zed context servers accept a "headers" object — an API-key Authorization header works there.

Zed + Brollvia: questions

What is a "context server"?

Zed's name for an MCP server: a source of tools and context for its agent panel. The protocol underneath is the same MCP every client on this hub speaks — only the settings key ("context_servers") and the UI language differ.

Does Zed support remote servers with OAuth?

Zed supports remote (HTTP) context servers, and servers that advertise OAuth get an authenticate action in the agent panel. Brollvia publishes standard OAuth discovery with PKCE — the flow verified through Claude's connectors — so the sign-in happens in your browser, not via a pasted secret.

Verified?

Standard, not verified: we have not completed a live production run in Zed yet. The setup above is Zed's documented remote context-server configuration.

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