Local MCP secret broker

Give your AI a button.
Not your secret.

SecretBridge opens a native popup when an AI needs an API key or credential. You paste it there, reuse it later, and authorize direct .env writes in your workspace—without putting the value in chat.

Download v0.1.5 Build from source X @Abomination81 ↗

Free and open source
macOS + Windows
No server or account

One clean handoff

The secret takes the short route.

The model handles the label and destination. SecretBridge handles the value locally.

AI requests it

The client sends a label, purpose, and suggested variable name—never the value.

⌨

You enter it

A labeled native popup collects the secret in a masked field.

⌑

Your OS stores it

macOS Keychain or Windows Credential Manager keeps it available for reuse.

.env

Save & Use

Your submission authorizes writes in the displayed workspace, with no second popup.

Built for the actual problem

Nothing magical. Nothing in chat.

SecretBridge does not pretend a local .env file is Fort Knox. It prevents the easy, permanent mistake: placing a reusable credential in an AI conversation or tool transcript.

Native masked entryThe value never becomes an MCP argument.
Reusable credentialsAsk for the same labeled secret in future sessions.
Explicit completion receiptThe AI knows when you clicked save and can continue.
Workspace-scoped writesSave & Use authorizes one workspace. Every file path and variable name is checked.
Local-only designNo hosted service, account, analytics, or network listener.

Source-first installation

Install on Mac or Windows.

Rust builds the executable locally, avoiding warnings for unsigned downloaded applications.

●

macOS

Apple Silicon or Intel

git clone https://github.com/Abomination81/secret-bridge-mcp.git
cd secret-bridge-mcp
./scripts/install.sh

Installs to ~/.local/bin/secret-bridge-mcp.

⊞

Windows

PowerShell on Windows 11

git clone https://github.com/Abomination81/secret-bridge-mcp.git
cd secret-bridge-mcp
.\scripts\install.ps1

Installs under %LOCALAPPDATA%\SecretBridge.

Requires the free Rust toolchain. Tagged GitHub releases also include unsigned convenience archives and SHA-256 checksums.

Works where local MCP works

Connect your AI client.

Codex

codex mcp add secret-bridge -- \
  /absolute/path/secret-bridge-mcp \
  --workspace-per-request \
  --client-name Codex

Claude Code

claude mcp add --scope user \
  --transport stdio secret-bridge -- \
  /absolute/path/secret-bridge-mcp \
  --workspace-per-request \
  --client-name "Claude Code"

Make it automatic for Codex and Claude Code: after connecting, run sh ./scripts/enable-defaults.sh both on macOS or .\scripts\enable-defaults.ps1 both in Windows PowerShell from your checkout, then start a new session. This adds a persistent preference to use SecretBridge whenever a credential is needed. Existing tool permissions and popup approvals still apply.

Also works with Gemini CLI and other local MCP clients that can launch a standard-input/output server. Full configuration examples are in the README.

The honest boundary

Out of the conversation—not invisible on disk.

SecretBridge keeps values out of AI messages, MCP payloads, logs, and command history during collection and reuse. Once a credential is written into an authorized workspace’s .env file, that file is normal local plaintext and can be read by software with filesystem access.

Read the complete security model →

SecretBridge MCP

Stop pasting keys into AI chats.

Free, local, open source, and built by Abomination81.

Download v0.1.5 Follow on X

Give your AI a button.Not your secret.

Example API key