1password logo

1password

Manage 1Password vaults and credentials through MCP with metadata-first reads and secret injection via local commands.

Install 1password

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "1password": {
      "command": "npx",
      "args": [
        "-y",
        "@takescake/1password-mcp"
      ],
      "env": {
        "OP_SERVICE_ACCOUNT_TOKEN": "YOUR_VALUE_HERE",
        "OP_KEYCHAIN_SERVICE": "YOUR_VALUE_HERE",
        "OP_KEYCHAIN_ACCOUNT": "YOUR_VALUE_HERE",
        "OP_MCP_ALLOWED_VAULTS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 15 tools correctly ().

Overview

1password is an MCP server for managing 1Password vaults and credentials through a 1Password Service Account. It provides tools for listing and searching items, creating and editing passwords and secure notes, rotating credentials, archiving or deleting items, and generating passwords. Secrets remain in 1Password by default, while op_run can inject op:// references into a local command without placing resolved values in the model context. Reach for it when an AI client needs controlled access to automation or CI credentials with vault allow-lists and non-secret metadata workflows.

Use cases

  • List automation vaults and inspect item metadata
  • Rotate staging or CI passwords
  • Inject 1Password secrets into local commands
  • Create secure notes and login items
  • Audit vault contents without revealing secrets

Key features

  • Service Account authentication
  • Vault allow-listing
  • Metadata-first secret reads
  • op:// reference validation and command injection
  • Password and passphrase generation
  • Item creation, editing, archiving, and deletion

Tools15

What 1password lets your agent do. Expand a tool for its parameters.

Verified live~3.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

17/17 checks healthy over the last 103d

What it can do

From the 15 tools this server returned when we ran it.

Runs commands · 1Can delete or modify data · 2Handles credentials · 9Makes network requests · 5Read-only tools · 12
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age285 days
Maintainers1

Observed 2026-11-16 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @takescake/1password-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars22Stargazers on the source repository.
npm downloads5.5kPackage downloads in the last 30 days.
Last commit17d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed15Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How 1password works

What 1password does

1password connects MCP clients to 1Password through a Service Account. It exposes vault discovery, item search, metadata-safe reads, item creation and editing, password rotation, archiving, permanent deletion, and password generation. Secure Notes and login or password items can be created with optional tags, notes, URLs, usernames, and custom fields.

The server is designed for credential workflows where plaintext should stay out of the model transcript. Reads return metadata by default: concealed fields, SSH private keys, one-time-password seeds, and card numbers remain hidden unless a tool is explicitly asked to reveal them. The server also supports checking an op:// reference without returning its value.

How it works

MCP clients start the server over stdio, typically through npx, and authenticate it with a 1Password Service Account token. The service account determines which vaults are available. An optional vault allow-list can further restrict discovery and operations to selected vaults.

For using credentials in scripts, op_run resolves op://vault/item/field references into the child process environment. The server does not log those resolved values and makes a best-effort attempt to redact them from standard output and error, including common JSON, URL, and base64 encodings. A command that intentionally transforms or transmits a secret can still expose it.

The server also supplies prompts for password generation, credential rotation, vault auditing, and secret-reference construction, plus browsable non-secret resources for configuration, vaults, and item metadata.

Setup and configuration

Use Node.js 20 or newer and create a 1Password Service Account with access limited to the vaults automation should use. Configure an MCP client to run npx -y @takescake/1password-mcp and provide OP_SERVICE_ACCOUNT_TOKEN in its environment.

On macOS, the token can instead be loaded from Keychain using OP_KEYCHAIN_SERVICE and, optionally, OP_KEYCHAIN_ACCOUNT. Token resolution gives precedence to command-line token options, then OP_SERVICE_ACCOUNT_TOKEN, then macOS Keychain. Command-line tokens are discouraged because local processes can inspect arguments.

OP_MCP_ALLOWED_VAULTS can restrict the server to an explicit set of vaults; the equivalent command-line option is --allowed-vaults. The package is community-built and is not an official 1Password product.

Tools and capabilities

  • Discover accessible vaults and list or title-search their items without returning secret values.
  • Retrieve item metadata and selected fields through item IDs or op:// references.
  • Create Secure Note and login or password items, then update titles, notes, tags, URLs, or fields.
  • Generate random passwords or memorable passphrases, including configurable character and suffix options.
  • Rotate concealed fields, archive items, or permanently delete them. Deletion cannot be undone.
  • Validate an op:// reference using non-secret metadata only.
  • Run local commands with referenced secrets available only to the child process. Command output is capped at 5 MiB per stream, and timeouts terminate the process tree.

Limitations and notes

Revealing a secret with item_get or password_read places that value in the model context and transcript. For commands, scripts, or API calls, op_run with an op:// reference is the preferred pattern. Notes are returned as-is, so sensitive content stored in notes should be handled accordingly.

Permanent deletion cannot be reversed. Archiving is the non-destructive alternative and hides the item from regular views. Service Account permissions and any configured vault allow-list limit what the tools can access.

The server uses the onepassword:// resource scheme. Older hard-coded 1password:// resource URIs should be replaced because URI schemes cannot begin with a digit.

Written by AllMCPs with AI assistance from the project’s README and listing data. How we build listings

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about 1password

1password is an MCP server that connects AI clients to 1Password Service Accounts and provides tools for vault discovery, item lookup, safe metadata reads, credential creation and editing, password generation, secret-reference validation, and command execution with op:// secrets injected into child-process environments.

Install it through an MCP client by configuring the command `npx -y @takescake/1password-mcp`. Set `OP_SERVICE_ACCOUNT_TOKEN` to a 1Password Service Account token, then restart the client and invoke the server.

Use op_run with op://vault/item/field references instead of revealing values with item_get or password_read. The referenced values are placed in the child process environment, while the server makes a best-effort attempt to redact them from command output.

Yes. Set `OP_MCP_ALLOWED_VAULTS` or use `--allowed-vaults` to limit accessible vaults. Vault listing and related operations are restricted to the configured allow-list.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG Preview1password AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/1password?style=directory)](https://allmcps.com/mcp/1password)
HTML Embed
<a href="https://allmcps.com/mcp/1password"><img src="https://allmcps.com/api/badge/1password?style=directory" alt="1password on AllMCPs" /></a>