[ctcbyzx]

Add a Baizhi Cloud Browser (CapyBrowser) setup guide to the existing MCP Servers section so LibreChat users can configure the hosted management tools with their own credentials. The guide uses the existing sensitive customUserVars flow, a static Bearer header and on-demand connection. It covers discovery, key replacement, removal, costs and cloud-run cleanup, including the separate CDP client needed for webpage actions.

The change contains one English guide, the guide-index entry and synchronized sidebar metadata for all 14 languages. English is the only new prose; translated navigation titles are preserved. It adds no application code or dependency. I maintain this integration and the public integration materials, and am a contributor to Chaitin's public integration repository. Related PR #774 documents Baizhi Cloud Agent Toolkit, a separate service.

Validation at upstream 2426cdc72ecd4be92b2545ec56b03cef6d7dea36:

• Passed the README-required pnpm lint, pnpm typecheck and full pnpm build; the successful build used Node.js 24.22.1 with NODE_USE_ENV_PROXY=1.
• Passed config-version, locale-navigation synchronization, changed JSON formatting and diff checks. The production build was served locally; the guide and sidebar were visually inspected.
• An internal loopback harness loaded this guide's YAML into the current LibreChat application's actual schema, processMCPEnv and built MCPConnection. Discovery worked with two separately supplied user values and a replacement value; an invalid credential was rejected, observed requests carried exactly one Authorization header, and connections were disposed.

The connection-layer checks do not cover GUI credential persistence, an Agent tool call, production service acceptance or an independent reader walkthrough. No production key, model call or cloud run was used. The harness and fixture are internal validation artifacts, outside this documentation diff. Prepared with AI assistance.

[vercel]

@ctcbyzx is attempting to deploy a commit to the LibreChat's projects Team on Vercel.

A member of the Team first needs to authorize it.

[ctcbyzx]

Could a maintainer authorize a Vercel preview for the current commit, b3c7ca9, and confirm that content/docs/mcp_servers/baizhi_cloud_browser.mdx is appropriately placed? This is one English guide with its index and navigation entries; it does not change the app runtime.