mcp-manager

<p align="center"> <img src="./src-tauri/icons/app-icon-rounded.png" alt="MCP Manager logo" width="160" height="160" /> </p> <h1 align="center">MCP Manager</h1> <p align="center"> A cross-platform desktop app for managing MCP server configs across Claude Code, Codex, Cursor, VS Code, OpenCode, Gemini CLI, and more. </p> <p align="center"> <a href="./LICENSE"><img src="https://img.shields.io/badge/license-MIT-0f172a.svg" alt="MIT License" /></a> <img src="https://img.shields.io/badge/Tauri-2-24c8db.svg" alt="Tauri 2" /> <img src="https://img.shields.io/badge/React-19-61dafb.svg" alt="React 19" /> <img src="https://img.shields.io/badge/Rust-stable-f74c00.svg" alt="Rust stable" /> <img src="https://img.shields.io/badge/platform-macOS%20%7C%20Windows%20%7C%20Linux-16a34a.svg" alt="Cross-platform" /> </p> <p align="center"> English | <a href="./README.zh-CN.md">简体中文</a> | <a href="https://github.com/xjeway/mcp-manager/releases/latest">Latest Release</a> | <a href="./docs/releasing.md">Release Guide</a> </p>

Why MCP Manager

MCP Manager is a cross-platform desktop app for people who do not want to hand-edit multiple MCP client configs.

• Keep a unified MCP workspace for all configured servers
• Import existing entries from local client configuration
• Find servers in the GitHub MCP Registry, the official MCP Registry, or any registry you add that implements the MCP Registry API, and add them in a few clicks
• Edit servers in form mode or raw JSON mode
• Apply generated configuration to multiple supported clients
• Review risky writes before files change
• Keep backups and rollback support during apply
• Use light mode, dark mode, or system theme
• Use the UI in English, Simplified Chinese, Traditional Chinese, Japanese, Korean, German, French, Spanish, Brazilian Portuguese, or Russian (follows the system language by default)

Screenshots

Download & Installation

System Requirements

• Desktop packages are published for macOS, Windows, and Linux
• Building from source requires Node.js 20+, npm 10+, Rust stable, and Tauri system dependencies for your platform

macOS

Homebrew

brew tap xjeway/mcp-manager
brew install --cask mcp-manager
brew update
brew upgrade --cask mcp-manager

Manual Download

Download from:

• https://github.com/xjeway/mcp-manager/releases/latest

Example macOS asset names:

• MCP-Manager-<version>-<arch>.dmg

Arch guide:

• Apple Silicon Macs: choose arm64 or aarch64 assets
• Intel Macs: choose x64 or x86_64 assets

After downloading the correct macOS asset, open it locally:

open ~/Downloads/MCP-Manager*.dmg

Current public macOS releases may still be unsigned while Apple signing and notarization are being prepared. If Gatekeeper blocks MCP Manager.app, use this fallback flow:

1. Drag MCP Manager.app into /Applications.
2. In Finder, right-click the app once and choose Open.
3. If macOS still says the app cannot be opened or is damaged, remove the quarantine flag and try again:

xattr -dr com.apple.quarantine "/Applications/MCP Manager.app"
open "/Applications/MCP Manager.app"

Windows

Manual Download

Download from:

• https://github.com/xjeway/mcp-manager/releases/latest

Example Windows asset names:

• MCP-Manager-<version>-<arch>-setup.exe
• MCP-Manager-<version>-x64.msi

Arch guide:

• Windows on ARM devices: choose the arm64 installer asset
• Intel / AMD PCs: choose the x64 or x86_64 installer asset

Package guide:

• setup.exe: available for both Windows x64 and Windows arm64
• .msi: published for stable Windows x64 releases

Choose the asset that matches your arch, then run it locally:

Start-Process "C:\Path\To\MCP-Manager-Setup.exe"
# or
msiexec /i "C:\Path\To\MCP-Manager.msi"

Linux Users

Download the latest Linux build from the Releases page:

Example Linux asset names:

• mcp-manager_<version>_<arch>.deb (Debian/Ubuntu)
• mcp-manager-<version>.<arch>.rpm (Fedora/RHEL/openSUSE)
• MCP-Manager-<version>-<arch>.AppImage (Universal)

Expanded distro guide:

• .deb: Debian, Ubuntu, Linux Mint, Pop!_OS, elementary OS, and other Debian-based distributions
• .rpm: Fedora, RHEL, Rocky Linux, AlmaLinux, openSUSE, and other RPM-based distributions
• .AppImage: portable option for desktop Linux when you do not want a system package

Arch guide:

• x86_64 or amd64 for most Intel and AMD 64-bit PCs
• arm64 or aarch64 for ARM64 Linux devices, when that asset is published in the release

Install with the matching command:

# Debian / Ubuntu
sudo dpkg -i ./mcp-manager_<version>_amd64.deb

# Fedora / RHEL / openSUSE
sudo rpm -i ./mcp-manager-<version>.x86_64.rpm

