Releases: CakeRepository/1Password-MCP
Releases · CakeRepository/1Password-MCP
Release list
v4.0.1
Summary
Documentation and package-metadata release for @takescake/1password-mcp.
- Refreshed README, CONTRIBUTING, and AGENTS for the full v4 surface (15 tools, prompts, resources)
- Clearer
op_run/ reveal guidance and MCP 2026-07-28 / Node ≥ 20 requirements - Improved npm and
server.jsondescriptions, keywords, and env-var docs
Install
npx -y @takescake/1password-mcpOr pin: @takescake/1password-mcp@4.0.1
v4.0.0
What's Changed
- fix(release): publish v3.0.0 directly by @CakeRepository in #15
- ci: enable npm trusted publishing by @CakeRepository in #16
- ci: clean up npm release workflows by @CakeRepository in #17
- chore: run one-time MCP v2 migration by @CakeRepository in #18
- chore: retry MCP v2 migration runner by @CakeRepository in #19
- feat: support MCP protocol 2026-07-28 by @CakeRepository in #20
Full Changelog: v3.0.0...v4.0.0
Contributors
CakeRepository
Assets 2
v3.0.0
Major security-focused release. password_read is now metadata-only unless reveal: true is explicitly supplied. Adds op_run and op_check_ref so agents can use and validate 1Password references without exposing plaintext secrets.
v2.5.0
Added
- item_get tool — Retrieve detailed information for a 1Password item, including tags, fields, website URLs, and notes. Concealed field values are hidden unless explicitly revealed. Supports secret references (op://vault/item/field) or vault and item IDs.
- item_edit tool — Edit an existing 1Password item, updating titles, notes, tags, website URL, and upserting or removing fields.
- item_list tool — List all items in a 1Password vault (returns metadata like ID, title, category, tags, and updatedAt).
- item_archive tool — Move a 1Password item to the archive instead of permanently deleting it.
- note_create tool — Create a Secure Note item with optional custom fields and tags.
Fixed
- Tool Schema Documentation Alignment — Updated parameter and tool descriptions for item_get and note_create to ensure the correct formats (e.g. op://vault/item/field for secret reference) and parameter descriptions (id or title for custom fields) are properly surfaced in MCP.