← ClaudeAtlas

connect-toollisted

Set up and PROVE authentication for any CLI, MCP server, or Skill by driving your ALREADY-OPEN, logged-in Chrome via the OpenCLI browser bridge (opencli browser bind): your real session, supervised live, never a fresh or headless Chromium. Reconciles to a desired auth state, so it works even when a tool is already connected: first-time setup, token refresh, broadening scopes, key rotation, and repair. Runs on macOS and Windows, storing every secret in the macOS Keychain or Windows Credential Manager without the complete value entering the model context, wires the consumer, and does not stop until a real authenticated call returns live data. Idempotent and self-learning. Use when the user says connect a vendor, set up auth, get me an API key or token, add or broaden a scope, refresh a token, log me into a CLI, wire up credentials, or do the auth setup. Drives your real Chrome through OpenCLI bind only. It does NOT and MUST NOT use any other browser-driving tool or skill, because a spawned browser does not carr
Servosity/msp-skills · ★ 14 · AI & Automation · score 73
Install: claude install-skill Servosity/msp-skills
# connect-tool - browser-driven auth lifecycle manager Drives your real, logged-in Chrome (via OpenCLI) to set up / refresh / broaden / repair auth for any CLI, MCP server, or Skill; stores secrets in the OS credential store **without the complete value ever entering this context**; and does not stop until a real authenticated call returns live data. **Runs on macOS and Windows.** ## 0. Running the helpers (read before your first command) Every helper is a Python script next to this file, run the same way on both platforms: ``` uv run <this-skill-dir>/scripts/<helper>.py [args] ``` `<this-skill-dir>` is the directory containing this SKILL.md, which you already know because you just read it. Use that path directly. Do NOT search the filesystem for it and do NOT hardcode `~/.claude/skills/connect-tool`: a plugin install lands somewhere else, and any shell-search snippet breaks under the PowerShell tool on Windows. `uv` supplies its own Python, so nothing else needs installing to run these. If `uv` is absent but Python 3.12+ is present, `python3 <script>` (`python` on Windows) also works. There is no bash in these instructions on purpose. On native Windows without Git for Windows, Claude Code has no Bash tool at all and uses PowerShell; a `uv run` line is identical in both shells. **Requirements: macOS or Windows, Google Chrome, Node.js 20+ and npm, OpenCLI plus its Chrome extension, and `uv` (or Python 3.12+).** Check every one in a single command: `uv run <this-skill-d