Head to head · Secrets storage · October 2026 research run
1Password service accounts, SDKs and Environments MCP vs Doppler
1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against Doppler's 71.9 (BB), and leads in 4 of 7 scored categories. Doppler leads on reliability and schema & documentation. 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
- Agent ergonomics, 69 against 59
- Security & auth, 94 against 82
- Maintenance & community, 82 against 76
- Transparency & trust, 87 against 75
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 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
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 68
- Schema & documentation, 81 against 74
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts
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 +12
1Password service accounts, SDKs and Environments MCP 68
Atlassian Statuspage at status.1password.com with per-region components for CLI, Connect, Service Accounts, Admin console and the Events API (20). In the 90 days to 1 November 2026 the history shows three incidents, with nothing posted after 20 October, Device Trust (9 September, about 30 minutes), vault profiles not showing in the web interface (16 October, minor, about 10 minutes, Admin console) and a high error rate on 1Password.com (16 to 20 October), which Statuspage marks major and posts against the Admin console in the US/Global region only, with a fix deployed about three and a half hours after it was opened. None was posted against Service Accounts or Connect, so minor only for the agent path (20); a reviewer may count the 16 October Admin console incident as a major outage, which would make this line 10. Rate limits published per token and per account for every plan, unchanged on 1 November (15). The 429 messages are documented, but there's no Retry-After or backoff guidance, only a note to wait for the window or upgrade (8 of 15). No SLA found for any plan (0). Service accounts, the CLI and Environments are generally available, and CLI 2.41.0 made op run --environment generally available, while the SDKs are version 0; the MCP server page no longer labels the server beta, though its Claude Code, Cursor and Kiro set-ups are (5 of 10).
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.
Security & auth 1Password service accounts, SDKs and Environments MCP +12
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).
Doppler 82
Service tokens are bound to one config, read-only by default and can expire with --max-age, and service account identities trade an OIDC token for a short-lived Doppler token on Team and above. The CLI keeps serving its encrypted fallback file after a token is revoked (27 of 30). Read-only tokens, the MCP server's --read-only and --config flags, and startup warnings when a production config or write tools are exposed (17 of 20). Secrets aren't untrusted content; the MCP README tells you to scope tokens and review output, and there's no value masking (10 of 15). Activity logs for 3 days on Developer and 90 on Team, and the security fact sheet says every secret change is logged, but we found no per-read access log (10 of 15). SOC 2 and ISO 27001 claimed on the security page, re-read on 1 November, a trust centre, a HackerOne bug bounty linked from that page, and a published list of customer-affecting vulnerabilities. www.doppler.com/.well-known/security.txt redirects to dashboard.doppler.com, whose robots.txt disallows the path, so we didn't read it (18 of 20).
Transparency & trust 1Password service accounts, SDKs and Environments MCP +12
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).
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).
Agent ergonomics 1Password service accounts, SDKs and Environments MCP +10
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).
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).
Schema & documentation Doppler +7
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.
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).
Maintenance & community 1Password service accounts, SDKs and Environments MCP +6
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).
Doppler 76
CLI 3.77.1 on 22 October 2026 (a Go update), after 3.77.0 on 7 October with a new tags command, 10 days before this check (30). Eight CLI tags from 3.76.1 (21 July) to 3.77.1, of which 3.76.2 to 3.77.1 fall in the 90 days, plus a September 2026 changelog entry (20). 35 open CLI issues, and most of the ten newest had no reply, including a panic report (#560) and one about secrets delete printing every value (#542), per the 1 October check, not re-read on 1 November (10 of 25). The CLI and the MCP server (1.0.5, 4 June 2026, no newer tag on 1 November) are official; the MCP server isn't in the MCP registry per the 30 September check, and we didn't confirm other SDKs (7 of 15). Both repositories run tests in CI, the CLI has a vulncheck workflow and the MCP server's dependencies were audited on 28 August 2026 (9 of 10). 30 + 20 + 10 + 7 + 9 = 76.
Score by category
| Category | Weight | 1Password service accounts, SDKs and Environments MCP | Doppler | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 80 | Doppler +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 81 | Doppler +7 |
| Agent ergonomics | 13% | 69 | 59 | 1Password service accounts, SDKs and Environments MCP +10 |
| Security & auth | 14% | 94 | 82 | 1Password service accounts, SDKs and Environments MCP +12 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 76 | 1Password service accounts, SDKs and Environments MCP +6 |
| Transparency & trust | 7% | 87 | 75 | 1Password service accounts, SDKs and Environments MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 73.7/100 | BB 71.9/100 |
Facts side by side
| Fact | 1Password service accounts, SDKs and Environments MCP | Doppler |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | 1Password | Doppler |
| Hosted endpoint | no (local only) | https://api.doppler.com/v3 |
| Transports | stdio | HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | MIT | Apache-2.0 (MCP server and CLI), closed platform |
| Tools exposed | 8 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-22 |
| Terms last updated | 2024-09-12 | 2026-02-08 |
| Privacy policy last updated | 2025-12-29 | 2026-09-17 |
| 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 | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 110 stars, 1M npm/wk, 817k PyPI/wk | 8 stars, 3.3k npm/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates 1Password service accounts, SDKs and Environments MCP higher.
| Reviewer | 1Password service accounts, SDKs and Environments MCP | Doppler |
|---|---|---|
| WardenSecurity auditor | 4/5 Vault scopes that can't be widened later | 3/5 Read-only tokens, and an MCP server that lists deletes |
| KeelOperations and maintenance reviewer | 3/5 listAll became list in a version 0 minor | 3/5 An MCP tool list rebuilt from the spec at start-up |
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.
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.
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
Doppler
- 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 - 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
- Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call
- On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer
- Run
doppler configure flags disable analyticson build agents if you don't want CLI command usage reported
Questions
Which is better for AI agents, 1Password service accounts, SDKs and Environments MCP or Doppler?
1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against Doppler's 71.9 (BB), and leads in 4 of 7 scored categories. Doppler leads on reliability and schema & documentation.
Can an agent call 1Password service accounts, SDKs and Environments MCP and Doppler without installing anything?
1Password service accounts, SDKs and Environments MCP runs on your own machine, with no hosted endpoint listed. Doppler has a hosted endpoint at https://api.doppler.com/v3.
Other comparisons with 1Password service accounts, SDKs and Environments MCP or Doppler
- 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 Bitwarden Secrets Manager
- 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 Doppler
- AWS Secrets Manager vs Doppler
- Azure Key Vault vs Doppler
- Bitwarden Secrets Manager vs Doppler
- Doppler vs Google Cloud Secret Manager
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Infisical
- Doppler vs Keeper Secrets Manager
- Doppler vs Phase
- Doppler vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/1password-vs-doppler.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/1password.json·/api/v1/tools/doppler.json - From a terminal
anchor compare 1password doppler(the CLI) - Over MCP
compare_tools {"a": "1password", "b": "doppler"}at/mcp, no key