Head to head · Secrets storage · October 2026 research run

Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server

Bitwarden Secrets Manager scores 57.5 (C) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 0 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on schema & documentation, agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust. Both do secrets storage.

Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons

Which one, for what

Bitwarden Secrets Manager C

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
  • No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them

Watch for

No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024

HashiCorp Vault + Vault MCP Server C

Best for Platform teams that already run Vault or need dynamic database and cloud credentials with leases, and for enterprises that want agent identities with ceiling policies.

Ahead on

  • Schema & documentation, 74 against 53
  • Agent ergonomics, 64 against 52
  • Security & auth, 86 against 76
  • Payments & pricing, 45 against 38
  • Maintenance & community, 77 against 36
  • Transparency & trust, 80 against 69

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased

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 HashiCorp Vault + Vault MCP Server +41

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.

HashiCorp Vault + Vault MCP Server 77

Vault 2.2.1 on 22 October 2026, 11 days before this check (30). 2.0.4 (4 August), 2.1.0 (1 September), 2.1.1 (16 September), 2.1.2 (7 October), 2.2.0 (15 October) and 2.2.1 (22 October), plus sdk/v0.26.0 (24 September) and 1.21.x Enterprise patches (20). 1.2k open issues with open regressions from 29 July (#32059) and 5 August (#32072), per the 1 October check; GitHub's pages answered 403 on 2 November (12 of 25). Only the Go client is official, and the MCP server still isn't in the MCP registry, where HashiCorp lists only the Terraform server (8 of 15). CI runs Go tests, security scans and Enos scenarios, but the MCP server's newest binary is still 0.2.0 from 24 September 2025 on releases.hashicorp.com (7 of 10).

Schema & documentation HashiCorp Vault + Vault MCP Server +21

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).

HashiCorp Vault + Vault MCP Server 74

Every Vault server generates an OpenAPI document at /v1/sys/internal/specs/openapi from its mounted paths, so the contract matches the plugins you run, though it isn't a static file you can read before installing (22 of 25). No llms.txt at developer.hashicorp.com or under /vault (both 404) (0). API pages state purpose per endpoint, and the MCP tools say when to be careful (delete_mount says "Use with extreme caution"), but none say when not to use them (14 of 20). Typed parameters in the OpenAPI and typed, required arguments on the 16 MCP tools (12 of 15). Sample requests and responses on each API page and a documented errors array with status codes (13 of 15). /v1 is stable and CHANGELOG.md dates every release with BREAKING CHANGES sections, but the MCP server's changelog lists a 0.2.1 that was never released (13 of 15).

Agent ergonomics HashiCorp Vault + Vault MCP Server +12

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).

HashiCorp Vault + Vault MCP Server 64

The MCP server has 16 tools with no toolsets or read-only subset (15 of 25, KV and LIST responses are small). LIST returns keys only and KV v2 reads one version, but there's little paging or filtering on most LIST endpoints (10 of 20). Errors come back as an errors array of strings with an HTTP status, which says permission denied without naming the missing capability (12 of 20). Every MCP tool carries readOnlyHint or destructiveHint, and KV v2 writes take a cas version for safe retries (17 of 20). The official client is the Go api package; Python (hvac) and Node clients are community. Vault Agent and Vault Proxy handle auto-auth, renewal and caching so an app reads a file or a local socket (10 of 15).

Transparency & trust HashiCorp Vault + Vault MCP Server +11

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).

HashiCorp Vault + Vault MCP Server 80

Vault is BUSL-1.1 with IBM as licensor, converting to MPL 2.0 four years after each version, and the MCP server is MPL-2.0. Source is public with clear terms, but the BUSL isn't an OSI licence (18 of 30). Privacy policy of 20 April 2026 per the 30 September check, and self-hosted Community sends nothing to HashiCorp; we didn't read an HCP DPA or subprocessor list (15 of 30). Dated end-of-sale and end-of-life notices for HCP Vault Secrets and BREAKING CHANGES sections in the changelog (16 of 20). The Community build stubs out the census reporter, so nothing phones home; Enterprise licence reporting wasn't checked (16 of 20).

Security & auth HashiCorp Vault + Vault MCP Server +10

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.

HashiCorp Vault + Vault MCP Server 86

