Skip to main content

Usage

mcpconfig <command> [options]

Commands

CommandDescription
list-clientsList MCP config file locations. By default shows only configs that were found on disk.
list-serversRead all found JSON configs and Codex config.toml, extract MCP servers (mcpServers or mcp_servers), and print a table: app name, server name, command, args.
add-serverInteractive flow: select one or more apps (↑/↓ move, Space toggle, “Select all”, Enter to confirm), then enter server name, command, and args. Writes to every selected config (JSON or Codex TOML).
delete-serverInteractive flow: enter server name to delete, then select one or more apps that contain that server (↑/↓ move, Space toggle, “Select all”, Enter to confirm). Removes the server from every selected config (JSON or Codex TOML).

Options

OptionShortDescription
—all-aOnly for list-clients. Show every known config location (found and not found).

Examples

# See which MCP configs exist and where they are
mcpconfig list-clients

# See all known config locations (including missing ones)
mcpconfig list-clients --all

# See all MCP servers from every found JSON and Codex TOML config in one table
mcpconfig list-servers

# Interactively add an MCP server to one or more configs
mcpconfig add-server

# Interactively remove an MCP server by name from selected configs
mcpconfig delete-server

Output

  • list-clients — One line per config: app name, ✓ or ✗ (found or not), and the full path when found.
  • list-servers — A table with columns: APP, SERVER, COMMAND, ARGS. JSON configs use mcpServers; Codex uses ~/.codex/config.toml and [mcp_servers.<name>]. Other TOML/YAML configs are skipped.
  • add-server — Writes the new server to each selected config; shows success or an error.
  • delete-server — Removes the server from each selected config; shows success, “Server not found”, or an error.

See also