Brollvia
Sign inJoin free

MCP client guide · October 2026

Brollvia MCP for Codex

Muse — TOML config or one command, OAuth for remote servers.

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

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

Start free Developers

Why connect Codex to Brollvia

OpenAI's Muse reads MCP servers from its TOML configuration and supports remote HTTP servers with OAuth: register Brollvia once and Codex can search the licensed library, assemble shot-list collections and download footage while it works in your repo — the media side of a build handled by the same agent as the code side.

Standard status, stated plainly: the steps are OpenAI's documented Codex MCP flow, our server implements the protocol and OAuth discovery, but our live verification badge currently belongs to Claude's connector run. If you connect Codex first and hit a discrepancy, the notes' API-key variant is the fallback every config-based client shares.

Connect Brollvia to Codex

  1. Run: codex mcp add brollvia --url https://brollvia.com/mcp — or add the TOML block below to ~/.codex/config.toml yourself.
  2. Start codex in your project.
  3. Open /mcp and authenticate brollvia when prompted.
  4. Complete the OAuth sign-in in your browser and approve the scopes.
  5. Ask Codex for footage — Brollvia's tools are in its set.

Or add this block to ~/.codex/config.toml:

[mcp_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:

Download three licensed clips of a blacksmith working — Brollvia only — into ./public/media.
Create a Brollvia shot list from the scenes in trailer-script.md and license the selections.
Print the licence verification URL for every Brollvia file in ./public/media.

Good to know

  • Codex config is TOML, not JSON — the [mcp_servers.<name>] table is the whole entry for a remote server.
  • codex mcp list shows configured servers; authentication state is per-server and can be reset from /mcp.
  • API-key fallback: config-based clients can send an Authorization header via the server's http_headers table if OAuth is unavailable.

Codex + Brollvia: questions

Does the Muse support OAuth, or only API keys?

It supports OAuth for remote MCP servers: registering a URL-based server and authenticating via /mcp runs the browser flow against the server's discovery metadata. Brollvia's authorization server (PKCE, rotating refresh tokens) is built for exactly this pattern.

Where does Codex keep MCP config?

In ~/.codex/config.toml under [mcp_servers] tables — user-level, shared across your projects. The `codex mcp add` command writes the same block the snippet shows, so the two routes in the steps are equivalent.

Is Codex verified with Brollvia?

Not yet — standard status, following OpenAI's documented configuration. We verify clients against production one at a time and badge them only after a full run; today that is Claude.

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