Claude Desktop

  1. Keep the app in its intended installed location and start its MCP server.
  2. Choose Copy Claude config in Agent connections.
  3. Merge the copied entry into ~/Library/Application Support/Claude/claude_desktop_config.json, preserving other entries under mcpServers.
  4. Restart Claude Desktop. Keep B-Roll Archives open with its server enabled.

The copied command points to the app’s bundled native stdio bridge. No Node.js or Python installation is needed. A typical installed location produces:

{
  "mcpServers": {
    "broll_archives": {
      "command": "/Applications/B-Roll Archives.app/Contents/Helpers/broll-mcp-bridge",
      "env": {
        "BROLL_ARCHIVES_MCP_URL": "http://127.0.0.1:8090/mcp"
      }
    }
  }
}

Copy the configuration again if you move or rename the app. The bridge is verified against the local server, but an actual Claude Desktop session remains to be checked. See the official local MCP connection guide.

Claude Code

Choose Copy Claude Code config and merge the HTTP server entry into the appropriate .mcp.json:

{
  "mcpServers": {
    "broll_archives": {
      "type": "http",
      "url": "http://127.0.0.1:8090/mcp"
    }
  }
}

Reload the connection and use /mcp to inspect status. Claude Code connection health has been checked with an isolated configuration. Consult Claude Code’s MCP documentation for configuration scopes.

Troubleshooting

Confirm the app is open, the endpoint matches, and existing JSON entries were preserved. A missing bridge command often means the installed app location differs from the example. See MCP overview.