GM

gustavodiasdev/mcpx-cli

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

12 stars 5 forks 품질 71 트렌드 19MIT

Interactive CLI to configure MCP servers for multiple AI providers

개요

Configure your MCP servers once, deploy to every AI CLI automatically. Each AI CLI tool uses a for configuring MCP (Model Context Protocol) servers: If you use multiple AI tools (and you probably do), you need to with different structures, field names, and quirks. For . maintains a single canonical config file (.mcpx.json) per project and the correct config file for each AI CLI provider you use. Navigate to your project directory and run: The interactive wizard will guide you through: 1. 🔍 — Automatically detects existing MCP configs in your project 2. 📥 — Offers to import servers from detected configs 3. ➕ — Interactive wizard to configure new MCP servers 4. 🎯 — Choose which AI CLIs you want to generate configs for 5. ⚙️ — Creates .mcpx.json and all provider config files MCPX uses a single .mcpx.json file as the source of truth:

README

원문 README의 일부입니다. 원문 보기.

🔌 MCPX

One config to rule them all. Configure your MCP servers once, deploy to every AI CLI automatically.


😩 The Problem

Each AI CLI tool uses a different file format for configuring MCP (Model Context Protocol) servers:

AI CLI Config File Format
Claude Code .mcp.json JSON
Gemini CLI .gemini/settings.json JSON
Kimi CLI ~/.kimi/mcp.json JSON
OpenAI Codex .codex/config.toml TOML
OpenCode opencode.json JSON
GitHub Copilot CLI .copilot/mcp-config.json JSON
VS Code .vscode/mcp.json JSON
IntelliJ IDEA .idea/mcp.json JSON

If you use multiple AI tools (and you probably do), you need to manually maintain 8 different config files with different structures, field names, and quirks. For every single project.


✨ The Solution

MCPX maintains a single canonical config file (.mcpx.json) per project and automatically generates the correct config file for each AI CLI provider you use.

.mcpx.json  ──────►  .mcp.json                     (Claude Code)
    │       ──────►  .gemini/settings.json          (Gemini CLI)
    │       ──────►  ~/.kimi/mcp.json               (Kimi CLI)
    │       ──────►  .codex/config.toml             (OpenAI Codex)
    │       ──────►  opencode.json                  (OpenCode)
    │       ──────►  .copilot/mcp-config.json       (Copilot CLI)
    │       ──────►  .vscode/mcp.json               (VS Code)
    └─────  ──────►  .idea/mcp.json                 (IntelliJ IDEA)

🚀 Quick Start

📦 Installation

npm install -g mcpx-cli

⚡ First Setup

Navigate to your project directory and run:

mcpx

The interactive wizard will guide you through:

  1. 🔍 Detection — Automatically detects existing MCP configs in your project
  2. 📥 Import — Offers to import servers from detected configs
  3. ➕ Add servers — Interactive wizard to configure new MCP servers
  4. 🎯 Select providers — Choose which AI CLIs you want to generate configs for
  5. ⚙️ Generate — Creates .mcpx.json and all provider config files

📋 Commands

Command Description
mcpx or mcpx init 🧙 Interactive setup wizard
mcpx add [name] ➕ Add a new MCP server
mcpx remove [name] ➖ Remove an MCP server
mcpx list 📄 List configured MCP servers
mcpx sync 🔄 Regenerate all provider config files
mcpx import [provider] 📥 Import config from an existing provider
mcpx status 📊 Show sync status of all providers
GitHub에서 전체 README 보기

설치

uvx mcp-atlassian
MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →