Or install with one command
claude mcp add --scope user nopeeking -- npx -y nopeeking
Three steps. Zero peeking.
-
Save it once
A popup opens on your PC, or Claude sends a one-time link to your phone. You type the password there, never in the chat.
-
Ask Claude to log in
“Log me in to Netflix.” Claude opens the page in Chrome and clicks into the password box.
-
NoPeeking types it
The password goes from Windows straight into the box, and only on the site it was saved for. Claude is never handed it.
API keys too
Run commands with a key Claude can’t read.
Claude asks to run a command with your saved key. NoPeeking puts the key in for that one command, as an environment variable, and masks it in anything the command prints.
Claude ›
run_with_secret OPENAI_API_KEY ← openai
curl … -H "Authorization: Bearer $env:OPENAI_API_KEY"
output ›
token used: ••••(openai)
What you need
- Windows 10 or 11
- Node.js 20 or newer
- Claude Code
- For website logins: Chrome with Claude in Chrome
No account, no password manager, nothing to pay. Works from your phone with Claude Code Remote Control.
What it can’t stop
- Claude Code can run commands as you. A Claude that has been tricked could read Credential Manager directly. The optional guard blocks the obvious ways; it’s a speed bump, not a wall.
- Once typed, a password sits in the page’s password box, where the page’s scripts and Claude’s own browser tools can read it.
- Masking catches the whole key, its common encodings and long pieces of it, but not every way a command could reshape it. Read commands before you approve them.