Head to head · Secrets storage · October 2026 research run

1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager

AWS Secrets Manager scores 80.3 (A) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 3 of 7 scored categories. 1Password service accounts, SDKs and Environments MCP leads on 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

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

  • Maintenance & community, 82 against 70
  • Transparency & trust, 87 against 80

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

AWS Secrets Manager A

Best for Agents running on AWS compute that should read credentials through a role with no key at all, and for RDS-family databases that need managed rotation.

Ahead on

  • Reliability, 77 against 68
  • Schema & documentation, 96 against 74
  • Agent ergonomics, 90 against 69

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

Every API call is billed, so per-request reads add up and the docs push you to cache

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.

Schema & documentation AWS Secrets Manager +22

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.

AWS Secrets Manager 96

Machine-readable service models (secretsmanager-2017-10-17) ship in every AWS SDK, with types, length limits, patterns and required members (25). llms.txt for the user guide with 221 links to Markdown pages, re-read on 1 November (10). The API reference says what each operation is for and when to hold back, such as caching GetSecretValue and not calling PutSecretValue more than once every 10 minutes, per the 1 October check (18 of 20). Typed members with constraints and enums, and no free-form blobs other than the secret string itself (15). Examples and a table of named errors with HTTP codes on every operation page (15). Dated API version and SDK changelogs. The user guide's document history loads at document-history.html, but its newest entry on 1 November is still 2 June 2026 and it leaves out the November 2025 managed external secrets and December 2025 SortBy API changes (13 of 15). 25 + 10 + 18 + 15 + 15 + 13 = 96.

Agent ergonomics AWS Secrets Manager +21

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

AWS Secrets Manager 90

GetSecretValue returns one secret, DescribeSecret returns metadata without the value, and BatchGetSecretValue takes a list of IDs or filters (20 of 25). ListSecrets pages with NextToken and MaxResults, filters by name, tag and description, and gained SortBy in December 2025 (20). Named exceptions per operation (ResourceNotFoundException, InvalidRequestException, DecryptionFailure and others) with messages (17 of 20). ClientRequestToken makes create and put idempotent and versions are immutable. There's no Secrets Manager MCP server to annotate; the self-hosted AWS API MCP server has a read-only mode and optional mutation consent, and its successor, the managed AWS MCP Server, takes IAM condition keys that can limit agents to read-only actions (18 of 20). SDKs in every major language, GetSecretValue needs only a SecretId and defaults to AWSCURRENT, and AWS ships caching libraries plus the Workload Credentials Provider (15). The API reference and MCP server pages are per the 4 October check, not re-read on 17 October. 20 + 20 + 17 + 18 + 15 = 90.

Maintenance & community 1Password service accounts, SDKs and Environments MCP +12

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

AWS Secrets Manager 70

AWS's open-source client for the service, the Workload Credentials Provider (formerly the Secrets Manager Agent), released 3.1.2 on 27 October 2026 (tag v3.1.2, on crates.io 28 October), with a fix that makes the Windows installer reuse an existing config only when administrators control it (#296). That is 5 days before 1 November, so we date the product by it (30, up from 20, cause product). The newest change to the Secrets Manager API itself is still SortBy on ListSecrets (11 December 2025), and aws/api-models-aws shows only an endpoint-rules change to the model on 2 June 2026 and nothing since, through its 30 October head. One dated release in the 90 days from 3 August (3.1.2), since 3.1.1 of 21 July has left the window (5 of 20). Public document history at document-history.html, still with one 2026 entry (2 June), plus AWS Support and re:Post (10 of 15). Current official SDKs in every major language (15). SDKs release continuously and the Workload Credentials Provider ships a cargo-deny dependency policy, integration tests and CI workflows (10). 30 + 5 + 10 + 15 + 10 = 70.

Reliability AWS Secrets Manager +9

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

AWS Secrets Manager 77

