McpMux

io.github.mcpmux由 GitHub 帳號 mcpmux 發布v0.1.1更新於 Oct 24, 2026

McpMux — configure MCP servers once, connect every AI client through one local gateway.

概覽

AI 產生的概覽

一款桌面應用程式,執行本機 MCP 閘道,讓一個 AI 用戶端透過單一本機位址存取所有已設定的 MCP 伺服器。

可以做什麼
透過一個本機閘道位址統一接入所有 MCP 伺服器,各 AI 用戶端只需設定一次,不必分別維護設定檔。從內建登錄檔安裝伺服器,檢視其工具、提示與資源以及即時連線狀態。用隔離的 Space 分開伺服器、憑證與權限,並依專案資料夾路由工具集。用 Feature Set 限定每個用戶端可見的工具、提示與資源。允許助理自行探索、搜尋並組合工具集並固定到目前資料夾,變更需經核准。檢視並撤銷已連線的用戶端。
適用情境
當多個 AI 用戶端(例如 Cursor、Claude Desktop、VS Code 或 Windsurf)需要同一批 MCP 伺服器,希望集中設定、避免把憑證放在明文設定檔中,並限制各專案或用戶端可用的工具時適用。
執行需求
需在 Windows、macOS 或 Linux 上安裝桌面應用程式,以本機程序執行,僅限桌面端。每個 AI 用戶端需填入指向本機 HTTP 端點的閘道設定片段。從原始碼建置需 Rust 1.75+、Node.js 18+ 與 pnpm 9+;Linux 另需 keyring 與 libsecret 相關套件。
安裝前請注意
它會保存所加入伺服器的憑證(存於作業系統鑰匙圈與加密的本機資料庫),並轉送這些伺服器的呼叫;請確認各用戶端與 Space 可存取的伺服器範圍。助理對設定的變更需經核准,但讀取操作不會提示。閘道僅綁定本機位址。預設在啟動時自動下載並安裝更新,可在設定中關閉。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 McpMux,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

McpMux

[License: GPL v3] [GitHub release] [CI] [Windows] [macOS] [Linux]

One app to manage all your MCP servers across every AI client.

Website · Download · Discover Servers · Features · Discord


The Problem

Cursor, Claude Desktop, VS Code, Windsurf — they all support MCP, but each one needs its own config file. None of them talk to each other.

┌─────────────────────────────────────────────────────────────────────────┐│  Today: every client manages MCP servers independently                  ││                                                                         ││  Cursor       → config.json    → github, slack, db  + API keys         ││  Claude       → config.json    → github, slack, db  + API keys  (dupe) ││  VS Code      → settings.json  → github, slack, db  + API keys  (dupe) ││  Windsurf     → config.json    → github, slack, db  + API keys  (dupe) ││                                                                         ││  ⚠ 4 config files  ·  4 copies of every API key  ·  all plain text     │└─────────────────────────────────────────────────────────────────────────┘

Add a server? Edit four files. Rotate an API key? Edit four files. New machine? Start from scratch.

And those API keys? Sitting in plain-text JSON files anyone on your machine can read.

The Fix

McpMux is a desktop app that runs a local MCP gateway. You configure servers once — every AI client connects through a single URL.

┌─────────────────────────────────────────────────────────────────────────┐│  With McpMux: one gateway, every client                                 ││                                                                         ││  Cursor       ─┐                                                        ││  Claude       ─┤                  ┌──→  GitHub                          ││  VS Code      ─┼──→  McpMux      ├──→  Slack                           ││  Windsurf     ─┤   localhost:45818├──→  PostgreSQL                      ││  Any client   ─┘                  └──→  + all your servers              ││                                                                         ││  ✓ 1 config  ·  credentials encrypted in OS keychain  ·  instant sync  │└─────────────────────────────────────────────────────────────────────────┘

Add a server in McpMux and every connected client picks it up instantly — no restart, no manual refresh. Remove a tool or update a prompt? Every client knows immediately.

Lightweight and cross-platform — built in Rust with Tauri 2, McpMux uses minimal CPU and memory while running quietly in your system tray on Windows, macOS, and Linux.

[McpMux Dashboard]


How It Works

1. Install servers from the built-in registry — or add your own

