Head to head · Secrets storage · October 2026 research run
1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 4 of 7 scored categories. 1Password service accounts, SDKs and Environments MCP leads on security & auth and payments & pricing. 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
- Security & auth, 94 against 80
- Payments & pricing, 45 against 30
Also in its favour
- Runs on your own machine
Watch for
Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After
Google Cloud Secret Manager BB
Best for Agents on GKE, Cloud Run or GCE that should read secrets through workload identity with per-secret, time-bound grants.
Ahead on
- Reliability, 87 against 68
- Schema & documentation, 83 against 74
- Agent ergonomics, 82 against 69
- Maintenance & community, 87 against 82
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle
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 Google Cloud Secret Manager +19
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).
Google Cloud Secret Manager 87
Google Cloud status dashboard with incident history (20). The incidents.json we read on 1 November has nothing tagged Secret Manager. In the 90 days from 3 August it lists a us-west1 outage on 20 August, us-central1-b network degradation on 1 September, Cloud Storage errors from 8 to 9 October and a europe-west2 incident on 20 October (06:00 to 12:08 UTC, 38 products), new since 17 October, none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second (120 a minute) on a global secret and 80 a second on a regional one, and 1 and 50 state changes a second per version, on the page updated 26 October (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, unchanged on 1 November (10). Generally available; regional Cloud SQL rotation is the preview part (10). 20+25+15+7+10+10 = 87.
Payments & pricing 1Password service accounts, SDKs and Environments MCP +15
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.
Google Cloud Secret Manager 30
No x402, MPP or L402 (0). Per-unit prices public, $0.000082192 an hour per active version (about $0.06 a month), $0.03 per 10,000 accesses and $0.05 per rotation notification, unchanged on 1 November (20). Always free each month for 6 active versions, 10,000 accesses and 3 rotation notifications, plus $300 trial credit, but the Free Trial page says sign-up needs a credit card or other payment method, re-read on 1 November (0). A person creates the Google Cloud account and billing account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Security & auth 1Password service accounts, SDKs and Environments MCP +14
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).
Google Cloud Secret Manager 80
OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30), less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v1 discovery document (revision 20261021) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to secretmanager.googleapis.com came back 'Request had invalid authentication credentials', where no token gives 'missing required authentication credential'. That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (20). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). google.com security.txt valid to 2030-04-01 with a VRP policy link and Secret Manager in Google Cloud's SOC 2 scope, both re-read on 1 November, and public security bulletins, none through GCP-2026-074 (28 October) naming Secret Manager since July; the two 2026 bulletins that mention Secret Manager (GCP-2026-042, Cloud Build, 24 June, and GCP-2026-048, Developer Connect, 13 July) fixed caller permission checks in those products, not in Secret Manager (20).
Agent ergonomics Google Cloud Secret Manager +13
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).
Google Cloud Secret Manager 82
accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server, and Secret Manager isn't on Google Cloud's list of managed MCP servers (updated 30 October 2026); the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.
Schema & documentation Google Cloud Secret Manager +9
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.
Google Cloud Secret Manager 83
A REST discovery document and the protobuf definitions in googleapis, with field behaviours marking required members (25). No llms.txt at docs.cloud.google.com or under /secret-manager/docs, both 404 again on 1 November (0). The reference describes each method, and the guides say to pin a version rather than rely on latest in production (16 of 20). Proto types, enums for version state and replication, required fields, and no free-form blobs besides the payload (15). Code samples in several languages on each how-to page and the standard google.rpc error model (12 of 15). v1 is stable and the release notes are dated, the newest still 14 September 2026 on 1 November (15).
Maintenance & community Google Cloud Secret Manager +5
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).
Google Cloud Secret Manager 87
@google-cloud/secret-manager 7.2.0 (npm, 12 October 2026, per the 17 October check; the secret-manager-v7.2.0 tag is still the newest in googleapis/google-cloud-node on 1 November), 20 days old. The newest release note is still 14 September 2026, a Parameter Manager change, so the award rests on the client, as on the Google Workspace listings (30). Dated release notes on 12 August, 8 September and 14 September, and Node.js client releases 7.0.0 (10 August), 7.1.0 (8 September), 7.1.1 (28 September) and 7.2.0, all in the 90 days from 3 August (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Node.js 7.2.0 and Python 2.31.0 (1 October, per the 6 October check; the google-cloud-secret-manager-v2.31.0 tag is still the newest on 1 November) (15). Generated libraries released from the googleapis monorepos with CI (10).
Score by category
| Category | Weight | 1Password service accounts, SDKs and Environments MCP | Google Cloud Secret Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 87 | Google Cloud Secret Manager +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 83 | Google Cloud Secret Manager +9 |
| Agent ergonomics | 13% | 69 | 82 | Google Cloud Secret Manager +13 |
| Security & auth | 14% | 94 | 80 | 1Password service accounts, SDKs and Environments MCP +14 |
| Payments & pricing | 10% | 45 | 30 | 1Password service accounts, SDKs and Environments MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 87 | Google Cloud Secret Manager +5 |
| Transparency & trust | 7% | 87 | 84 | 1Password service accounts, SDKs and Environments MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 73.7/100 | BB 76.9/100 |
Facts side by side
| Fact | 1Password service accounts, SDKs and Environments MCP | Google Cloud Secret Manager |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | 1Password | Google Cloud |
| Hosted endpoint | no (local only) | https://secretmanager.googleapis.com/v1 |
| Transports | stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | MIT | Apache-2.0 (client libraries) |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-10-12 |
| Terms last updated | 2024-09-12 | 2026-09-02 |
| Privacy policy last updated | 2025-12-29 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| 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 | 4.2M npm/wk, 13.6M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.6/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Google Cloud Secret Manager higher.
| Reviewer | 1Password service accounts, SDKs and Environments MCP | Google Cloud Secret Manager |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 listAll became list in a version 0 minor | 4/5 Dated notes and no deprecations since May |
| WardenSecurity auditor | 4/5 Vault scopes that can't be widened later | 4/5 No API keys, and reads unlogged until you ask |
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.
Google Cloud Secret Manager
Workload identity on GKE, Cloud Run and GCE, so no key in the agent, and API keys are refused. Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle.
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
Google Cloud Secret Manager
- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
- Read once per run and cache; accesses past 10,000 a month are metered
- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there
Questions
Which is better for AI agents, 1Password service accounts, SDKs and Environments MCP or Google Cloud Secret Manager?
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 4 of 7 scored categories. 1Password service accounts, SDKs and Environments MCP leads on security & auth and payments & pricing.
Can an agent call 1Password service accounts, SDKs and Environments MCP and Google Cloud Secret Manager without installing anything?
1Password service accounts, SDKs and Environments MCP runs on your own machine, with no hosted endpoint listed. Google Cloud Secret Manager has a hosted endpoint at https://secretmanager.googleapis.com/v1.
Other comparisons with 1Password service accounts, SDKs and Environments MCP or Google Cloud Secret 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 Bitwarden Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- 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 Google Cloud Secret Manager
- AWS Secrets Manager vs Google Cloud Secret Manager
- Azure Key Vault vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Doppler vs Google Cloud Secret Manager
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Infisical
- Google Cloud Secret Manager vs Keeper Secrets Manager
- Google Cloud Secret Manager vs Phase
- Google Cloud Secret Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/1password-vs-google-secret-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/1password.json·/api/v1/tools/google-secret-manager.json - From a terminal
anchor compare 1password google-secret-manager(the CLI) - Over MCP
compare_tools {"a": "1password", "b": "google-secret-manager"}at/mcp, no key