agent-login-broker (qulup-app) + Bitwarden Agent AccessPartly tested🌏 World

@kevin327g's open-source Bitwarden MCP login broker lets an agent log in without seeing the password; tested with Claude Code / Codex through GitHub 2FA

kevin mitsunaga of the Japanese band fhána (@kevin327g, building as qulup) uses Bitwarden, envied 1Password for Agents, and noticed Claude Code and Codex couldn't use it yet—so he built agent-login-broker (MIT, 0.1.2), an MCP server that does exactly one job: logging in. The agent just says "log in to app.example.com"; the server fetches one credential through Bitwarden Agent Access (aac) only after you approve, types it into its own headless Chromium (computing a TOTP code if the item has an authenticator key), drops it, and returns only "logged in to …" to the agent. The author says he tested it with Claude Code, Codex and omp, including GitHub switching from the passkey prompt to an authenticator code. We cloned commit e631a7f, installed deps plus Playwright's pinned Chromium, and ran the author's test suite: all 56 tests passed. We did not connect a real Bitwarden vault or log in to any real site.

Visit site agent-login-broker (qulup-app) + Bitwarden Agent Access ↗
Pricing
Free
Region
Global
Where it's from
Overseas
Added
Nov 1, 2026
Tested on
Nov 1, 2026
Version we used
qulup-app/agent-login-broker commit e631a7f (npm 0.1.2); Playwright 1.64.1; aac not installed
Categories
Automation & AgentsCodingProductivity
Original author
kevin mitsunaga (qulup) @kevin327g ↗
Our test
Partly tested
Cost / time
Plugin is MIT and free; Bitwarden free can store authenticator keys, but the author hasn't verified whether aac hands TOTP over on a free account (may need a paid plan); your agent subscription is separate.
Source
X @kevin327g ↗GitHub qulup-app/agent-login-broker ↗

The task

Let a coding agent log in to sites that need an account (admin panels, dashboards, your own SaaS) without the password or 2FA code ever entering the agent's conversation, tool output or logs.

Steps

  1. Prereqs: Node 20+; Bitwarden CLI (`bw login`); download `aac` from bitwarden/agent-access Releases onto PATH or `~/.local/bin` (author tested 0.11.0; still pre-1.0).
  2. Install the plugin—Claude Code: `claude plugin marketplace add qulup-app/agent-login-broker`, then `claude plugin install agent-login-broker@agent-login-broker`; Codex / omp / pi commands are in the README. Restart; `/mcp` should list agent-login-broker.
  3. Install the matching browser: `npx -y -p [email protected] playwright install chromium` (a bare `npx playwright install` may fetch a mismatched version).
  4. Pair aac: in one terminal run `aac listen`, `/unlock`, then `/pair agent-login-broker` for a code; in another run the README line `read -rs AAC_TOKEN && export AAC_TOKEN && aac connect; unset AAC_TOKEN` and enter it. Keep a single pairing on the machine.
  5. In Bitwarden set the item's URI to the site host and `bw sync`; for TOTP sites, save the authenticator key in the item.
  6. Each login: keep `aac listen` unlocked and tell the agent "log in to app.example.com". For a new site it drafts a recipe with `propose_recipe` (login path, username/password selectors, success path)—review it before saving.
  7. Approve the credential fetch in `aac listen` (times out after 3 minutes); the agent gets "logged in to …"; ask for `open_page` if you want to see it.
  8. To pin the agent to a fixed site list, set `AGENT_LOGIN_BROKER_SITES=app.example.com,...`.

Prompt

Use agent-login-broker to log in to app.example.com. If there's no recipe for this site yet, draft one with propose_recipe and show it to me; save it and log in only after I approve. Don't ask me for the password and never type a password into a browser yourself.

What the author says

@kevin327g: an MCP server that only does logins—it fetches one Bitwarden password per approval, uses it, discards it, and tells the AI only "logged in"; the AI never reads the password. If the item has TOTP it fills 2FA too; on GitHub it switched from the passkey prompt to the authenticator code and logged in. Tested with Claude Code, Codex and omp, MIT-licensed; early release, macOS only, use at your own risk. In replies: approvals appear in the terminal's aac listen, and he approves from his phone over SSH (Moshi) when away; it covers site logins only, not API keys sitting in .env.

Our test

On a Linux box we cloned qulup-app/agent-login-broker commit e631a7f (package 0.1.2), ran `npm ci --ignore-scripts` (Playwright 1.64.1, MCP SDK 1.32.2), `node --check server.mjs` passed; after installing Playwright's matching chromium-headless-shell we ran `npm test`. We did not install aac or the Bitwarden CLI, connected no real account, and did not have Claude Code / Codex perform a real login.

What we found when we tried it:Without the browser, 24 of 56 tests passed and 32 failed, all with "Executable doesn't exist … chrome-headless-shell"; with it installed, 56/56 passed (~1–2 s). Covered behaviours include: an error that would echo the password is replaced by a generic one, otpSwitch never follows a link off-site, an ordinary field with "code" in its name never gets the OTP, a bot check on the login form stops it before any credential is requested, and landing anywhere but the recipe's successPath fails closed. So the claimed safeguards have matching automated tests—but we did not verify an end-to-end login on a real site.

How to get in

Post is in English with Japanese replies; GitHub and README (EN/JA) are public. aac fetches credentials via Bitwarden's relay (wss://ap.lesspassword.dev by default).

Who it suits

Bitwarden users who want Claude Code / Codex to self-test or pull data from admin panels and dashboards without pasting passwords into chat.

Pitfalls

  • In our run, 32 tests first failed purely because Playwright's Chromium was missing; with the pinned browser installed, 56/56 passed. Use the versioned install command from the README.
  • The author says this is not covered: the agent runs as your user and can call `aac connect` itself, producing an identical approval prompt—deny any request you didn't just make, and keep auto-approve windows short.
  • The agent can write the recipes file; a malicious page could steer it to change which field gets the password. Review recipe changes before approving, or lock sites with `AGENT_LOGIN_BROKER_SITES`.
  • The password is still typed into the site's page, so its own and third-party scripts can read it—same as logging in by hand.
  • Only 6-digit authenticator TOTP; SMS/email codes, push approvals and passkey-only flows don't work; Google sites are refused outright; reCAPTCHA / hCaptcha / Turnstile make it stop and hand you the login page.
  • Early 0.1.2, macOS-only testing; Linux/Windows untested. Automated logins may break some sites' terms—use only on accounts you're authorized to use.

More in this category