# 1Password service accounts, SDKs and Environments MCP vs Doppler

> Doppler has a score of 71.6 (BB) against 1Password service accounts, SDKs and Environments MCP's 69.9 (B). Both do secrets store. The largest gap is reliability, 22 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/1password-vs-doppler
- Markdown: https://www.anchorterminal.com/compare/1password-vs-doppler.md (~1,800 tokens)
- Slim: https://www.anchorterminal.com/compare/1password-vs-doppler.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/1password-vs-doppler.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

Doppler has a score of 71.6 (BB) against 1Password service accounts, SDKs and Environments MCP's 69.9 (B). Both do secrets store. The largest gap is reliability, 22 points.

- 1Password service accounts, SDKs and Environments MCP: grade B, 69.9/100, rank #104 of 452. Markdown https://www.anchorterminal.com/tools/1password.md · JSON https://www.anchorterminal.com/api/v1/tools/1password.json
- Doppler: grade BB, 71.6/100, rank #79 of 452. Markdown https://www.anchorterminal.com/tools/doppler.md · JSON https://www.anchorterminal.com/api/v1/tools/doppler.json

## Which one, for what

Pick 1Password service accounts, SDKs and Environments MCP for agent ergonomics (+10), security & auth (+12), transparency & trust (+12).

Pick Doppler for reliability (+22), schema & documentation (+7), payments & pricing (+5).

## Score by category

| Category | Weight | 1Password service accounts, SDKs and Environments MCP | Doppler | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 90 | Doppler +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 74 | 81 | Doppler +7 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 59 | 1Password service accounts, SDKs and Environments MCP +10 |
| Security & auth | 14% (17.5 this run) | 94 | 82 | 1Password service accounts, SDKs and Environments MCP +12 |
| Payments & pricing | 10% (12.5 this run) | 20 | 25 | Doppler +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 72 | 76 | Doppler +4 |
| Transparency & trust | 7% (8.8 this run) | 89 | 77 | 1Password service accounts, SDKs and Environments MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.9 · B** | **71.6 · BB** | |

## Facts side by side

| Fact | 1Password service accounts, SDKs and Environments MCP | Doppler |
| --- | --- | --- |
| Kind | Model 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 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-07-31 | 2026-09-21 |
| Popularity | 110 stars, 1M npm/wk, 817k PyPI/wk | 8 stars, 3.3k npm/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |

## 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

1. Read secrets by reference (op://vault/item/field) with client.secrets.resolve or resolveAll, and keep the reference, not the value, in config
2. 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
3. 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
4. Set integrationName and integrationVersion in createClient so the usage report shows which agent read what
5. 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

### 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

## 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)](https://www.anchorterminal.com/compare/1password-vs-akeyless.md)
- [1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager.md)
- [1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-bitwarden-secrets-manager.md)
- [1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/1password-vs-google-secret-manager.md)
- [1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/1password-vs-hashicorp-vault.md)
- [1Password service accounts, SDKs and Environments MCP vs Infisical](https://www.anchorterminal.com/compare/1password-vs-infisical.md)
- [Akeyless (SecretlessAI and MCP server) vs Doppler](https://www.anchorterminal.com/compare/akeyless-vs-doppler.md)
- [AWS Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.md)
- [Bitwarden Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.md)
- [Doppler vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/doppler-vs-google-secret-manager.md)
- [Doppler vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.md)
- [Doppler vs Infisical](https://www.anchorterminal.com/compare/doppler-vs-infisical.md)