| name | pass-cli-mcp |
| description | Canonical protocol for model-side skill behavior when orchestrating proton-pass-community-mcp tools in chat sessions. |
| metadata | {"status":"draft"} |
Proton Pass MCP Skill Wrapper
Use this skill as a thin protocol layer around the proton-pass-community-mcp MCP server.
Purpose
- Enforce authentication-safe behavior for model-driven tool usage.
- Run a fast preflight before normal tool workflows.
- Keep secret material out of chat and tool arguments unless explicitly required by a user-approved tool.
Session Startup Protocol
Run this flow once when the skill is loaded for a new chat session:
- Call
check_status.
- If it succeeds, proceed with requested tools.
- If it returns
AUTH_REQUIRED or AUTH_EXPIRED:
- Tell the user to run
pass-cli login outside MCP.
- Tell the user to confirm when login is complete.
- Retry
check_status once user confirms.
- If it returns a CLI version compatibility error:
- Tell the user the detected version and pinned requirement.
- Ask the user to update/downgrade
pass-cli outside MCP before continuing.
Do not run check_status before every subsequent tool call in the same session.
Only run it again if an AUTH_* error occurs and the user says they re-authenticated.
Authentication Safety Rules
- Never ask the user to paste passwords, OTP codes, private keys, or session tokens into chat.
- Never attempt to discover credentials from local files, environment variables, browser state, or third-party services.
- Treat authentication as user-managed out-of-band.
- If auth errors persist after user confirmation, report failure and stop.
Tool Usage Guidance
- Prefer list/search tools first, then targeted view/read tools.
- Keep outputs minimal and deterministic when possible.
- For mutative operations, follow MCP write gates and explicit confirmation requirements.