Main
Use
clientsto discover where each tool stores MCP config (Claude Code, Cursor, VS Code/Copilot, Gemini CLI, etc.) before making changes.Prefer JSON (
--json) output when driving it from an agent; the README calls out redaction of known secret patterns.Use backup/rollback features before mutating configs so you can revert if a client fails to start servers after edits.
Source-backed notes
- README shows install:
npm install -g mcpickand alsonpx mcpick --helpas a no-install entry point. - README lists supported clients and example commands for list/enable/disable/add/remove MCP servers.
- README documents backup/restore/rollback and profile save/load flows for safer config mutations.
FAQ
- Will it leak secrets in JSON output?: README says it redacts known secret patterns and prints
***for env/headers values. - Does it work without a TTY?: README says non-TTY runs show help instead of launching the interactive TUI for safety.
- What is the smallest safe flow?: Start with
mcpick clients, thenmcpick list --json, then backup before any edits.