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.

mcpx list and mcpx status are read-only inspection commands — they never modify any file. Use them to get a quick overview of what is configured and whether everything is up to date before or after making changes.

​
mcpx list

mcpx list displays every MCP server defined in your canonical config along with its transport type, command or URL, and disabled status. 
mcpx list [--dir <path>] [--verbose]

​
Output

Each server is shown with its name (bold), transport in parentheses, a [disabled] label when applicable, and the full command line or URL on the line below. After the server list, the names of all configured providers are printed. 
┌─────────────────────────────────────────────────────┐
│  MCP Servers                                        │
│                                                     │
│  github (stdio)                                     │
│    npx -y @anthropic-ai/mcp-github-server           │
│                                                     │
│  my-api (http) [disabled]                           │
│    https://mcp.example.com                          │
└─────────────────────────────────────────────────────┘
Enabled providers: Claude Code, Copilot CLI
If no .agents/mcp.json exists, MCPX prints a warning and directs you to run mcpx init. If the config file exists but has no servers, MCPX reports that no MCP servers are configured.

​
mcpx status

mcpx status compares each generated provider config file on disk against what MCPX would produce from the current canonical config, and reports whether each file is in sync. 
mcpx status [--dir <path>] [--verbose]

​
Output

Each provider is shown with its display name, config file path, and a colored status indicator. A summary line is printed afterwards. 
┌────────────────────────────────────────────────────────────────┐
│  2 server(s), 3 provider(s)                                    │
│                                                                │
│  Claude Code       .mcp.json                       sync        │
│  Copilot CLI       .copilot/mcp-config.json        desync      │
│  VS Code           .vscode/mcp.json                missing     │
└────────────────────────────────────────────────────────────────┘
⚠ Some providers are out of date. Run "mcpx sync" to update them.

​
Status meanings

StatusColorMeaning
syncGreenThe provider config file exists and its content exactly matches what MCPX would generate. No action needed.
desyncYellowThe provider config file exists but its content differs from the expected output. Run mcpx sync to bring it up to date.
missingRedThe provider config file does not exist at all. Run mcpx sync to create it.
When all providers are synchronized, MCPX prints All providers are synchronized. instead of the warning. If any provider is desync or missing, the warning directs you to run mcpx sync.
Run mcpx status after manually editing .agents/mcp.json to see exactly which provider files are affected before committing or sharing the project. It is also useful after pulling changes from version control to check whether a mcpx sync is needed.

Build docs developers (and LLMs) love

Get started for freeTalk to us