Stats
Actions
Tags
From 1password
Check 1Password MCP, CLI, and desktop app readiness for Grok Build
How this command is triggered — by the user, by Claude, or both
Slash command
/1password:1password-statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
# 1Password Status Run a read-only health check of the 1Password integration. ## Steps 1. Run the status script: 2. If CLI is available, gather additional info (no secret values): 3. Check MCP binary resolution: 4. Report in this format: 5. If CLI is not signed in or MCP auth is needed, suggest `/1password-login`. 6. If MCP is not enabled at all, suggest `/1password-setup`. No destructive operations. Never print secret values.
Run a read-only health check of the 1Password integration.
Run the status script:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/status.sh
If CLI is available, gather additional info (no secret values):
op whoami 2>/dev/null || echo "Not signed in"
op vault list 2>/dev/null | head -10 || true
Check MCP binary resolution:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-mcp-path.sh 2>&1 || true
Report in this format:
## 1Password Status
| Check | Status |
|-------|--------|
| Desktop app | running / not detected |
| MCP binary | found at <path> / missing |
| CLI (op) | v<version> at <path> / missing |
| CLI auth | signed in as <account> / not signed in |
| Grok MCP | check /mcp for `1password` server |
### Next steps
<specific fixes for any failures>
If CLI is not signed in or MCP auth is needed, suggest /1password-login.
If MCP is not enabled at all, suggest /1password-setup.
No destructive operations. Never print secret values.
npx claudepluginhub awfixers-stuff/plugins --plugin 1password