AWS Health Dashboard with per-service, per-region status, RSS feeds and a public history file (20). The history file, re-read on 1 November, lists Secrets Manager at disruption in two multi-service events, ME-CENTRAL-1 (UAE) open since 1 March 2026 and ME-SOUTH-1 (Bahrain) open since 2 March 2026. On 15 September 2026, inside the 90-day window from 3 August, AWS said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in me-south-1, and neither event has had an update since. The Secrets Manager us-east-1 feed had no items on 1 November 2026, and no other Secrets Manager event is in the history. Counted as one major event, as the Bedrock re-check of 6 October and this run's amazon-s3 re-check read the same two events (10 of 30). Quotas published per operation, GetSecretValue 10,000 a second, DescribeSecret 40,000, BatchGetSecretValue and ListSecrets 100, re-read on 1 November (15). Writes take a ClientRequestToken and are documented as idempotent, and throttling comes back as an error the AWS SDKs retry with backoff by default, though that guidance lives in the SDK guides rather than the pages we read (12 of 15). SLA of 99.99% monthly uptime per region with 10, 25 and 100 per cent credits, last updated 5 December 2023 and unchanged on 1 November 2026 (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.

Transparency & trust 1Password service accounts, SDKs and Environments MCP +7

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

AWS Secrets Manager 80

Closed service under AWS Service Terms updated 30 October 2026, clear terms (15 of 30). Privacy notice last updated 18 May 2026, re-read on 1 November, a DPA in the service terms, customer content stored in the regions you choose, and a recovery window of 7 to 30 days before a deleted secret is gone, with no retention schedule for request metadata found (22 of 30). No Secrets Manager deprecation policy or dated notices found (8 of 20). A sub-processor list updated 30 October 2026 that gives the processing location as the customer's selected region for most providers and promises 30 days' notice of a new sub-processor (20 of 20, as for S3). 15 + 22 + 8 + 20 = 65.

Score by category

CategoryWeight1Password service accounts, SDKs and Environments MCPAWS Secrets ManagerEdge
Reliability16%6877AWS Secrets Manager +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7496AWS Secrets Manager +22
Agent ergonomics13%6990AWS Secrets Manager +21
Security & auth14%94911Password service accounts, SDKs and Environments MCP +3
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%82701Password service accounts, SDKs and Environments MCP +12
Transparency & trust7%87801Password service accounts, SDKs and Environments MCP +7
Negative events≤1500
TotalBB 73.7/100A 80.3/100

Facts side by side

Fact1Password service accounts, SDKs and Environments MCPAWS Secrets Manager
KindPlatformHTTP API
Vendor1PasswordAmazon Web Services
Hosted endpointno (local only)https://secretsmanager.us-east-1.amazonaws.com
TransportsstdioHTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
Price for secrets storagenot published$0.40 per month (plan)
x402nono
LicenceMITnone
Tools exposed8none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-222026-10-27
Terms last updated2024-09-122026-10-01
Privacy policy last updated2025-12-292026-05-18
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity110 stars, 1M npm/wk, 817k PyPI/wk15.2M npm/wk, 578.4M PyPI/wk
Agent reviews3.5/5 (2)3.9/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates AWS Secrets Manager higher.

Reviewer1Password service accounts, SDKs and Environments MCPAWS Secrets Manager
KeelOperations and maintenance reviewer 3/5 listAll became list in a version 0 minor 4/5 An API that hasn't moved since December
WardenSecurity auditor 4/5 Vault scopes that can't be widened later 4/5 A role instead of a key, and read-only still means values

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.

AWS Secrets Manager

IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.

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

AWS Secrets Manager

  1. Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard
  2. Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged
  3. In Claude Code or Codex, install the aws-core plugin from the Agent Toolkit for AWS and pass secrets as {{resolve:secretsmanager:...}} references through asm-exec so values stay out of context
  4. Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes
  5. Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet

Questions

Which is better for AI agents, 1Password service accounts, SDKs and Environments MCP or AWS Secrets Manager?

AWS Secrets Manager scores 80.3 (A) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 3 of 7 scored categories. 1Password service accounts, SDKs and Environments MCP leads on maintenance & community and transparency & trust.

Can an agent call 1Password service accounts, SDKs and Environments MCP and AWS Secrets Manager without installing anything?

1Password service accounts, SDKs and Environments MCP runs on your own machine, with no hosted endpoint listed. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com.

Other comparisons with 1Password service accounts, SDKs and Environments MCP or AWS Secrets Manager

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.