Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

brokre

by Furowuversion 0.2.36i★ –iRuns on your computer
Registry nameio.github.Furowu/brokre

Install

Overview

Description from the maker (original English)

AI-safe credential broker for MCP — run saved SSH/MySQL/psql aliases; passwords never reach AI.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Databases & datasets

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "brokre": {
      "command": "npx",
      "args": [
        "-y",
        "brokre"
      ]
    }
  }
}

Run this in your terminal

claude mcp add brokre -- npx -y brokre

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "brokre": {
      "command": "npx",
      "args": [
        "-y",
        "brokre"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "brokre": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "brokre"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Furowu, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

  • More stars than 0% of the other 956 servers in this category
  • Published to the registry more recently than 42% of the other 956 servers in this category
  • Basic checks equal to or better than 100% of the other 956 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is brokre safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.36) reached the registry 44 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday
Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 3 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

brokre — AI-safe Credential Broker

English | 简体中文

brokre is a local credential broker for AI agents and humans. Use it with Cursor, Claude Code, Kimi Code, Trae, OpenClaw, Hermes Agent, ChatClaw, and other MCP-capable clients to run ssh, mysql, psql, and more — passwords never enter AI context, environment variables, or `ps` output. It wraps any CLI on your `PATH` — not only SSH or MySQL — and injects saved passwords at the prompt without exposing plaintext to the AI process, shell history, or process environment.

Developed by Techinone (成都同创合一科技有限公司).

What's New in 0.2.17

0.2.17 is the current release: SessionRelay routed SSH by default, multi-hop bastion routes, local-only list by default, and the existing one-command npm install / auto MCP registration / auto binary upgrade flow.

npm — install, auto-update, auto MCP setup
npm install -g brokre          # or: npx -y brokre@latest
CapabilityWhat happens
Auto MCP registrationpostinstall runs brokre-setup-mcp — detects installed IDEs only and merges npx -y brokre@latest into each global MCP config. Re-run: brokre mcp setup or npx brokre-setup-mcp. Skip: BROKRE_MCP_SKIP_SETUP=1.
Auto binary upgradeOn each MCP start, compares npm package version with PATH / ~/.brokre/bin/brokre; downloads matching GitHub Release when missing or older.
CLI without npmbrokre version / brokre upgrade for install.sh users; brokre mcp setup to register MCP after installing IDEs.
Supported IDEsCursor, VS Code, VS Code Insiders, Claude Code, Claude Desktop, Trae, Kimi Code, Windsurf, OpenClaw, Codex CLI, Gemini CLI, Hermes Agent, Continue, Zed — see packages/brokre-mcp/README.md.

Recommended MCP config (also applied by auto-setup):

{ "command": "npx", "args": ["-y", "brokre@latest"] }
Bastion broker — cluster management

The bastion layer lets AI agents operate many hosts behind one jump box without copying vault passwords into context or scattering secrets on the laptop.

AdvantageWhat it means in practice
Single control planeRegister a bastion SSH alias (b150), sync inner aliases from remote brokre, and drive the whole cluster from brokre list / MCP brokre_list
Smart routingb150::db, b150::app-01, multi-hop b1::b2::inner — route separator ::; routed SSH uses SessionRelay by default
Secrets stay on the bastionRouted exec runs ~/.brokre/bin/brokre on the jump host; laptop holds metadata and session gate, not inner-host passwords
Human gate, agent-friendlyBastion outbound requires unlock (TTY, /bastion-auth, or MCP URL elicitation); gate auth survives manage UI idle expiry so long MCP runs keep working
Cluster-safe defaultsLocal-only list by default; explicit bastion discovery; reachability probes with ms timeouts and concurrency caps; loop detection and audit route/bastion fields
Privileged ops over routesbrokre_exec_elevated and sudo/sudo -i paths work through bastions with session reuse and PTY hardening

Typical flow for a K8s / DB / batch cluster behind one entry host:

brokre bastion enable b150

brokre bastion sync b150 --json # pull inner alias catalog brokre bastion unlock brokre list --include-bastions --json # b150::db, b150::worker-01, … brokre ssh b150::db systemctl status # MCP: brokre_exec with routed alias

MCP equivalent:

{ "binary": "ssh", "args": ["b150::db", "uname", "-a"] }

Gate policy (default vs strict) — see Bastion gate policy below. Gate is inactive until brokre bastion set-key; then default unlocks only bastion outbound paths; strict requires unlock for every exec while list remains local-only unless bastion discovery is requested.

See Cross-network list inheritance and Bastion proxy below for setup details.

CLI security (core)

brokre is built around one rule: secrets stay out of the AI's reach and out of observable process state.

LayerWhat brokre does
No env / `ps` leakageInjection is PTY prompt-based — passwords are never passed via -p, SSHPASS, MYSQL_PWD, or exported env vars
Parent never holds plaintext (Unix)Saved passwords decrypt in a short-lived brokre --internal-injector child, written once to the PTY, then the child exits
AI cannot `reveal`brokre reveal requires a real TTY + master passphrase; unavailable in the web UI and not exposed via MCP
Vault at restPer-field AES-256-GCM; DEK wrapped with OS keyring (Linux) or ~/.brokre/.master_kek (macOS) + optional Argon2id reveal passphrase
AuditHMAC-chained JSONL at ~/.brokre/audit/audit.log; brokre audit list queries history (metadata only); brokre audit verify detects tampering
MCP boundaryMCP exposes metadata (brokre_list), exec (brokre_exec, brokre_exec_elevated), brokre_setup, and read-only audit (brokre_audit_list, brokre_audit_verify) — no passwords, session tokens, or reveal
Manage UIBinds 127.0.0.1 only; passwords are write-only; audit log tab for history; session token printed in your terminal, never returned to AI
OS hardeningCore dumps disabled, ptrace checks (Linux), optional mlockall — see docs/HARDENING.md

Full threat model: SECURITY.md, THREAT_MODEL.md.

Any CLI on PATH (generic by design)

brokre is not a fixed list of database/SSH wrappers. The core model is:

brokre <any-cli-on-PATH> [args...]

First connection: run verbatim, capture the password you type at the prompt, offer to save as an alias. Next time: brokre … auto-injects — AI and scripts only see the alias name.

Preset prompt patterns ship for common tools (ssh, mysql, psql, redis-cli, ftp, clickhouse, git, docker, kubectl, sudo, …). Everything else uses a generic password: / passphrase: matcher — no code changes required.

brokre gsql prod-cluster -c "SELECT 1"    # any proprietary CLI on PATH

brokre kubectl get pods # if your cluster CLI prompts for a password brokre my-internal-tool --host db.internal

Customize when needed:

  • ~/.brokre/prompts.toml — per-binary prompt regex overrides
  • ~/.brokre/manage.toml — custom sections in the manage UI (e.g. GaussDB, internal tools)

Built-in manage UI tabs (when the binary is installed) include SSH, FTP, MySQL, PostgreSQL, Redis, ClickHouse, MinIO — convenience only; the PTY wrapper works for any CLI.

Install (MCP first — recommended for AI)

The npm package brokre launches the local brokre mcp server over stdio for Cursor, Claude Code, Kimi Code, Trae, OpenClaw, Windsurf, VS Code, and other MCP clients.

Choose your install path
PathBest forInstallMCP in IDEsCLI upgrade
npm (recommended)AI users; want one commandnpm install -g brokreAutomatic on install (postinstall)npm + auto-download on each MCP start
install.sh / HomebrewProduction; no Node for daily use`curl … \bash or brew install brokre`Run brokre mcp setup after IDE installbrokre version / brokre upgrade
Manual MCP JSONCustom layouts onlyCLI or npm already presentEdit IDE config by handDepends on how CLI was installed

Recommended MCP entry (also what auto-setup writes):

{ "command": "npx", "args": ["-y", "brokre@latest"] }

No Node — point MCP at the native binary: { "command": "brokre", "args": ["mcp"] }.

Path A — npm one-liner (0.2.8+)
npm install -g brokre

or without global install:

npx -y brokre@latest

Windows: npm install -g brokre, open a new terminal, run brokre --version (first run downloads the native CLI if needed). Local npm i brokre (no -g) is not on PATH.

On npm install, three things happen automatically:

  1. MCP launcher — brokre-mcp / npx -y brokre@latest spawns brokre mcp.
  2. IDE auto-registration — postinstall runs brokre-setup-mcp: detects installed IDEs only (app, CLI, or real usage artifacts — not empty folders) and merges the MCP entry above into each global config. Idempotent; preserves your other MCP servers.
  3. Binary auto-upgrade — on each MCP start, if PATH or ~/.brokre/bin/brokre is older than the npm package, the matching GitHub Release is downloaded.

IDEs covered by auto-setup

IDEGlobal config
Cursor~/.cursor/mcp.json
VS Code / Insiders…/Code/User/mcp.json
Claude Code~/.claude.json
Claude Desktop…/Claude/claude_desktop_config.json
Trae…/Trae/User/mcp.json
Kimi Code~/.kimi-code/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
OpenClaw~/.openclaw/openclaw.json (mcp.servers)
Codex CLI~/.codex/config.toml (mcp_servers.brokre)
Gemini CLI~/.gemini/settings.json
Hermes Agent~/.hermes/config.yaml (mcp_servers)
Continue~/.continue/config.yaml or ~/.continue/mcpServers/brokre.yaml
Zed~/.config/zed/settings.json (context_servers)
ChatGPT Desktop_(unsupported — remote Connectors UI only)_
Grok Bot_(info tip — connectors/plugins; no mcp.json)_

Re-run registration (e.g. you installed brokre before Cursor, then installed Cursor later):

brokre mcp setup              # via CLI — same logic as postinstall

npx brokre-setup-mcp # via npm brokre mcp setup --dry-run # preview only brokre mcp setup --force # overwrite existing brokre entry

Skip auto-registration on npm install: BROKRE_MCP_SKIP_SETUP=1. Disable binary auto-download: BROKRE_SKIP_AUTO_INSTALL=1. Pin a binary: BROKRE_BIN=/path/to/brokre.

Requires Node.js 18+ for the npm path.

Path B — Native CLI (install.sh / Homebrew, no npm)
curl -fsSL https://raw.githubusercontent.com/Furowu/brokre/main/install.sh | bash
brew tap Furowu/brokre

brew install brokre

Version and upgrade (built into the CLI — no npm required):

brokre version                # version, binary path, install type

brokre version --check # compare with latest GitHub release brokre version --check --json brokre upgrade # download latest release (curl + tar) brokre upgrade --check # exit 1 if an update is available brokre upgrade 0.2.10 # install a specific version brokre upgrade --force # reinstall even when up to date

Re-run install.sh also upgrades when a newer release exists.

Register MCP after CLI install (needs Node for the setup script, or npx fallback):

brokre mcp setup
Manual per-IDE setup (optional)

Use this only if you skip auto-setup or need project-scoped config.

Cursor — one-click install, or ~/.cursor/mcp.json:

{

"mcpServers": { "brokre": { "command": "npx", "args": ["-y", "brokre@latest"] } } }

Claude Code — user scope in ~/.claude.json or claude mcp add --scope user brokre -- npx -y brokre@latest. Project scope: .mcp.json with "type": "stdio".

More clients

Only the beginning is shown; read the rest in the repo

Ask PopNx