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 add and mcpx remove are the day-to-day commands for keeping your server roster up to date. Both operate on the canonical .agents/mcp.json (or ~/.agents/mcp.json) and automatically sync every configured provider file after making a change, so all your AI tools stay in step without a separate mcpx sync call.

​
mcpx add

mcpx add launches the server wizard to define a new MCP server and appends it to the canonical config. 
mcpx add [name] [--dir <path>] [--verbose]

​
Arguments

ArgumentRequiredDescription
[name]NoPre-check name: if a server with this name already exists, MCPX warns and exits. The interactive wizard always prompts for the final server name.

​
Behavior

  1. If no .agents/mcp.json exists in the target directory (or global scope), MCPX prints a warning and directs you to run mcpx init first.
  2. If name is provided and a server with that name already exists in the config, MCPX warns about the duplicate and exits without making changes.
  3. The interactive server wizard collects the server name, transport type (stdio or http), command or URL, arguments, and environment variables.
  4. The new server is saved to the canonical config.
  5. All configured providers are synced immediately — any provider config file that changed is reported as updated.

​
Example

mcpx add github
MCPX will prompt for transport, command, args, and env vars, then write the result to .agents/mcp.json and update all provider files.

​
mcpx remove

mcpx remove permanently deletes a server from the canonical config and syncs all provider files to reflect the removal. 
mcpx remove [name] [--dir <path>] [--verbose]

​
Arguments

ArgumentRequiredDescription
[name]NoName of the server to remove. If omitted, an interactive picker is shown.

​
Behavior

  1. If no .agents/mcp.json exists, MCPX warns and exits.
  2. If no servers are configured, MCPX reports that the list is empty.
  3. If name is not supplied (or does not match an existing server), MCPX presents an interactive list of server names to choose from.
  4. A confirmation prompt is shown before any changes are made.
  5. After confirmation, the server is removed from the canonical config and all provider files are synced.

​
Example

mcpx remove github
MCPX asks for confirmation, then removes github from .agents/mcp.json and updates every provider config file.
Removal is permanent — the server definition is deleted from the canonical config and cannot be recovered. If you only want to stop a server from appearing in provider configs temporarily, use mcpx disable instead. You can always re-enable it later without re-entering all its settings.
Both mcpx add and mcpx remove call the same sync logic used by mcpx sync internally. After either command completes, every provider file listed in the providers array of .agents/mcp.json reflects the latest state.

Build docs developers (and LLMs) love

Get started for freeTalk to us