Can AI agents automate Bitwarden?

Bitwarden is automatable today through the official bw CLI. This record is Bitwarden Password Manager (cloud and self-hosted vaults, organization administration, CLI, Public API, and the first-party local MCP). It is not 1Password and not HashiCorp Vault. bw installs on Windows, macOS, and Linux, logs in with email, a personal API key (BW_CLIENTID and BW_CLIENTSECRET), or SSO, and unlocks with a master password to produce BW_SESSION. Item, folder, send, and organization-collection commands return JSON; --pretty formats that JSON. That is the broadest documented agent path for vault items. The Public API is a documented REST surface at https://api.bitwarden.com/public for members, collections, groups, event logs, and policies. It authenticates with OAuth2 client credentials (scope api.organization) against identity.bitwarden.com, then Authorization: Bearer. Bitwarden states the Public API does not manage individual vault items and is available to Teams and Enterprise organizations. A separate Vault Management API is a local Express server started with bw serve; it is not a hosted vault-item API. First-party MCP is npm package @bitwarden/mcp-server (bitwarden/mcp-server), stdio only. Vault tools wrap the CLI (lock, unlock, sync, item CRUD, folders, attachments, Send, device approval). Organization-admin tools wrap the Public API and need Teams or Enterprise plus owner or admin API credentials. The README says the server must never be hosted publicly and that vault contents can appear in AI responses. That is the opposite of 1Password Environments MCP, which the opened 1Password page says never returns stored secret values. iPaaS connectors were not opened. Computer-use viability is unassessed. CLI scores 8 and is the best path. API scores 6 because the hosted Public API is org-admin only and edition-gated. MCP scores 6 because it is local-only, can leak vault secrets into model output, and org tools need Teams or Enterprise.

Best path today: cli · Overall automatability: 8/10