@vessl-ai/mcpctl
v0.0.16
Published
CLI for managing MCP server executions and secrets
Readme
MCPCTL CLI
A powerful CLI for managing MCP servers, secrets, profiles, and the control plane. If you want to automate or script your MCP workflows, this is the tool you need.
Installation
npm install -g @vessl-ai/mcpctlUsage
mcpctl <command> [subcommand] [options]Commands
Server Management (server)
Start a server:
mcpctl server start --file <spec.json> [--profile <name>]--file: Path to the server spec JSON file (required)--profile: Profile name for environment variable injection
Stop a server:
mcpctl server stop <server-name>Restart a server:
mcpctl server restart <server-name>Get server status:
mcpctl server status <server-name>List servers:
mcpctl server list
Secret Management (secret)
Add a secret:
mcpctl secret add <name> --value <value> [--source <vault|keychain|env>]Get a secret:
mcpctl secret get <name> [--source <vault|keychain|env>]List secrets:
mcpctl secret list [--source <vault|keychain|env>]Remove a secret:
mcpctl secret remove <name> [--source <vault|keychain|env>]
Profile Management (profile)
Create a profile:
mcpctl profile create <name> [--description <text>] [--copy-from <name>]Delete a profile:
mcpctl profile delete <name>List profiles:
mcpctl profile listUse a profile:
mcpctl profile use <name>Set profile environment variable:
mcpctl profile env set <key> <value> [--profile <name>]Get profile environment variable:
mcpctl profile env get <key> [--profile <name>]List profile environment variables:
mcpctl profile env list [--profile <name>]Delete profile environment variable:
mcpctl profile env delete <key> [--profile <name>]
Control Plane Management (control-plane or cp)
Start the control plane:
mcpctl control-plane start [--foreground]Stop the control plane:
mcpctl control-plane stopRestart the control plane:
mcpctl control-plane restartGet control plane status:
mcpctl control-plane statusView control plane logs:
mcpctl control-plane logs [--type <stdout|stderr>]
Toolset Management (toolset)
Save a toolset:
mcpctl toolset save <name> --client <client> [--description <desc>]// Save the current client config's toolset (servers) as a named toolset file. Optionally add a description.
Load a toolset:
mcpctl toolset load <name> --client <client>// Load a saved toolset into the current client config. Prompts to save the current config before loading.
List toolsets:
mcpctl toolset list [--client <client>]// List all saved toolsets for the given client (or all clients).
Configuration
- All configuration, profiles, and secrets are stored in
~/.mcpctlby default. - Set the environment variable
DEBUG=truefor verbose logging.
Contributing
Contributions are welcome! If you have suggestions, bug reports, or want to add features, please open an issue or submit a pull request.
Ready to automate your MCP workflows? Clone, install, and get started!
