@rui.branco/1password-mcp 0.1.1 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +27 -16
- package/index.js +791 -620
- package/package.json +2 -2
- package/setup.js +93 -8
package/README.md
CHANGED
|
@@ -16,33 +16,44 @@ Built to mirror the multi-instance pattern of [jira-mcp](https://github.com/rui-
|
|
|
16
16
|
### Prerequisites
|
|
17
17
|
|
|
18
18
|
- Node.js 18+
|
|
19
|
-
-
|
|
19
|
+
- Either:
|
|
20
|
+
- **The 1Password 8 desktop app** (recommended — no admin permissions needed, and you get access to all vaults you can already see), or
|
|
21
|
+
- A 1Password **service account** token (needs admin to provision, scoped to shared vaults only — good for CI/headless use)
|
|
20
22
|
|
|
21
|
-
### Step 1:
|
|
22
|
-
|
|
23
|
-
1. Go to <https://start.1password.com/developer-tools/infrastructure-secrets/serviceaccount>
|
|
24
|
-
2. Create a service account and grant it access to the vaults you want to use
|
|
25
|
-
3. Copy the token — it starts with `ops_`
|
|
26
|
-
|
|
27
|
-
### Step 2: Configure
|
|
23
|
+
### Step 1: Install and register the MCP
|
|
28
24
|
|
|
29
25
|
```bash
|
|
30
|
-
|
|
26
|
+
claude mcp add --scope user --transport stdio 1password -- npx -y @rui.branco/1password-mcp
|
|
31
27
|
```
|
|
32
28
|
|
|
33
|
-
|
|
29
|
+
### Step 2: Run setup
|
|
34
30
|
|
|
35
31
|
```bash
|
|
36
|
-
|
|
32
|
+
npx @rui.branco/1password-mcp setup
|
|
37
33
|
```
|
|
38
34
|
|
|
39
|
-
|
|
35
|
+
The setup wizard walks you through picking an auth mode and validates the connection before saving.
|
|
40
36
|
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
37
|
+
### Step 3 (desktop auth only): One-time 1Password 8 toggles
|
|
38
|
+
|
|
39
|
+
Desktop auth delegates unlock to the 1Password 8 desktop app, so you need to enable the SDK integration **once** per machine:
|
|
40
|
+
|
|
41
|
+
1. Open the **1Password 8 desktop app** (not `my.1password.com` in the browser).
|
|
42
|
+
2. Open **Settings** (cmd+, on Mac / ctrl+, on Windows).
|
|
43
|
+
3. Click the **Developer** tab.
|
|
44
|
+
4. Under *Command-Line Interface (CLI)*, tick **"Integrate with 1Password CLI"**.
|
|
45
|
+
5. Under *Integrate with the 1Password SDKs*, tick **"Integrate with other apps"**. ← **This is the critical one.** Without it, the SDK cannot unlock and every call will fail with `DesktopSessionExpiredError`.
|
|
46
|
+
6. Optional: **Settings → Security → Unlock using Touch ID** so the OS prompt can be cleared with your fingerprint.
|
|
47
|
+
|
|
48
|
+
The first time the MCP actually calls 1Password, your OS will pop an authorization prompt asking whether `1password-mcp-setup` (during the wizard) and `1password-mcp` (at runtime) can talk to 1Password. Click Approve.
|
|
49
|
+
|
|
50
|
+
### Finding your account name
|
|
51
|
+
|
|
52
|
+
When the wizard asks for "Account name", open the 1Password 8 desktop app and click the **account switcher** in the top-left. The signin address shown next to your name is what you want — it looks like `my.1password.com`, `my-team.1password.com`, or similar.
|
|
53
|
+
|
|
54
|
+
### Step 4: Reconnect
|
|
44
55
|
|
|
45
|
-
|
|
56
|
+
Run `/mcp` in Claude Code to reconnect the 1password server and pick up the new config.
|
|
46
57
|
|
|
47
58
|
## Tools
|
|
48
59
|
|