McpMux

┌─────────────────────────────────────────────────────────────────────────┐ │ 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 inplain-text JSON filesanyone on your machine can read.

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.

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 keepsitselfcurrent: new versions download and install on launch by default (toggle in Settings), so a restart is all it takes.

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.

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.

Your AI client tells McpMux which folder it's working in (its MCProot). McpMux uses that toroute 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 theWorkspacestab (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.

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 featuresarethe effective toolset a session resolves to.

Cursor, VS Code, Windsurf, Claude Code — see every AI app connected to your gateway in real time, with live status. Routing isworkspace-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.

Hand an assistant a hundred tools and it burns tokens and reaches for the wrong one. McpMux ships a built-inTool Optimizationcapability so the AI can keepitselflean — straight from chat, no config files.

Start a request with@muxand the assistant can:

- Discoverwhat's available —mcpmux_list_spaces,mcpmux_list_all_tools,mcpmux_search_tools
- Composea focused FeatureSet of just the tools it needs —mcpmux_manage_feature_set
- Pinthe current folder to that set so it sticks —mcpmux_bind_current_workspace

Reads are silent; anything that changes your setup pops aone-click approval dialog that names the exact Space— the AI proposes, you decide. The@muxtrigger 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."

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 to127.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 viazeroize

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

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

Quick install(detects your distro automatically):

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

Debian / Ubuntu(APT repository for automatic updates):

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

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

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

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 needsgnome-keyring libsecret-1-dev librsvg2-dev pkg-config.

Built withTauri 2(Rust + React 19),Axumfor the gateway,ringfor encryption,rmcpfor MCP.

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

Expose your local AI agent CLIs through one MCP endpoint

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

One remote MCP server for 500+ production APIs — Stripe, HubSpot, Postgres, Gmail, and more. OAuth and API key auth, credential management, and a CLI.

Single tool to control all 100+ API integrations, and UI components

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

Unified MCP & skill management gateway with progressive disclosure. Manages multiple MCP servers as Agent Apps, loading tool schemas on demand for 99% context token savings. Shared across Claude Code, Codex, OpenCode and more.

A collection of Model Context Protocol (MCP) servers for various tasks and integrations, supporting both Python and Node.js environments.

Self-hosted MCP gateway: convert REST/SOAP/GraphQL/SQL APIs into MCP tools with 29 pre-built adapters, OAuth2, RBAC and audit log.

A universal bridge to convert any web API into an MCP server, supporting multiple transport types.