Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/davidpastorvicente/mcpx-cli/llms.txt

Use this file to discover all available pages before exploring further.

If you already have MCP servers configured in Claude Code, GitHub Copilot CLI, VS Code, or another supported tool, you don’t need to re-enter every server by hand. MCPX can detect those existing config files, parse their server definitions, and import them straight into .agents/mcp.json so you can manage everything from one place going forward.

Before you start

MCPX can detect and import from any of the following provider config files. Make sure you’re running from the correct project directory (or pass --dir) so MCPX can find them.
ProviderProject config fileGlobal config file
Claude Code.mcp.json~/.claude.json
Antigravity CLI.gemini/config/mcp_config.json~/.gemini/config/mcp_config.json
Kimi CLI.kimi-code/mcp.json~/.kimi-code/mcp.json
OpenAI Codex.codex/config.toml~/.codex/config.toml
OpenCodeopencode.json~/.config/opencode/opencode.jsonc
GitHub Copilot CLI.copilot/mcp-config.json~/.copilot/mcp-config.json
VS Code.vscode/mcp.json(project only)
IntelliJ IDEA.idea/mcp.json(project only)

Import with the wizard

The easiest way to migrate is through mcpx init, which runs detection automatically as part of setup.
1
Run mcpx init from your project directory
2
cd my-project
mcpx init
3
You will be asked to choose project or global scope.
4
MCPX detects existing configs automatically
5
MCPX scans the directory (and, for global scope, your home directory) for all known provider config files. It prints a summary of what it found, for example:
6
┌ Detected MCP configurations
│ Claude Code - 3 server(s)
│ VS Code - 2 server(s)

7
Choose to import and select which servers
8
MCPX asks: Import these configurations? Answer Yes to import all detected servers automatically, or No to skip and configure servers manually.
9
If you answer Yes, MCPX merges every detected server into a single in-memory map. Servers with the same name from different providers are last-write-wins in detection order.
10
Select which providers to enable
11
After import, the provider selection wizard lists all supported providers. Toggle each one you want MCPX to manage and press Enter to confirm.
12
MCPX writes .agents/mcp.json and regenerates all provider files
13
MCPX saves the canonical config and immediately generates a correctly-formatted config file for each selected provider. You’ll see a Created: line for each file written.

Import from a specific provider directly

If you already have a .agents/mcp.json and want to pull in servers from one more provider — for example, you found an old .mcp.json in a project — use mcpx import and pass the provider name:
mcpx import claude-code
Valid provider names are: claude-code, antigravity-cli, kimi-cli, openai-codex, opencode, copilot-cli, vscode, intellij. If you omit the provider name, MCPX detects all available configs and lets you choose interactively:
mcpx import
After selecting which servers to bring in, MCPX asks if you want to sync providers immediately. Answer Yes and all your provider files are updated in one step.
If a server name in the imported config already exists in .agents/mcp.json, the imported version overwrites the existing entry. Review the imported servers carefully if you have customizations you want to keep.
Use --dir to import from a project in a different location without changing your working directory:
mcpx import --dir /path/to/old-project

After import

Once the import is complete, verify everything looks right:
# See all imported servers and their status
mcpx list

# Confirm all provider files are in sync
mcpx status
You can now safely remove the old manually-managed provider config files from your workflow — MCPX owns them and will regenerate them whenever you run mcpx sync or any mutation command. If the files contain secrets in env fields, consider adding them to .gitignore and letting each developer regenerate them locally.

Build docs developers (and LLMs) love