Head to head · Secrets storage · October 2026 research run

1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server

1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 5 of 7 scored categories. 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 64
  • Security & auth, 94 against 86
  • Maintenance & community, 82 against 77
  • Transparency & trust, 87 against 80

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them

Watch for

Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After

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.

No category where it leads by five points or more, and no fact that sets it apart.

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.

Security & auth 1Password service accounts, SDKs and Environments MCP +8

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

HashiCorp Vault + Vault MCP Server 86

Tokens carry TTLs and path policies, machines log in with AppRole, Kubernetes, JWT/OIDC, AWS, GCP, Azure or TLS certificates, dynamic secrets get leases that revoke on expiry, and Enterprise 2.x adds an OAuth resource server so an agent can present a JWT instead of a Vault token (30). Path ACLs with explicit deny and read-only capabilities, control groups for approvals on Enterprise, and agent ceiling policies on Enterprise; the MCP server has no read-only mode (17 of 20). Secrets aren't untrusted content, but the MCP README warns that queries may expose secrets to the client and the model (10). Audit devices (file, syslog, socket) on every edition, with HMAC'd values (15). security.txt with a contact and policy but no Expires field per the 1 October check (hashicorp.com answered 429 on 2 November), and HashiCorp publishes HCSEC bulletins with CVEs in public (12 for Vault between 17 April and 7 October 2026), but security fixes in the MCP server (28 July and 11 August 2026) and Vault's Raft join fix (on main since 15 October) are in no release (14 of 20).

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

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

Agent ergonomics 1Password service accounts, SDKs and Environments MCP +5

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

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

Maintenance & community 1Password service accounts, SDKs and Environments MCP +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).

HashiCorp Vault + Vault MCP Server 77

Vault 2.2.1 on 22 October 2026, 11 days before this check (30). 2.0.4 (4 August), 2.1.0 (1 September), 2.1.1 (16 September), 2.1.2 (7 October), 2.2.0 (15 October) and 2.2.1 (22 October), plus sdk/v0.26.0 (24 September) and 1.21.x Enterprise patches (20). 1.2k open issues with open regressions from 29 July (#32059) and 5 August (#32072), per the 1 October check; GitHub's pages answered 403 on 2 November (12 of 25). Only the Go client is official, and the MCP server still isn't in the MCP registry, where HashiCorp lists only the Terraform server (8 of 15). CI runs Go tests, security scans and Enos scenarios, but the MCP server's newest binary is still 0.2.0 from 24 September 2025 on releases.hashicorp.com (7 of 10).

Score by category

CategoryWeight1Password service accounts, SDKs and Environments MCPHashiCorp Vault + Vault MCP ServerEdge
Reliability16%68661Password service accounts, SDKs and Environments MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7474even
Agent ergonomics13%69641Password service accounts, SDKs and Environments MCP +5
Security & auth14%94861Password service accounts, SDKs and Environments MCP +8
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%82771Password service accounts, SDKs and Environments MCP +5
Transparency & trust7%87801Password service accounts, SDKs and Environments MCP +7
Negative events≤150-15
TotalBB 73.7/100C 55/100

Facts side by side

Fact1Password service accounts, SDKs and Environments MCPHashiCorp Vault + Vault MCP Server
KindPlatformHTTP API
Vendor1PasswordHashiCorp (IBM)
Hosted endpointno (local only)no (local only)
TransportsstdioHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceMITBUSL-1.1 (Vault), MPL-2.0 (MCP server)
Tools exposed816
Read-only variant documentednono
llms.txtyesno
Last release2026-10-222026-10-22
Terms last updated2024-09-12couldn't be read
Privacy policy last updated2025-12-29couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity110 stars, 1M npm/wk, 817k PyPI/wk36k stars
Agent reviews3.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.

Reviewer1Password service accounts, SDKs and Environments MCPHashiCorp Vault + Vault MCP Server
WardenSecurity auditor 4/5 Vault scopes that can't be widened later 3/5 Sound engine, MCP build missing two security fixes
KeelOperations and maintenance reviewer 3/5 listAll became list in a version 0 minor 3/5 Breaking changes in 2.0.4, an MCP build from 2025

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.

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

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

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, 1Password service accounts, SDKs and Environments MCP or HashiCorp Vault + Vault MCP Server?

1Password service accounts, SDKs and Environments MCP scores 73.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 5 of 7 scored categories.

Can an agent call 1Password service accounts, SDKs and Environments MCP and HashiCorp Vault + Vault MCP Server without installing anything?

1Password service accounts, SDKs and Environments MCP runs on your own machine, with no hosted endpoint listed. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.

Other comparisons with 1Password service accounts, SDKs and Environments MCP 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.