Description
mcpm.sh/src/mcpm/commands/client.py
Line 117 in 3ff1c95
When setting a client, mcpm suggests that come commands will now operate on that client
mcpm client set continue
Success: Active client set to continue
╭──────────────────────────────────────────────────────────────────────────────────────────── Active Client Changed ────────────────────────────────────────────────────────────────────────────────────────────╮
│ The active client (continue) will be used for all MCP operations. │
│ Commands like 'mcpm list', 'mcpm status', and 'mcpm install' will now operate on continue. │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Listed commands are not valid:
# mcpm list
Usage: mcpm [OPTIONS] COMMAND [ARGS]...
Error: No such command 'list'.
# mcpm status
Usage: mcpm [OPTIONS] COMMAND [ARGS]...
Error: No such command 'status'.
# mcpm install
Usage: mcpm [OPTIONS] COMMAND [ARGS]...
Error: No such command 'install'.
Should probably be:
- mcpm list -> mcpm ls
- mcpm install -> mcpm add
- mcpm status -> ???