Connect a Client
The BCTRL MCP server is a hosted endpoint. Point any MCP client at it and approve access in the browser.
Clients with native remote (Streamable HTTP) MCP support connect with the URL directly. Clients that only speak stdio — or that do not yet handle remote OAuth — bridge through mcp-remote, which runs the browser approval locally and forwards to the endpoint. Add it as a command (npx) with args (-y mcp-remote <url>):
Place that entry under your tool’s MCP servers key — mcpServers, servers, or context_servers, depending on the client.
For step-by-step setup for a specific client — Claude, Codex, Cursor, VS Code, Windsurf, Zed, Goose, or OpenCode — choose it from the sidebar. See also Transports and Authentication.

