Skip to main content

​
Overview

mcpconfig looks for MCP config files under your home directory (~). Each app uses a specific path and format (JSON, TOML, or YAML).
  • list-clients — Lists all known config locations (found and optionally not found with --all).
  • list-servers — Reads JSON configs (mcpServers) and Codex config.toml (mcp_servers) and prints a combined table. Other TOML/YAML configs are not parsed for servers.
  • add-server — Writes only to configs that exist and are JSON or Codex TOML. YAML configs (Goose, Continue.dev) are listed by list-clients but cannot be updated by add-server.
  • delete-server — Removes a server by name from selected configs; only JSON and Codex TOML configs that contain that server are shown.

​
Config paths

Paths are relative to your home directory (~).
macOS: The Library/Application Support/... paths are typical on macOS. On Linux or Windows, some apps may use different locations; mcpconfig uses these paths as-is from the home directory.

​
Config format details

  • JSON — Uses an mcpServers object. Each key is a server name; value has command and optional args.
  • Codex TOML — Uses [mcp_servers.<name>] sections with command and optional args. See the Codex config reference.
  • YAML (Goose, Continue.dev) — Listed by list-clients only; not parsed for list-servers and not writable by add-server or delete-server.