R
r69shabh/secureinput
Your agent needs the token.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · r69shabh/secureinput · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
r69shabh/secureinput;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# SecureInput
Excerpted from the repository README (abridged)
Your agent needs the token. It doesn't need to see it.
SecureInput is an open-source, local-first MCP server for API keys, passwords, and tokens. When your coding agent needs a credential, you type it into a small input that appears inside the chat, styled like the host's own composer. The value goes straight to a local command (stdin or env) or a .env file. The agent only gets back { "ok": true, "status": "completed", "exitCode": 0 }.
Works with Claude Code, Claude Desktop, Cursor, Codex, VS Code / GitHub Copilot, Windsurf, Cline, and any stdio MCP client. macOS and Linux, Node.js 22+.
Install · How it works · Security model · FAQ · Watch the 20-second overview
## Install
Pick your client. Every option runs npx -y secureinput mcp (Node.js 22+), which starts the shared local daemon on first use. Try it with a fake key first.
### 1. Connect your agent
Claude Code
bash
claude mcp add --scope user secureinput -- npx -y secureinput mcp
claude mcp list # secureinput: ✔ Connected
Claude Desktop : one-file bundle, no terminal
1. Download the latest secureinput-release-.mcpb from GitHub Releases. The bundle is unsigned; review the release before installing.
2. Open Settings → Desktop app → Manage next to Extensions (older versions: Settings → Extensions), then Advanced settings → Install Extension… and pick the file. See Claude's guide.
3. Ask Claude to save a fake key with SecureInput.
To upgrade, install the newer .mcpb.
Cursor : use the button above, or ~/.cursor/mcp.json
json
{ "mcpServers": { "secureinput": { "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
VS Code / GitHub Copilot : use the button above, or .vscode/mcp.json
json
{ "servers": { "secureinput": { "type": "stdio", "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
Codex CLI
bash
codex mcp add secureinput -- npx -y secureinput mcp
Or in ~/.codex/config.toml:
toml
[mcp_servers.secureinput]
command = "npx"
args = ["-y", "secureinput", "mcp"]
Windsurf, Cline, or any stdio client
json
{ "mcpServers": { "secureinput": { "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
Global install or from source
bash
npm install -g secureinput # then use command "secureinput", args ["mcp"]
secureinput doctor # checks Node, config and the daemon
From source: git clone https://github.com/r69shabh/secureinput.git && cd secureinput && npm ci && npm run build && npm link.
GUI apps may not see a Node version manager's PATH (fnm, nvm, volta). If npx isn't found, use the full path from realpath "$(which npx)" as the command.
### 2. Tell your agent to use it
Add this to your agent rules (CLAUDE.md, AGENTS.md, .cursor/rules, …) so it reaches for the tool instead of asking you to paste:
text
When you need an API key, password, or token, call the SecureInput MCP tool
request_secret. Do not ask me to paste secrets into chat. Prefer delivery
mode "execute" with the secret in stdin/env, or "write_env" for .env files.
## How it works
agent: "I need a GitHub token to create the repo."
│ request_secret (MCP)
input inside the chat (MCP Apps hosts) ─or─ paired page on 127.0.0.1
│ encrypted to the local daemon
SecureInput daemon on 127.0.0.1
├── execute: gh auth login --with-token (token through stdin)
SecureInput is an open-source, local-first MCP server for API keys, passwords, and tokens. When your coding agent needs a credential, you type it into a small input that appears inside the chat, styled like the host's own composer. The value goes straight to a local command (stdin or env) or a .env file. The agent only gets back { "ok": true, "status": "completed", "exitCode": 0 }.
Works with Claude Code, Claude Desktop, Cursor, Codex, VS Code / GitHub Copilot, Windsurf, Cline, and any stdio MCP client. macOS and Linux, Node.js 22+.
Install · How it works · Security model · FAQ · Watch the 20-second overview
## Install
Pick your client. Every option runs npx -y secureinput mcp (Node.js 22+), which starts the shared local daemon on first use. Try it with a fake key first.
### 1. Connect your agent
Claude Code
bash
claude mcp add --scope user secureinput -- npx -y secureinput mcp
claude mcp list # secureinput: ✔ Connected
Claude Desktop : one-file bundle, no terminal
1. Download the latest secureinput-release-.mcpb from GitHub Releases. The bundle is unsigned; review the release before installing.
2. Open Settings → Desktop app → Manage next to Extensions (older versions: Settings → Extensions), then Advanced settings → Install Extension… and pick the file. See Claude's guide.
3. Ask Claude to save a fake key with SecureInput.
To upgrade, install the newer .mcpb.
Cursor : use the button above, or ~/.cursor/mcp.json
json
{ "mcpServers": { "secureinput": { "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
VS Code / GitHub Copilot : use the button above, or .vscode/mcp.json
json
{ "servers": { "secureinput": { "type": "stdio", "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
Codex CLI
bash
codex mcp add secureinput -- npx -y secureinput mcp
Or in ~/.codex/config.toml:
toml
[mcp_servers.secureinput]
command = "npx"
args = ["-y", "secureinput", "mcp"]
Windsurf, Cline, or any stdio client
json
{ "mcpServers": { "secureinput": { "command": "npx", "args": ["-y", "secureinput", "mcp"] } } }
Global install or from source
bash
npm install -g secureinput # then use command "secureinput", args ["mcp"]
secureinput doctor # checks Node, config and the daemon
From source: git clone https://github.com/r69shabh/secureinput.git && cd secureinput && npm ci && npm run build && npm link.
GUI apps may not see a Node version manager's PATH (fnm, nvm, volta). If npx isn't found, use the full path from realpath "$(which npx)" as the command.
### 2. Tell your agent to use it
Add this to your agent rules (CLAUDE.md, AGENTS.md, .cursor/rules, …) so it reaches for the tool instead of asking you to paste:
text
When you need an API key, password, or token, call the SecureInput MCP tool
request_secret. Do not ask me to paste secrets into chat. Prefer delivery
mode "execute" with the secret in stdin/env, or "write_env" for .env files.
## How it works
agent: "I need a GitHub token to create the repo."
│ request_secret (MCP)
input inside the chat (MCP Apps hosts) ─or─ paired page on 127.0.0.1
│ encrypted to the local daemon
SecureInput daemon on 127.0.0.1
├── execute: gh auth login --with-token (token through stdin)
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/r69shabh-secureinput/)
- Source
- awesome · https://github.com/r69shabh/secureinput
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.