# AppImage
chmod +x ./MCP-Manager-<version>-<arch>.AppImage
./MCP-Manager-<version>-<arch>.AppImage

Build From Source

Install dependencies:

make install

Run the desktop app:

make tauri-dev

Run the web UI only:

make dev

Quick Start

1. Launch MCP Manager.
2. Import existing entries from local client configuration files.
3. Edit servers in form mode or JSON mode.
4. Apply the generated config to one or more supported clients.
5. Review warnings, then write with backup and rollback protection.

Supported Clients

Available Now

| Client | Import | Apply | | --- | --- | --- | | Claude Code | ✅ | ✅ | | Claude Desktop | ✅ | ✅ | | Codex | ✅ | ✅ | | Cursor | ✅ | ✅ | | OpenCode | ✅ | ✅ | | GitHub Copilot | ✅ | ✅ | | Gemini CLI | ✅ | ✅ | | Antigravity | ✅ | ✅ | | iFlow | ✅ | ✅ | | Qwen Code | ✅ | ✅ | | Cline | ✅ | ✅ | | Windsurf | ✅ | ✅ | | Kiro | ✅ | ✅ | | Qoder | ✅ | ✅ | | VS Code | ✅ | ✅ |

Command Line (Preview)

A command-line tool, mcpmgr, shares the desktop app's server list, so changes made in either show up in the other. Run it with npx, or install it with npm or Homebrew:

npx @mcpmgr/cli list
npm install -g @mcpmgr/cli
brew install xjeway/mcp-manager/mcpmgr

mcpmgr add context7 -- npx -y @upstash/context7-mcp@latest
mcpmgr add linear --url https://mcp.linear.app/mcp -a cursor,claude-code
mcpmgr add --from mcp.json --project
mcpmgr list
mcpmgr remove context7 -a codex
mcpmgr rollback

From a checkout, use cargo run --bin mcpmgr -- <command>.

In a terminal, add walks you through choosing servers, clients and user or project scope, then shows what each client file will get before writing. Every step can be answered with a flag (--server, --env, --app, --global/--project, --yes); --dry-run previews and --json prints machine-readable output. Run inside an AI coding agent such as Claude Code or Codex, it skips the prompts and targets that agent's client.

How It Works

• The app reads local client configuration and converts it into the internal model
• Apply writes client-specific output with atomic updates, backup, and rollback support
• The online marketplace turns a registry entry (npm, PyPI, Docker image, or remote URL) into a server draft you review in the editor; every client starts turned off

Network Access

MCP Manager only goes online to check for updates and, while the marketplace page is open, to query MCP registries. Registry results are cached: the marketplace opens from the cache and updates it in the background after 6 hours, and still works offline with the last data. Adding a source under Settings → Marketplace sources sends one check request to it. Turn the marketplace off under Settings → Online marketplace to stop those requests entirely.

Scope

Current scope is focused on configuration management. Runtime lifecycle management such as process start, stop, logs, and health checks is intentionally out of scope for v1.

Project Structure

mcp-manager/
  src/                frontend application
  src-tauri/          tauri app (commands exposed to the frontend, online marketplace)
  crates/
    mcp-manager-core/ client adapters, parsing, safe writes (shared)
    mcp-manager-cli/  command-line tool (`mcpmgr`)
  public/             static assets and branding
  docs/               release notes and design references
  openspec/           change and spec tracking

Core Modules (crates/mcp-manager-core)

• platform: OS-aware path resolution and environment context
• adapters: per-client import and apply logic
• core: canonical config model and merge behavior
• parser: YAML / JSON / TOML parsing and extraction
• storage: atomic write, backup, and rollback
• store: the shared servers.yaml, with locking and change detection
• workflow: import, preview, and apply across all clients
• ops: server list edits and validation, mirrored from the frontend

Development

make install
make dev
make tauri-dev
make build
make test
make check
make tauri-build

Release Automation

This repository includes GitHub Actions workflows for CI and desktop release packaging with the official Tauri release action.

See docs/releasing.md for:

• tag-driven GitHub Release publishing
• macOS, Windows, and Linux package generation
• updater signing setup
• optional platform code signing
• version sync and git tag helper commands

Contributing

Issues and pull requests are welcome.

If you plan to contribute a non-trivial change, open an issue or discussion first so the scope and direction are clear before implementation.

Local Development

make install
make tauri-dev

Before Opening a PR

make test
make check

Keep README.md and README.zh-CN.md in sync when changing user-facing project documentation.

Disclaimer

This project is developed primarily with AI assistance (AI-driven development). Code, tests, and documentation are largely AI-generated and reviewed by a human maintainer, so they may still contain mistakes.

MCP Manager reads and rewrites the configuration files of other tools. Backups and rollback are built in, but you should still back up important client configs yourself, review changes before applying them, and use the software at your own risk. It is provided "as is" under the MIT License, without warranty of any kind.

License

MIT @ xJeway