proton-pass-community-mcp
Related Servers
Alternatives to proton-pass-community-mcp
No user-submitted related servers found.
Related Servers
- 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.-
- 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.19 npm1MIT
- AlicenseAqualityDmaintenanceEnables interaction with Obsidian vaults through the official Obsidian CLI, allowing note management, search, and vault operations without plugins or API keys.21MIT
- AlicenseAqualityDmaintenanceEnables secure secrets management through the Doppler CLI via natural language interactions. Supports managing secrets, projects, configs, and environments across different Doppler workspaces.11MIT
- AlicenseBqualityDmaintenanceEnables natural language management of Doppler secrets, projects, configs, and environments by wrapping the Doppler CLI for use with MCP clients like Claude Desktop.11MIT
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.