proton-pass-community-mcp
Provides tools for interacting with Proton Pass, including managing vaults, items (logins, notes, credit cards, etc.), sharing, member management, password generation, and more via the pass-cli.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@proton-pass-community-mcp list my vaults"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
proton-pass-community-mcp is an MCP server for Proton Pass, with broad coverage of pass-cli operations.
It is an independent community project. It is not affiliated with or endorsed by Proton AG.
The integration provides:
typed tool inputs with
zodstdio transport for MCP clients
CLI compatibility baseline: 2.3.3
The current rehabilitation targets the existing 47 tools against the published CLI 2.3.3 source. Validation covers schemas, subprocess behavior, fixtures, and the installed npm package; live vault compatibility has not been revalidated. See the compatibility audit for per-tool evidence and limits.
Available Tools
The server exposes the following MCP tool surface:
Tool | Purpose |
| Session/account status from |
| User account details from |
| Check user authentication status and CLI version |
| Inject secrets into template files |
| Run commands with secret references resolved |
| List vaults |
| List shares |
| List pending invitations |
| Accept an invitation token |
| Reject an invitation token |
| View current Proton Pass CLI settings |
| List members of a specific vault |
| Update a vault member role |
| Remove a vault member |
| List vault or share items, omitting contents |
| Search items by title |
| View item by URI or selectors |
| Create a vault |
| Update a vault name |
| Delete a vault |
| Share a vault with a user |
| Transfer vault ownership |
| Create a login item |
| Create a login item from template payload |
| Create a note item |
| Create a credit card item |
| Create a WiFi item |
| Create a custom item from template payload |
| Create an identity item from template payload |
| Move an item between vaults |
| Move an item to trash |
| Restore an item from trash |
| Update an item field set |
| Delete an item |
| Download an item attachment |
| List members of an item |
| Update an item member role |
| Remove an item member |
| Create an alias item |
| Share an item with a user |
| Generate item TOTP codes |
| Generate a random password |
| Generate a passphrase |
| Generate TOTP from secret/URI |
| Score password strength |
Coverage goal: provide comprehensive support for Proton Pass CLI workflows that fit MCP tool semantics. Intentionally excluded are CLI behaviors that are purely interactive or otherwise not a good fit for reliable MCP tool execution.
The search_items operation is additional functionality that is not provided by the base CLI.
Mutative tools require write gate opt-in (ALLOW_WRITE=1) and explicit per-call confirmation (confirm: true). This includes download_item_attachment, which can overwrite a local file, and inject/run. delete_item permanently deletes an item without requiring it to be trashed first.
Changed input requirements: update_item, trash_item, untrash_item, and update_vault require an explicit agentReason for every session type. CLI 2.3.3 can apply these mutations before validating an agent audit reason, so the server validates the reason before invoking the CLI. Other audited tools accept an optional agentReason; see audit-reason policy.
Proposed protocol-aligned confirmation policy (elicitation-first with fail-closed fallback) is documented in docs/TOOL_SCHEMA_PLAN.md.
Related MCP server: protonpass-mcp
Available Resources
The server also exposes static MCP resources for item-create template snapshots:
pass://templates/item-create(catalog/index)pass://templates/item-create/loginpass://templates/item-create/notepass://templates/item-create/credit-cardpass://templates/item-create/wifipass://templates/item-create/custompass://templates/item-create/identity
Snapshot artifact source:
These resources reflect the six existing CLI template types, refreshed from the 2.3.3 source without executing the CLI. They are examples, not authoritative validation schemas or necessarily create-ready values (WiFi still needs a nonblank SSID). Login templates now include totp_uri.
Item Discovery Contract
list_items and search_items project CLI JSON into item references, omitting nested item contents and secrets. Unknown JSON envelopes and invalid JSON fail without returning the raw payload. The legacy list_items.output: "human" hint also returns JSON references and cannot bypass this projection; it does not accept pagination parameters. Explicit view_item field reads preserve the field's text rather than parsing JSON-looking secrets.
list_items and search_items both support MCP pagination:
Input fields:
pageSize(optional,1..250, default100for JSON output)cursor(optional non-negative integer string offset, for example"100")
Behavior:
Response includes
items,pageSize,cursor,returned,total, andnextCursor.Use
nextCursorin a follow-up call to fetch the next page.
list_items also forwards filterType, filterState, and sortBy to pass-cli item list.
search_items semantics:
title-only search (
field: "title")matching modes:
contains,prefix,exactoptional
caseSensitivean omitted vault/share selector searches the CLI's default vault, not all vaults
Requirements
Currently, the server expects the user to handle authentication. If it's not able to authenticate, it will simply prompt the user to authenticate using one of thepass-cli methods.
Node.js
24(.nvmrc)pass-cliinstalled and authenticatedMCP client capable of stdio transport
For project development and testing, use the repo wrapper (
npm run pass -- <args>orscripts/pass-dev.sh <args>) instead of barepass-cliso auth stays in the repo-local session scope.
Run Locally
npm ci
npm run build
npm run devFor project-side pass-cli work, prefer:
npm run pass -- infoThis routes through the repo wrapper, which uses a project-local session dir and avoids OS keychain/keyring by default. To assert that the active repo-local session is the intended throwaway account before mutative work:
export PASS_DEV_EXPECTED_ACCOUNT=<throwaway-account-identifier>
npm run pass:dev:preflightInstall and Run via npm/npx
Install from npm or run directly with npx:
npm install --global proton-pass-community-mcp
proton-pass-community-mcp --allow-version-driftor:
npx -y proton-pass-community-mcp --allow-version-driftRelease operations for maintainers are documented in docs/DEPLOYMENT.md.
Anonymized Demo Shell (Docker)
Use this when recording demos and you want a neutral workspace path in tooling metadata:
npm run demo:shellThis launches a container with the project mounted at /workspace/project.
To run a single command instead of an interactive shell:
npm run demo:shell -- npm run checkNotes:
Shell prompt aliases/PS1 tweaks only change terminal display; they do not change real working-directory metadata emitted by tools.
For true path anonymization in logs, run the host/tooling process from inside this containerized workspace.
MCP Client Configuration
Example MCP server config using npx package execution:
{
"mcpServers": {
"proton-pass-community-mcp": {
"command": "npx",
"args": ["-y", "proton-pass-community-mcp", "--allow-version-drift"]
}
}
}If you are developing locally from source, use a direct local build path:
Example MCP server config using command-line args:
{
"mcpServers": {
"proton-pass-community-mcp": {
"command": "node",
"args": ["/absolute/path/to/proton-pass-community-mcp/dist/index.js", "--allow-version-drift"]
}
}
}Example MCP server config using environment overrides:
{
"mcpServers": {
"proton-pass": {
"command": "node",
"args": ["/absolute/path/to/proton-pass-community-mcp/dist/index.js"],
"env": {
"PASS_CLI_BIN": "pass-cli",
"PASS_CLI_ALLOW_VERSION_DRIFT": "true"
}
}
}
}Authentication Model
Authentication is user-managed outside MCP with
pass-cli login.The
pass-clisession may be established with normal account credentials or with a pre-provisioned personal access token (PAT).On auth failure, tools return standardized
AUTH_*errors and a retry instruction.The MCP server does not collect credentials, OTP codes, private keys, or PAT values.
PAT-backed login does not change the boundary: login/logout remain outside MCP, and PAT provisioning is not currently exposed as an MCP tool surface.
For project development, the canonical
pass-clientrypoint is the repo wrapper (npm run pass -- <args>/scripts/pass-dev.sh <args>), not barepass-cli.The repo wrapper isolates project auth into
.tmp/proton-pass-dev-sessionand avoids default keychain/keyring access, but it does not by itself prove the correct account is active; usescripts/pass-dev-preflight.shornpm run pass:dev:preflightto assert the expected throwaway account.Use
check_statusonce as a session preflight (not per tool call); rely onAUTH_*fallback errors if the session later expires.check_statuscompares your local CLI version against the development baseline and reports a version assessment for LLMs:equal: exact semver matchcompatible: semver differs but appears compatible by policypossibly_incompatible: semver indicates potential drift, or version parsing/execution prevented a strict comparison
Version assessments are advisory.
check_statusis marked as an MCP error only when connectivity/authentication fails.There is no MCP-specific API token auth layer in this server. Authentication methods are those supported by
pass-cliin the server process environment.Agent provisioning and agent-token login also remain outside MCP.
agentReasonis an audit explanation, not a credential or authorization grant. It is forwarded only to that invocation asPROTON_PASS_AGENT_REASON; the server does not invent reasons or mutate its process environment. Non-agent sessions can omit it except on the four mutation tools listed above. Permission/capability denials remain errors rather than instructions to reauthenticate.A valid reason does not make mutation and audit delivery atomic. Never automatically retry a failed mutation: inspect its state first.
check_statususesinfoplus--version; it is a session preflight, not proof that every capability or remote API call will succeed.
Test Account Workflow
For disposable test-account usage in local development and CI (including account preflight checks and session isolation), see docs/testing/TEST_ACCOUNT_WORKFLOW.md.
Startup Flags
--allow-version-drift: treat semver mismatch/version-parse uncertainty as compatible forcheck_status
Equivalent environment variable:
PASS_CLI_ALLOW_VERSION_DRIFT=true|false(accepted truthy values:true,1,yes,on; falsy:false,0,no,off)If both are set, the CLI flag takes precedence.
Example:
npm run dev -- --allow-version-driftNotes
This is not an official Proton project.
This project currently targets Proton Pass via
pass-clionly.See ROADMAP.md for planned features.
In addition to the MCP server, there is an agent skill file that is intended to be integrated with this MCP - however, it is currently only a draft.
Developer runtime configuration and validation workflows are documented in CONTRIBUTING.md.
Disposable account setup and contributor/CI guidance are documented in docs/testing/TEST_ACCOUNT_WORKFLOW.md.
See CONTRIBUTING.md if you're interested in contributing to this project. Contributors are welcome.
LICENSE
GPL-3 © 2026 Really Him
Available Tools
47 toolsaccept_inviteC
Accept an invitation token.
Inputs: inviteToken (required), confirm.
check_statusA
Run preflight checks for connectivity/authentication and CLI version compatibility.
Inputs: no named parameters.
create_credit_card_itemB
Create a credit card item in a vault or share.
Inputs: title (required), cvv, pin, note, +7 more.
create_custom_itemB
Create a custom item from template payload in a vault or share.
Inputs: template (required), confirm, shareId, vaultName, +1 more.
create_identity_itemC
Create an identity item from template payload in a vault or share.
Inputs: template (required), confirm, shareId, vaultName, +1 more.
create_item_aliasB
Create an email alias item.
Inputs: prefix (required), output, confirm, shareId, +1 more.
create_login_itemC
Create a login item in a vault or share.
Inputs: title (required), url, email, confirm, +6 more.
create_login_item_from_templateB
Create a login item from template JSON.
Inputs: template (required), confirm, shareId, vaultName, +1 more.
create_note_itemB
Create a note item in a vault or share.
Inputs: title (required), note, confirm, shareId, +2 more.
create_vaultC
Create a new vault.
Inputs: name (required), confirm.
create_wifi_itemA
Create a WiFi item in a vault or share.
Inputs: ssid (required), title (required), note, confirm, +5 more.
delete_itemA
Permanently delete an item by share ID and item ID, bypassing trash.
Inputs: itemId (required), shareId (required), confirm, agentReason.
delete_vaultC
Delete a vault by share ID or vault name.
Inputs: confirm, shareId, vaultName.
download_item_attachmentA
Download an item attachment to a local path, potentially overwriting it. Requires write permission and confirmation.
Inputs: itemId (required), shareId (required), outputPath (required), attachmentId (required), +1 more.
generate_item_totpB
Generate TOTP code(s) for an item by URI or selectors, optionally targeting a specific field.
Inputs: uri, field, itemId, output, +4 more.
generate_passphraseC
Generate a passphrase.
Inputs: count, numbers, separator, capitalize.
generate_random_passwordC
Generate a random password.
Inputs: length, numbers, symbols, uppercase.
generate_totpA
Generate a TOTP token from a secret or otpauth URI.
Inputs: secretOrUri (required), output.
injectC
Inject secrets from Proton Pass references into a template file.
Inputs: inFile (required), force, confirm, outFile, +2 more.
list_invitesA
List pending invitations accessible to the current authenticated user.
Inputs: cursor, pageSize.
list_item_membersC
List item members.
Inputs: itemId (required), shareId (required), output.
list_itemsB
List items for a vault or share with MCP pagination support for JSON output.
Inputs: cursor, output, sortBy, shareId, +4 more.
list_vault_membersA
List members for a vault by share ID or vault name.
Inputs: cursor, shareId, pageSize, vaultName.
list_vaultsA
List vaults accessible to the current authenticated user.
Inputs: output.
move_itemC
Move an item from one vault to another.
Inputs: itemId, confirm, itemTitle, toShareId, +4 more.
reject_inviteB
Reject an invitation token.
Inputs: inviteToken (required), confirm.
remove_item_memberC
Remove an item member.
Inputs: shareId (required), memberShareId (required), confirm.
remove_vault_memberC
Remove a member from a vault.
Inputs: memberShareId (required), confirm, shareId, vaultName.
runC
Run a command with Proton Pass secret references resolved in environment.
Inputs: command (required), confirm, envFiles, noMasking, +1 more.
score_passwordC
Score password strength.
Inputs: password (required), output.
search_itemsA
Search items by title with MCP pagination support for JSON output.
Inputs: query (required), field, match, cursor, +7 more.
set_default_vaultC
Set default vault by share ID or vault name.
Inputs: confirm, shareId, vaultName.
transfer_vaultB
Transfer vault ownership to a member.
Inputs: memberShareId (required), confirm, shareId, vaultName.
trash_itemC
Move an item to trash by selectors.
Inputs: agentReason (required), itemId, confirm, shareId, +2 more.
unset_default_vaultC
Unset default vault setting.
Inputs: confirm.
untrash_itemB
Restore an item from trash by selectors.
Inputs: agentReason (required), itemId, confirm, shareId, +2 more.
update_itemC
Update an item using selectors and field assignments.
Inputs: fields (required), agentReason (required), itemId, confirm, +3 more.
update_item_memberB
Update an item member role.
Inputs: role (required), shareId (required), memberShareId (required), confirm.
update_vaultC
Update a vault by share ID or vault name.
Inputs: newName (required), agentReason (required), confirm, shareId, +1 more.
update_vault_memberC
Update a vault member role.
Inputs: role (required), memberShareId (required), confirm, shareId, +1 more.
view_itemA
View a specific item by URI or selectors, optionally returning a specific field.
Inputs: uri, field, itemId, output, +4 more.
view_session_infoA
View current Proton Pass session/account summary from pass-cli info.
Inputs: no named parameters.
view_settingsA
View current Proton Pass CLI settings.
Inputs: no named parameters.
view_user_infoA
View Proton user profile/account details from pass-cli user info.
Inputs: output.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 47 tools
Most tools map to distinct resource-action pairs: vaults, items, members, invites, attachments, and utilities are clearly separated. A few boundary cases like create_login_item_from_template versus create_custom_item or list_shares versus list_vaults could cause minor confusion, but the descriptions generally resolve it.
The dominant verb_noun snake_case pattern is consistent across the set: list_vaults, create_vault, trash_item, untrash_item, share_vault, and so on. The main deviations are generic single-verb tools like inject and run, plus verbose template-based creation variants, but the overall pattern remains predictable.
47 tools is a very large MCP surface, beyond what is typically comfortable for agent tool selection. Many tools are narrowly scoped variants, such as eight item-creation tools and separate member-management clusters, which could potentially be consolidated without losing clarity.
The tool set covers the full password-manager workflow well: vault lifecycle, item lifecycle with trash/restore/permanent delete, sharing and invitations, member management, TOTP, password generation, and session/settings checks. Minor gaps like uploading or updating attachments keep it from being a 5, but agents can complete common workflows without dead ends.
Maintenance
Related MCP Connectors
Manage PocketBase Cloud projects, instances, deploys, domains, collections and records.
Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.
Password vault for AI agents with scoped, user-approved access
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables secure secrets management through the Doppler CLI via natural language interactions. Supports managing secrets, projects, configs, and environments across different Doppler workspaces.11MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Proton Pass. It wraps the official pass-cli binary and exposes 14 tools so any MCP-compatible AI assistant (Claude Desktop, Claude Code, etc.) can manage your vaults, credentials, and secrets.14-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with 1Password vaults and items via the op CLI, supporting vault listing, item lookup, password read/create/update/generate, and delete operations. Zero idle CPU usage and supports service account tokens for headless use.15 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables to manage 1Password resources including vaults, items, documents, users, groups, and more through the 1Password CLI, exposing 65 tools for comprehensive password management via natural language.-