# 1password [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/CakeRepository/1Password-MCP.git  
**GitHub Stars:** 22  
**npm Downloads (last month):** 5478  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/1password

## Description
MCP server for 1Password service accounts

## Tools
Capabilities this server exposes over MCP:

- **vault_list** — List the 1Password vaults accessible to the service account (limited to the allow-listed vaults when OP_MCP_ALLOWED_VAULTS / --allowed-vaults is configured). Returns vault IDs, names, descriptions, and types.
- **item_lookup** — Search for items within a 1Password vault by title substring. Returns item IDs, titles, categories, and vault IDs.
- **item_delete** — Permanently delete an item from a 1Password vault. This action cannot be undone.
- **item_get** — Retrieve a full 1Password item — title, category, tags, notes, and all fields (id, title, type, section). Secret-bearing field values (passwords and other concealed fields, SSH private keys, one-time-password seeds, card numbers) are hidden unless reveal is true; only known non-secret types (text, URL, email, phone, date, menu, card type, address, reference) are shown by default. Accepts a secret reference (op://vault/item/field) or vault ID + item ID. Revealing a secret puts it in the model context/transcript — to USE a secret in a command or API call, prefer op_run with op:// references instead.
- **item_edit** — Edit an existing 1Password item. Update the title, notes (pass an empty string to clear notes), tags, website URL, upsert fields, or remove fields. Only referenced fields are changed; all others are preserved.
- **item_list** — List all items in a 1Password vault, returning id, title, category, tags, and updatedAt for each. Never returns secret values.
- **item_archive** — Archive an item in a 1Password vault. The item is moved to the archive and hidden from regular views, rather than being permanently deleted.
- **note_create** — Create a Secure Note item in a 1Password vault, with optional tags and custom fields.
- **password_create** — Create a new password/login item in a 1Password vault with optional username, URL, tags, and notes.
- **password_read** — Retrieve a secret from 1Password using either a secret reference (op://vault/item/field) or vault ID + item ID. Supports field selection and optional value reveal (defaults to metadata-only). Revealing a secret puts it in the model context/transcript — to USE a secret in a command or API call, prefer op_run with op:// references instead.
- **password_update** — Update (rotate) a password or concealed field on an existing 1Password item. If the target field does not exist, it will be created.
- **password_generate** — Generate a cryptographically secure random password with configurable length and character types. Uses rejection sampling for unbiased randomness.
- **password_generate_memorable** — Generate a memorable passphrase from random dictionary words with optional number and symbol suffixes. Uses a ~500-word curated list for good entropy.
- **op_run** — Run a local shell command with 1Password secrets injected as environment variables. Resolved values go only into the child process environment, are never logged by the server, and are redacted from stdout/stderr on a best-effort basis (including common encodings such as JSON, URL and base64) — a command that deliberately transforms or transmits a secret can still expose it. This is the preferred way to USE a secret in a command, API call, or script: prefer op_run with op://vault/item/field references in `env` over reading a secret with password_read/item_get and pasting it into a command yourself, which would put the plaintext in the model context and transcript.
- **op_check_ref** — Validate an op://vault/item/field secret reference and return only non-secret metadata (vault name, item title, field label, field type) confirming it resolves — the field VALUE is never returned. Use this to check a reference is correct before using it with op_run; do not use password_read/item_get with reveal just to check a reference exists.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "1password": {
    "command": "npx",
    "args": ["-y","@takescake/1password-mcp"],
    "env": {
      "OP_SERVICE_ACCOUNT_TOKEN": "",
      "OP_KEYCHAIN_SERVICE": "",
      "OP_KEYCHAIN_ACCOUNT": "",
      "OP_MCP_ALLOWED_VAULTS": ""
    }
  }
}
```

**Requires environment variables:** `OP_SERVICE_ACCOUNT_TOKEN`, `OP_KEYCHAIN_SERVICE`, `OP_KEYCHAIN_ACCOUNT`, `OP_MCP_ALLOWED_VAULTS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

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

_Full upstream README: https://allmcps.com/mcp/1password/readme_

