protonpass-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PASS_LOG_LEVEL | No | Log verbosity: trace, debug, info, warn, error, off. | info |
| PROTON_PASS_SESSION_DIR | No | Override session storage path. | |
| PROTON_PASS_KEY_PROVIDER | No | Key storage backend. Use 'fs' in Docker (no system keyring). | keyring |
| PROTON_PASS_ENCRYPTION_KEY | No | Encryption key when KEY_PROVIDER=env. SHA-256 hashed internally. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vaultsA | List all Proton Pass vaults accessible to the current account. |
| create_vaultB | Create a new Proton Pass vault. |
| list_itemsA | List items stored in a vault. Omit vault_id to list items across all vaults. |
| view_itemB | View the full details of an item (title, username, password, URLs, notes, custom fields, etc.). |
| create_loginB | Create a new login credential item in a vault. |
| create_noteA | Create a new secure note item in a vault. |
| update_itemA | Update an existing item. Only the fields you supply will change. |
| trash_itemA | Move an item to trash (soft delete). Use restore_item to undo. |
| restore_itemB | Restore a trashed item. |
| get_totpA | Get the current TOTP one-time code for an item that has 2FA configured. |
| generate_passwordB | Generate a cryptographically secure random password. |
| view_secretA | Retrieve a specific field value from an item using a pass:// URI. URI format: pass://// Fields: username, password, email, url, note, totp, or custom field name. Example: pass://Work/GitHub/password |
| get_user_infoA | Get information about the currently authenticated Proton account. |
| share_vaultB | Share a vault with another Proton user by email. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a specific resource and action, with only minor overlap between get_totp and view_secret (which can retrieve the totp field via URI). For example, list_items vs view_item are clearly distinct in scope (metadata vs full details).
All tools follow a consistent verb_noun snake_case pattern (e.g., list_vaults, create_note, trash_item, generate_password). There is no mixing of camelCase, vague verbs, or irregular naming conventions.
14 tools is well-scoped for a password manager, covering vaults, items, lifecycle, sharing, TOTP, and password generation. Each tool has a distinct place and the set feels intentional rather than bloated.
The tool surface covers core CRUD/lifecycle for vaults and items, plus sharing, TOTP retrieval, and password generation. Minor gaps exist, such as no permanent delete (only trash/restore) and limited item creation types (only login and note), but these are workable.