原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

McpMux

✓ Brand-named GitHub · github.com/mcpmux

作者:mcpmux版本 0.1.1i★ 27 (整个仓库的星标)i–官方网站 ↗
注册名称io.github.mcpmux/mcp-mux

安装方法

What it does

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

  • Connects –
  • Account or key No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 McpMux

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 McpMux

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 McpMux

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 McpMux

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 McpMux

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 McpMux 的人💬 讨论 →

一览

GitHub 星标i
27 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
许可证i
GPL-3.0
连接方式
–
最新版本i
0.1.1
分类i
其他
发布到注册中心i
2026年2月18日
代码最后更新i
2026年11月3日
作者
mcpmux
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 mcpmux 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于16天前

  • ✓ 通过

    有许可证

    使用 GPL-3.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/mcpmux-mcp-mux-gsd3z.svg)](https://mcp.popnx.com/en/servers/mcpmux-mcp-mux-gsd3z)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20693 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20693 个服务器的 1% 更新
  • 基础检查结果等于或优于此分类中其他 20693 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

McpMux 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于16天前,最新版本(0.1.1)于9个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
McpMux
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/44/44/41/44/4
许可证GPL-3.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

McpMux

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

[Website](https://mcpmux.com) · [Download](https://mcpmux.com/download) · [Discover Servers](https://mcpmux.com) · [Features](https://mcpmux.com/features) · [Discord](https://discord.gg/b4RDmwAHAN)


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.


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):

{

"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.

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.

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

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.

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.

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.

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.

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

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.

*"@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](https://mcpmux.com/download) — 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):

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

Other install methods

Debian / Ubuntu (APT repository for automatic updates):

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

Fedora / RHEL (from GitHub Releases):

# Download the latest .rpm

sudo dnf install https://github.com/mcpmux/mcp-mux/releases/latest/download/mcpmux-0.0.12-1.amd64.rpm

Arch Linux (AUR):

yay -S mcpmux-bin

AppImage (any distro):

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

Or download directly from GitHub Releases.


Development

pnpm setup    # First-time: install dependencies

pnpm dev # Start development pnpm build # Production build pnpm 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

  • Website & Server Discovery —

只显示了开头部分;其余内容请在仓库中阅读