Head to head · Secrets storage · October 2026 research run

Doppler vs HashiCorp Vault + Vault MCP Server

Doppler scores 71.9 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on agent ergonomics and transparency & trust. Both do secrets storage.

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

Which one, for what

Doppler BB

Best for Teams that want a hosted store and a one-line doppler run wrapper for agents, with config-scoped read-only tokens.

Ahead on

  • Reliability, 80 against 66
  • Schema & documentation, 81 against 74

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them

Watch for

Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts

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

  • Agent ergonomics, 64 against 59
  • Transparency & trust, 80 against 75

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.

Reliability Doppler +14

Doppler 80

Atlassian Statuspage at www.dopplerstatus.com with an incident history back to 2023 (20). In the 90 days from 3 August, re-read from the history feed on 1 November, the one incident is elevated timeouts for the dashboard, CLI and API on 27 October, posted at 12:26 PDT and resolved at 13:25 PDT (59 minutes), filed against the API and Dashboard components at minor impact. Timeouts rather than an outage, and under an hour, so minor (20 of 30, was 30). The 16 July CLI download failure has left the window, and the last API outages were on 18 and 20 November 2025. Rate limits published per plan, 240 reads, 120 secret reads and 60 writes a minute on Developer (15). A 429 carries retry-after in seconds plus x-ratelimit-limit, -remaining and -reset headers, but there's no retry guidance for writes (13 of 15). The Enterprise plan card lists a 99.95% SLO, an objective rather than an agreement, though the comparison table on the same page labels the row 99.95% SLA, and no SLA appears for Team (5 of 10). The API is generally available and the MCP server is marked experimental (7 of 10). 20 + 20 + 15 + 13 + 5 + 7 = 80.

HashiCorp Vault + Vault MCP Server 66

Status page at status.hashicorp.com (incident.io) with history for HCP products, including HCP Vault Dedicated components (20). From 4 August to 2 November 2026 one incident named Vault. HCP Vault Dedicated Azure cluster updates and creation failed from 3 to 9 October, one operation on one cloud, not the Vault API, so it reads as partial. New disaster recovery cluster creation also failed on 6 August, in an incident that names no product or component; read as Vault's, it was partial too. Minor only (20). The other incidents were on HCP Terraform, Infragraph, Vault Radar, provider downloads and releases.hashicorp.com. Rate limit quotas are documented and configurable, but no default figures are published for HCP or a fresh install (7 of 15). Quotas can send Retry-After and X-Ratelimit headers when enable_rate_limit_response_headers is set, and KV v2 has check-and-set for safe writes (12 of 15). No SLA found on the IBM price table, and HashiCorp's own pricing page wasn't re-read on 2 November (0). The HTTP API is generally available, while the MCP server is still marked beta in its docs (7 of 10).

Schema & documentation Doppler +7

Doppler 81

OpenAPI 3.1 at docs.doppler.com/openapi/core.json, 47 paths and 89 operations in the copy we read, with 4xx response schemas and a security scheme (25). llms.txt at docs.doppler.com with about 500 links to Markdown versions of the guides and API reference (10). Operation summaries are one word ("List", "Retrieve", "Download"), and the MCP tools inherit them, so a model learns little about when to use each (10 of 20). Typed parameters from the OpenAPI, carried into the generated MCP schemas (12 of 15). Error responses are defined in the spec, but the reference only describes them by status range (10 of 15). /v3 versioned paths, a monthly changelog (July and August 2026 entries) and semver CLI releases (14 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 +5

Doppler 59

With no flags the MCP server exposes one tool per API operation, up to 89 in the spec we read; --read-only cuts that to the 36 GET operations and --config to 10 config and secret tools. The API has /secrets/names for names without values and a download endpoint for a whole config in one call (18 of 25). page and per_page on the list endpoints (15 of 20). Errors come back with a messages array and a status code, and the reference documents them only by range (10 of 20). No MCP tool annotations (read-only is a startup flag instead) and no idempotency keys (6 of 20). doppler run needs only a token, and the MCP server infers project and config from a scoped token; we didn't confirm current official SDKs beyond the CLI (10 of 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 +5

Doppler 75

CLI and MCP server are Apache-2.0, the platform is closed under clear terms (18 of 30). Privacy notice of 17 September 2026 per the 30 September check, not re-read on 1 November, a DPA, and a subprocessor list dated 13 July 2026 with 9 entries, consistent with the fact sheet's single GCP us-central1 region; retention periods aren't stated (24 of 30). No deprecation policy or dated deprecation notices found (8 of 20). Subprocessors and data location are disclosed, but the CLI sends anonymous command analytics by default, with an analytics flag to turn it off that the README doesn't mention (14 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).

Score by category

CategoryWeightDopplerHashiCorp Vault + Vault MCP ServerEdge
Reliability16%8066Doppler +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8174Doppler +7
Agent ergonomics13%5964HashiCorp Vault + Vault MCP Server +5
Security & auth14%8286HashiCorp Vault + Vault MCP Server +4
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7677HashiCorp Vault + Vault MCP Server +1
Transparency & trust7%7580HashiCorp Vault + Vault MCP Server +5
Negative events≤150-15
TotalBB 71.9/100C 55/100

Facts side by side

FactDopplerHashiCorp Vault + Vault MCP Server
KindHTTP APIHTTP API
VendorDopplerHashiCorp (IBM)
Hosted endpointhttps://api.doppler.com/v3no (local only)
TransportsHTTP, stdioHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (MCP server and CLI), closed platformBUSL-1.1 (Vault), MPL-2.0 (MCP server)
Tools exposednone16
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-222026-10-22
Terms last updated2026-02-08couldn't be read
Privacy policy last updated2026-09-17couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity8 stars, 3.3k npm/wk36k stars
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Doppler

Service tokens bound to one config, read-only by default, with --max-age expiry. Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts.

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

Doppler

  1. Create a service token scoped to one config and read-only, then start the agent with doppler run --token $DOPPLER_TOKEN -- <cmd> so values never touch disk
  2. Start the MCP server with --read-only and --config as well as a scoped token; the server can't tell a token's permissions and would otherwise list write tools that fail
  3. Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call
  4. On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer
  5. Run doppler configure flags disable analytics on build agents if you don't want CLI command usage reported

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, Doppler or HashiCorp Vault + Vault MCP Server?

Doppler scores 71.9 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on agent ergonomics and transparency & trust.

Do Doppler and HashiCorp Vault + Vault MCP Server need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Doppler and HashiCorp Vault + Vault MCP Server without installing anything?

Doppler has a hosted endpoint at https://api.doppler.com/v3. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.

Other comparisons with Doppler 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.