Head to head · Secrets storage · October 2026 research run
1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager
1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in every scored category. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
1Password service accounts, SDKs and Environments MCP BB
Best for Teams whose people already use 1Password and want agents reading from the same vaults with read-only, vault-scoped tokens, and for developers who want an MCP server that never leaks a value.
Ahead on
- Schema & documentation, 74 against 53
- Agent ergonomics, 69 against 52
- Security & auth, 94 against 76
- Payments & pricing, 45 against 38
- Maintenance & community, 82 against 36
- Transparency & trust, 87 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After
Best for Teams already on Bitwarden who want cheap, end-to-end encrypted, project-scoped machine identities for a few agents, injected with bws run.
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community 1Password service accounts, SDKs and Environments MCP +46
1Password service accounts, SDKs and Environments MCP 82
Python SDK 0.4.2 (PyPI on 22 October 2026, per the 23 October check; tag v0.4.2 in the repository on 1 November) and CLI 2.41.1 on 21 October 2026, so the newest release is 10 days old (30). CLI 2.38.1, 2.39.0, 2.40.0 (1 October), 2.41.0 (12 October) and 2.41.1, SDKs 0.4.1 and JavaScript 0.5.0 and Python 0.4.2 all fall in the last 90 days (20). Responsiveness per the 1 October check, not re-read on 1 November, since GitHub's pages answered 403. The JavaScript SDK had 30 open issues and 16 open pull requests, and in the Python SDK 5 of the 8 newest open issues had no reply, including a broken get_variables report from 3 June 2026 (10 of 25). Current official SDKs in three languages; the official MCP registry search for 1password on 1 November returns only a third-party entry (io.github.CakeRepository/1password), nothing under a 1Password namespace (15). The SDKs pin one current core package, CLI 2.40.0 and 2.41.1 updated Go for known vulnerabilities, and Python SDK 0.4.2 shipped no CPython 3.14 wheels (cp39 to cp313 only) per the 23 October check (7 of 10).
Bitwarden Secrets Manager 36
Newest releases are 2.1.0 for Rust, Python and bws, tagged 20 May 2026, and Go 2.1.0 on 22 May, 166 days before this check (10). No release in the 90 days from 6 August; commits since then are unreleased, among them a bws config fix on 1 September (#1569), CI permission hardening on 24 September and internal crates 4.0.0 on 30 September, with none after that by 4 November (0). 33 open issues, with bug reports from July 2025 still open and no fix released since May, per the 1 October check (10 of 25). Rust, Python and Go SDKs are current at 2.1.0, but the npm package is 1.0.0 from September 2024, and the official MCP server covers the password vault only (7 of 15). Renovate keeps dependencies current and CI covers each binding (9 of 10). 10+0+10+7+9 = 36.
Schema & documentation 1Password service accounts, SDKs and Environments MCP +21
1Password service accounts, SDKs and Environments MCP 74
No contract for the service account path itself, but the self-hosted Connect server has a public OpenAPI file (1.8.1), and the MCP tools are closed source so their schemas can't be read (15 of 25). llms.txt at www.1password.dev with Markdown links for service accounts, SDKs, Connect, the Events API, the CLI and the MCP server (10). The docs say what each piece is for and the AI agent tutorial says when not to use it (12 of 20). The SDKs are typed in TypeScript, Go and Python and the Connect spec types every field (12 of 15). Plenty of examples, a documented Connect error body and the 429 texts, but SDK errors are thin and two open issues ask for better exceptions (10 of 15). Dated release notes for the SDKs, CLI and Connect at releases.1password.com, though Python SDK 0.4.2 (PyPI, 22 October 2026) still had no release note on 1 November (15). The developer docs also have llms-full.txt and an MCP search server for the docs; the Agentic Autofill partner guide is on www.1password.dev but not in llms.txt, and isn't scored here since it's a partner preview.
Bitwarden Secrets Manager 53
No OpenAPI for the Secrets Manager API; the SDK generates JSON schemas for its own command interface, which the language bindings are built from (10 of 25). bitwarden.com/llms.txt answers with an index of about 60 links, none to the Secrets Manager CLI, SDK or machine account help pages (3 of 10). Help pages explain each concept and the CLI has --help for every command, but nothing says when to use the SDK rather than bws run (12 of 20). The SDKs are typed from those generated schemas (12 of 15). Examples on the help pages and READMEs, while open issues #1561, #1287 and #1331 report wrong or bare error messages (8 of 15). Semver tags and GitHub releases, but the crate changelogs stopped in September 2024 (8 of 15).
Security & auth 1Password service accounts, SDKs and Environments MCP +18
1Password service accounts, SDKs and Environments MCP 94
Service account tokens are scoped per vault to read_items, write_items or share_items, can expire with --expires-in, are revocable, and permissions can't be widened after creation. The JavaScript SDK 0.5.0 adds workload identity through the Credential Broker in public preview (30). Read-only service accounts, Personal, Private and Employee vaults excluded, and the MCP server asks for approval per Environment in the desktop app, though not per destructive call. Enterprise Password Manager admins can turn the local MCP server off under Policies, Agentic permissions (17 of 20). The MCP server won't return a secret value even when asked, and the SDK agent tutorial warns against putting raw credentials in front of a model (15). Service account usage reports show which items were read, and the audit log and Events API need Business (12 of 15). security.txt with a HackerOne programme, a public trust centre listing SOC 2 Type II and ISO 27001 (20).
Bitwarden Secrets Manager 76
Machine account access tokens are revocable, optionally expire (default never), are never stored by Bitwarden, and inherit the account's Can read or Can read, write grant per project, while secrets decrypt only on the client. A revoked token's live session can keep reading for up to an hour, and there's no workload identity login (23 of 30). Can read on one project gives a read-only agent, but there's no approval step for writes or deletes (14 of 20). Secrets aren't untrusted content, and bws run puts them in the environment rather than in a model's context (10). Each machine account has an event log of secret access, retained indefinitely and exportable, on Teams and Enterprise only (12 of 15). SOC 2 Type II, SOC 3, ISO 27001 and a HackerOne bounty, but bitwarden.com/.well-known/security.txt answered 404 on 4 November 2026; the SDK's SECURITY.md routes reports to HackerOne (17 of 20). OSV lists no advisory for bitwarden-sdk on PyPI, @bitwarden/sdk-napi on npm or the bws and bitwarden crates on 4 November.
Transparency & trust 1Password service accounts, SDKs and Environments MCP +18
1Password service accounts, SDKs and Environments MCP 87
SDK wrappers and the WebAssembly core package are MIT, the CLI, desktop app and service are closed under clear terms (18 of 30). Privacy notice effective 29 December 2025 (unchanged on 1 November), a DPA (v202504, per the 1 October check) and a subprocessor list effective 30 April 2025 (re-read on 1 November) agree, though retention is only as long as necessary (25 of 30). SDK support policy of three months of patches per version 0 release, with dated release notes (15 of 20). Subprocessors listed and data hosted in the US, Canada or EU at the customer's choice (20).
Bitwarden Secrets Manager 69
Source is on GitHub, but the SDK and bws ship under Bitwarden's own SDK licence, which limits use to applications that work with Bitwarden; it isn't an OSI licence (12 of 30). The privacy policy (revised April 2024, per the 30 September check) and the compliance page agree on US or EU hosting on Azure, with GDPR and DPF statements; we didn't read a DPA or subprocessor list (18 of 30). No SDK deprecation policy found; the only dated removal is the action type commands in bws 1.0.0 (6 of 20). No telemetry in the bws or SDK source, and hosting regions are disclosed (16 of 20).
Agent ergonomics 1Password service accounts, SDKs and Environments MCP +17
1Password service accounts, SDKs and Environments MCP 69
The MCP server has 8 tools and returns names only, but its definitions aren't published, so we can't size them (20 of 25). Connect filters items with SCIM-style title and tag filters and pages the activity log, while the SDK lists vaults and items by state without paging (12 of 20). Errors carry a status and message in Connect and fixed 429 texts for service accounts, and issues #243 and #218 in the Python SDK report vague or misleading exceptions (10 of 20). On 1 November the docs still mark 3 of the 8 MCP tools read-only and none destructive (on 1 October 4 were marked read-only and 4 destructive). All three list tools are marked, the other five create, rename, append or authenticate, and secret reads are safe to repeat, but there's no idempotency for writes, so 12 of 20 stays. Official Go, JavaScript and Python SDKs, op:// references as the only required input for a read (15).
Bitwarden Secrets Manager 52
No MCP server for Secrets Manager, so the cost is CLI output, which comes as json, yaml, env, tsv, table or none (15 of 25). Secrets list by project and are fetched one by one by UUID, with no name lookup, paging or filtering (8 of 20). Error messages are a known weak spot, with open issues for a wrong message on a bad token (#1561) and a bad message on a missing write permission (#1287) (8 of 20). No idempotency keys or retry guidance, and secret writes are addressed by ID (6 of 20). SDKs in eight languages plus bws run, and the access token is the only required input (15).
Payments & pricing 1Password service accounts, SDKs and Environments MCP +7
1Password service accounts, SDKs and Environments MCP 45
No x402, MPP or L402 (0). Plan prices are public, with no per-call pricing (10). A 14-day trial on every plan, and on 1 November both pricing pages still say "No credit card required" under each plan's trial button (20, was 10 when the pages didn't say). A person signs up in a browser and creates the service account, and there's no API to create one without a signed-in human (0). 1Password for Agents (22 October) is included at no additional cost on Individual and Families plans, but it is reached through partner agents, not bought or set up by an agent. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Bitwarden Secrets Manager 38
No x402, MPP or L402 (0). Teams $6 and Enterprise $12 per user a month with 20 or 50 machine accounts and $1 per extra machine account are public (10). A free plan with 2 users, 3 projects and 3 machine accounts, and a 14-day trial; the pages don't say whether a card is taken (15 of 20). A person signs up and creates the machine account and token in the web app (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Score by category
| Category | Weight | 1Password service accounts, SDKs and Environments MCP | Bitwarden Secrets Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 66 | 1Password service accounts, SDKs and Environments MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 53 | 1Password service accounts, SDKs and Environments MCP +21 |
| Agent ergonomics | 13% | 69 | 52 | 1Password service accounts, SDKs and Environments MCP +17 |
| Security & auth | 14% | 94 | 76 | 1Password service accounts, SDKs and Environments MCP +18 |
| Payments & pricing | 10% | 45 | 38 | 1Password service accounts, SDKs and Environments MCP +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 36 | 1Password service accounts, SDKs and Environments MCP +46 |
| Transparency & trust | 7% | 87 | 69 | 1Password service accounts, SDKs and Environments MCP +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 73.7/100 | C 57.5/100 |
Facts side by side
| Fact | 1Password service accounts, SDKs and Environments MCP | Bitwarden Secrets Manager |
|---|---|---|
| Kind | Platform | SDK + MCP |
| Vendor | 1Password | Bitwarden |
| Hosted endpoint | no (local only) | https://api.bitwarden.com |
| Transports | stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | MIT | Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-05-22 |
| Terms last updated | 2024-09-12 | no date given |
| Privacy policy last updated | 2025-12-29 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 110 stars, 1M npm/wk, 817k PyPI/wk | 480 stars, 24k npm/wk, 25k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate 1Password service accounts, SDKs and Environments MCP higher.
| Reviewer | 1Password service accounts, SDKs and Environments MCP | Bitwarden Secrets Manager |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 listAll became list in a version 0 minor | 2/5 Releases at 2.1.0, changelog stuck at 1.0.0 |
| WardenSecurity auditor | 4/5 Vault scopes that can't be widened later | 3/5 Decrypted on the client, readable for an hour after revoke |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
1Password service accounts, SDKs and Environments MCP
Service accounts scoped per vault to read, write or share, with an optional expiry and permissions that can't be changed after creation. Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After.
Bitwarden Secrets Manager
End-to-end encrypted, decrypted only on the client that holds the token. No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024.
Before you call either
1Password service accounts, SDKs and Environments MCP
- Read secrets by reference (op://vault/item/field) with client.secrets.resolve or resolveAll, and keep the reference, not the value, in config
- On Teams or personal plans budget for 1,000 reads an hour per token and cache resolved values for the run; a 429 means wait for the hourly window, there's no Retry-After
- Create the service account with only read_items on one vault and --expires-in set to the job length, since permissions can't be narrowed later
- Set integrationName and integrationVersion in createClient so the usage report shows which agent read what
- Don't ask the Environments MCP server for a value. Use it to find the variable name, then load it with op run or the SDK
- To sign in to a person's websites without seeing the password, Agentic Autofill is partner preview only; contact 1Password's partnerships team before building on it
Bitwarden Secrets Manager
- Create one machine account per agent with Can read on one project, and give its token an expiry date rather than the default of never
- Run the agent under
bws run -- <cmd>so secrets arrive as environment variables and aren't written to disk or into the context - Fetch with
bws secret list <project-id> --output jsononce per run;bws secret getneeds the secret's UUID, not its name - Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud
- Rotate the secret's value as well as revoking the token in an emergency, since a live session can read for up to an hour
Questions
Which is better for AI agents, 1Password service accounts, SDKs and Environments MCP or Bitwarden Secrets Manager?
1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in every scored category.
Other comparisons with 1Password service accounts, SDKs and Environments MCP or Bitwarden Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Akeyless (SecretlessAI and MCP server)
- 1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Azure Key Vault
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server
- 1Password service accounts, SDKs and Environments MCP vs Infisical
- 1Password service accounts, SDKs and Environments MCP vs Keeper Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Phase
- 1Password service accounts, SDKs and Environments MCP vs Pulumi ESC
- Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager
- AWS Secrets Manager vs Bitwarden Secrets Manager
- Azure Key Vault vs Bitwarden Secrets Manager
- Bitwarden Secrets Manager vs Doppler
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server
- Bitwarden Secrets Manager vs Infisical
- Bitwarden Secrets Manager vs Keeper Secrets Manager
- Bitwarden Secrets Manager vs Phase
- Bitwarden Secrets Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/1password-vs-bitwarden-secrets-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/1password.json·/api/v1/tools/bitwarden-secrets-manager.json - From a terminal
anchor compare 1password bitwarden-secrets-manager(the CLI) - Over MCP
compare_tools {"a": "1password", "b": "bitwarden-secrets-manager"}at/mcp, no key