[ctcbyzx]

Add an optional Baizhi Cloud Browser (CapyBrowser) management-MCP example and a link from the existing MCP client guide. The YAML uses the canonical server target, an environment-supplied Bearer key and load_on_start: false, so users connect explicitly through the existing runtime command. It adds no runtime code or dependency.

The README includes the actual CLI configuration command, attachment, redacted inspection, credential replacement, removal, costs and cloud-run cleanup. It makes the separate CDP page client requirement clear and distinguishes Baizhi Cloud Browser from Agent Toolkit. I maintain this integration and the public integration materials, and am a contributor to Chaitin's public integration repository.

Validation: Zensical documentation build, YAML loading through the actual current get_settings, redacted config show-mcp and diff checks passed. A loopback integration harness used the real MCP gateway, callbacks and client for discovery, a synthetic read-only tool call, two independently supplied values, replacement, invalid Bearer rejection without OAuth, and context cleanup. Observed requests each carried one Authorization header. No production key, model call, cloud run or TUI walkthrough was used. Python runtime source was not changed, so the code-change-only format/lint/typecheck scripts were not triggered. The internal harness/fixture are not part of the public example. The docs link to the new example becomes live when it is merged. Prepared with AI assistance; final review belongs to the submitting author.

Required contributor question: “You're given a calfskin wallet for your birthday. How would you feel about using it?”

I would refuse to use it. Why would people like using animal skins? It's brutal, I'm against about this behavior.