Supabase
MCP server for interacting with the Supabase platform
作者による説明(英語の原文)
AI-safe credential broker for MCP — run saved SSH/MySQL/psql aliases; passwords never reach AI.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"brokre": {
"command": "npx",
"args": [
"-y",
"brokre"
]
}
}
}ターミナルでこれを実行します
claude mcp add brokre -- npx -y brokreプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"brokre": {
"command": "npx",
"args": [
"-y",
"brokre"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"brokre": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"brokre"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント Furowu で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.2.36)がレジストリに届いたのは44 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Supabase, MongoDB MCP Server, Elasticsearch MCP Server
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP server for interacting with the Supabase platform
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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 (成都同创合一科技有限公司).
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 -g brokre # or: npx -y brokre@latest
| Capability | What happens |
|---|---|
| Auto MCP registration | postinstall 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 upgrade | On each MCP start, compares npm package version with PATH / ~/.brokre/bin/brokre; downloads matching GitHub Release when missing or older. |
| CLI without npm | brokre version / brokre upgrade for install.sh users; brokre mcp setup to register MCP after installing IDEs. |
| Supported IDEs | Cursor, 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"] }
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.
| Advantage | What it means in practice |
|---|---|
| Single control plane | Register a bastion SSH alias (b150), sync inner aliases from remote brokre, and drive the whole cluster from brokre list / MCP brokre_list |
| Smart routing | b150::db, b150::app-01, multi-hop b1::b2::inner — route separator ::; routed SSH uses SessionRelay by default |
| Secrets stay on the bastion | Routed exec runs ~/.brokre/bin/brokre on the jump host; laptop holds metadata and session gate, not inner-host passwords |
| Human gate, agent-friendly | Bastion 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 defaults | Local-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 routes | brokre_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.
brokre is built around one rule: secrets stay out of the AI's reach and out of observable process state.
| Layer | What brokre does |
|---|---|
| No env / `ps` leakage | Injection 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 rest | Per-field AES-256-GCM; DEK wrapped with OS keyring (Linux) or ~/.brokre/.master_kek (macOS) + optional Argon2id reveal passphrase |
| Audit | HMAC-chained JSONL at ~/.brokre/audit/audit.log; brokre audit list queries history (metadata only); brokre audit verify detects tampering |
| MCP boundary | MCP 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 UI | Binds 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 hardening | Core dumps disabled, ptrace checks (Linux), optional mlockall — see docs/HARDENING.md |
Full threat model: SECURITY.md, THREAT_MODEL.md.
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.
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.
| Path | Best for | Install | MCP in IDEs | CLI upgrade | |
|---|---|---|---|---|---|
| npm (recommended) | AI users; want one command | npm install -g brokre | Automatic on install (postinstall) | npm + auto-download on each MCP start | |
| install.sh / Homebrew | Production; no Node for daily use | `curl … \ | bash or brew install brokre` | Run brokre mcp setup after IDE install | brokre version / brokre upgrade |
| Manual MCP JSON | Custom layouts only | CLI or npm already present | Edit IDE config by hand | Depends 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"] }.
npm install -g brokre
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:
brokre-mcp / npx -y brokre@latest spawns brokre mcp.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.PATH or ~/.brokre/bin/brokre is older than the npm package, the matching GitHub Release is downloaded.IDEs covered by auto-setup
| IDE | Global 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.
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
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
冒頭だけを表示しています。続きはリポジトリで読めます