Tokens carry TTLs and path policies, machines log in with AppRole, Kubernetes, JWT/OIDC, AWS, GCP, Azure or TLS certificates, dynamic secrets get leases that revoke on expiry, and Enterprise 2.x adds an OAuth resource server so an agent can present a JWT instead of a Vault token (30). Path ACLs with explicit deny and read-only capabilities, control groups for approvals on Enterprise, and agent ceiling policies on Enterprise; the MCP server has no read-only mode (17 of 20). Secrets aren't untrusted content, but the MCP README warns that queries may expose secrets to the client and the model (10). Audit devices (file, syslog, socket) on every edition, with HMAC'd values (15). security.txt with a contact and policy but no Expires field per the 1 October check (hashicorp.com answered 429 on 2 November), and HashiCorp publishes HCSEC bulletins with CVEs in public (12 for Vault between 17 April and 7 October 2026), but security fixes in the MCP server (28 July and 11 August 2026) and Vault's Raft join fix (on main since 15 October) are in no release (14 of 20).

Payments & pricing HashiCorp Vault + Vault MCP Server +7

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.

HashiCorp Vault + Vault MCP Server 45

No x402, MPP or L402 (0). HCP Vault Dedicated hourly prices per cluster and $72.92 a client a month are public on the IBM price table, marked indicative (20). A $500 HCP trial credit, and the pricing pages don't say whether a card is needed (10 of 20). A person signs up for HCP and creates the cluster, and there's no programmatic signup (0). Vault Community self-hosts free under the BUSL-1.1, but the rubric scores the paid option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightBitwarden Secrets ManagerHashiCorp Vault + Vault MCP ServerEdge
Reliability16%6666even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5374HashiCorp Vault + Vault MCP Server +21
Agent ergonomics13%5264HashiCorp Vault + Vault MCP Server +12
Security & auth14%7686HashiCorp Vault + Vault MCP Server +10
Payments & pricing10%3845HashiCorp Vault + Vault MCP Server +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3677HashiCorp Vault + Vault MCP Server +41
Transparency & trust7%6980HashiCorp Vault + Vault MCP Server +11
Negative events≤150-15
TotalC 57.5/100C 55/100

Facts side by side

FactBitwarden Secrets ManagerHashiCorp Vault + Vault MCP Server
KindSDK + MCPHTTP API
VendorBitwardenHashiCorp (IBM)
Hosted endpointhttps://api.bitwarden.comno (local only)
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceBitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closedBUSL-1.1 (Vault), MPL-2.0 (MCP server)
Tools exposednone16
Read-only variant documentednono
llms.txtnono
Last release2026-05-222026-10-22
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity480 stars, 24k npm/wk, 25k PyPI/wk36k stars
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates HashiCorp Vault + Vault MCP Server higher, the other way from the total score.

ReviewerBitwarden Secrets ManagerHashiCorp Vault + Vault MCP Server
KeelOperations and maintenance reviewer 2/5 Releases at 2.1.0, changelog stuck at 1.0.0 3/5 Breaking changes in 2.0.4, an MCP build from 2025
WardenSecurity auditor 3/5 Decrypted on the client, readable for an hour after revoke 3/5 Sound engine, MCP build missing two security fixes

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

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.

HashiCorp Vault + Vault MCP Server

Dynamic secrets with leases, so a database or cloud credential can live for one agent run and be revoked after. HashiCorp published 12 Vault security bulletins between April and October 2026, and the MCP server's newest build is still 0.2.0 from September 2025, with security fixes from July and August 2026 unreleased.

Before you call either

Bitwarden Secrets Manager

  1. 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
  2. Run the agent under bws run -- <cmd> so secrets arrive as environment variables and aren't written to disk or into the context
  3. Fetch with bws secret list <project-id> --output json once per run; bws secret get needs the secret's UUID, not its name
  4. Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud
  5. 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

HashiCorp Vault + Vault MCP Server

  1. Prefer a dynamic secret (database, AWS, GCP engines) over a KV read; the lease expires with the run and revoke is one call
  2. Log in with AppRole or Kubernetes auth and keep the token for its TTL. Renew with auth/token/renew-self rather than logging in per request
  3. For KV v2, GET /v1/<mount>/data/<path> and read data.data, and pass cas on writes so a retry can't overwrite a newer version
  4. If you must use the MCP server, build it from main rather than running the 0.2.0 image, run it over stdio, and give it a token limited to one mount
  5. Ask your operator for Vault 2.2.1 or later (2.1.2 fixes four bulletins of 7 October) and to set enable_rate_limit_response_headers so a 429 carries Retry-After

Questions

Which is better for AI agents, Bitwarden Secrets Manager or HashiCorp Vault + Vault MCP Server?

Bitwarden Secrets Manager scores 57.5 (C) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 0 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on schema & documentation, agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust.

Can an agent call Bitwarden Secrets Manager and HashiCorp Vault + Vault MCP Server without installing anything?

Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.

Other comparisons with Bitwarden Secrets Manager or HashiCorp Vault + Vault MCP Server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.