2. Paste one config into each AI client (the last config you'll ever need):

json
{  "mcpServers": {    "mcpmux": {      "type": "http",      "url": "http://localhost:45818/mcp"    }  }}

3. Done. Every tool from every server is available in every client, right now.

McpMux routes calls to the right server, refreshes OAuth tokens automatically, and keeps credentials encrypted in your OS keychain — you never think about it again. It also keeps itself current: new versions download and install on launch by default (toggle in Settings), so a restart is all it takes.


Features

All Your Servers, One Place

No more duplicating server configs across Cursor, Claude, VS Code, and Windsurf. Install a server in McpMux and it's immediately available everywhere. Expand any server to inspect its tools, prompts, and resources. See live connection status. OAuth tokens refresh automatically in the background.

[Server Management — Azure, AWS, Notion, Docker, Slack all connected]

100+ Servers, One Click

Stop hunting for MCP server repos and hand-writing transport configs. Browse a curated registry of 100+ servers — GitHub, Slack, PostgreSQL, Docker, Notion, AWS, Azure, and more. Click install, enter your credentials, and the server is live across every AI client you use. You can also browse the full registry at mcpmux.com.

[Discover — browse 100+ servers and install with one click]

The full registry is also available on the web at mcpmux.com — with search, categories, and one-click install via deep links.

[mcpmux.com — server registry on the web]

Workspaces That Keep Things Separate

Create isolated Spaces — each with their own servers, credentials, and permissions. A "Work" space for company databases and internal APIs. A "Personal" space for side projects. Switch in one click from the sidebar and every connected AI client follows automatically. No more accidentally querying your personal database from a work project.

[Workspaces — switch context instantly from the sidebar]

Different Tools for Different Folders

Your AI client tells McpMux which folder it's working in (its MCP root). McpMux uses that to route each workspace to its own toolset — open your backend repo and the AI sees your database and deploy tools; open a docs folder and it sees only search and filesystem. Map a folder once in the Workspaces tab (or let the AI do it — see below) and every future session from that exact path resolves automatically. Matching is per-folder and exact, so nothing leaks across projects.

[Workspaces — map a folder to the Space and FeatureSet it should get]

Control What Each Client Can Do

Not every AI client should have the same power. Create Feature Sets — curated bundles that control exactly which tools, prompts, and resources are exposed. Build a "Read Only" set for cautious workflows, a "React Development" set with just GitHub and Filesystem, or a "Full Stack Dev" set with everything — then route a folder to it via a Workspace mapping. A FeatureSet's included features are the effective toolset a session resolves to.

[Feature Sets — pick exactly which tools each bundle exposes, per server]

See and Manage Every Connected Client

Cursor, VS Code, Windsurf, Claude Code — see every AI app connected to your gateway in real time, with live status. Routing is workspace-driven: each app's toolset is decided by the Workspace binding for the folder it reports, not configured per app. Open any app to rename it, see how it's routed, or revoke its connection. New apps authenticate via OAuth with a one-click approval flow.

[Connected apps — routing is workspace-driven per reported folder]

Let Your AI Curate Its Own Toolset

Hand an assistant a hundred tools and it burns tokens and reaches for the wrong one. McpMux ships a built-in Tool Optimization capability so the AI can keep itself lean — straight from chat, no config files.

Start a request with @mux and the assistant can:

  • Discover what's available — mcpmux_list_spaces, mcpmux_list_all_tools, mcpmux_search_tools
  • Compose a focused FeatureSet of just the tools it needs — mcpmux_manage_feature_set
  • Pin the current folder to that set so it sticks — mcpmux_bind_current_workspace

[Tool Optimization — the built-in self-management tools the AI drives, reads silent and writes gated]

Reads are silent; anything that changes your setup pops a one-click approval dialog that names the exact Space — the AI proposes, you decide. The @mux trigger keeps these requests cleanly separated from your real work, and every operation can target a specific Space by id.

[Approval — every self-management write asks first, showing the target Space and the exact tool diff]

"@mux build a minimal toolset for this Next.js repo and pin it to this folder."


Security

MCP defaults to plain-text config files with raw API keys. McpMux replaces that with defense in depth:

  • OS Keychain — secrets in platform-native secure storage (DPAPI on Windows, Keychain on macOS, libsecret on Linux), never in plain-text files
  • AES-256-GCM — field-level database encryption for all sensitive data
  • OAuth 2.1 + PKCE — standard auth flow with automatic token refresh
  • Local-only gateway — binds to 127.0.0.1, nothing exposed to the network
  • Per-client access keys — each AI client authenticates independently with granular permissions
  • Sanitized logs — tokens and secrets never appear in log output
  • Memory zeroization — secrets wiped from memory after use via zeroize

All MCP traffic stays on your machine. Cloud sync (optional, coming soon) only covers config metadata — never credentials or payloads.


Getting Started

1. Download McpMux — Windows, macOS, Linux

2. Add servers — use the Discover tab to browse 100+ servers, or explore servers on mcpmux.com and install with one click

3. Paste the config — copy the snippet from the Dashboard into your AI clients

That's the last config file you'll ever touch.

Linux quick install: curl -fsSL https://install.mcpmux.com | bash

macOS via Homebrew: brew install --cask mcpmux/tap/mcpmux

See mcpmux.com/download for all platforms and install methods.


Install on Linux

Quick install (detects your distro automatically):

bash
curl -fsSL https://install.mcpmux.com | bash
Other install methods

Debian / Ubuntu (APT repository for automatic updates):

bash
curl -fsSL https://install.mcpmux.com/apt | sudo bash

Fedora / RHEL (from GitHub Releases):

bash
# Download the latest .rpmsudo dnf install https://github.com/mcpmux/mcp-mux/releases/latest/download/mcpmux-0.0.12-1.amd64.rpm

Arch Linux (AUR):

bash
yay -S mcpmux-bin

AppImage (any distro):

bash
curl -fsSL https://install.mcpmux.com | bash  # auto-detects, falls back to AppImage

Or download directly from GitHub Releases.


Development

bash
pnpm setup    # First-time: install dependenciespnpm dev      # Start developmentpnpm build    # Production buildpnpm test     # Run all tests

Prerequisites: Rust 1.75+, Node.js 18+, pnpm 9+. Linux also needs gnome-keyring libsecret-1-dev librsvg2-dev pkg-config.

Built with Tauri 2 (Rust + React 19), Axum for the gateway, ring for encryption, rmcp for MCP.

Project structure
mcp-mux/├── apps/desktop/          # Tauri desktop app (React + Rust)├── crates/│   ├── mcpmux-core/       # Domain logic│   ├── mcpmux-gateway/    # HTTP gateway, OAuth, routing│   ├── mcpmux-storage/    # SQLite + encryption + OS keychain│   └── mcpmux-mcp/        # MCP protocol├── packages/ui/           # Shared UI components└── tests/                 # Unit, integration, E2E tests

Links

Contributing

See CONTRIBUTING.md for guidelines.

License

GNU General Public License v3.0

來源:README.md,提交 87df4a2

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分