Deploying from a catalog by slug is convenient and opaque, and being able to read the Docker Compose definition back means what actually landed on the host is inspectable rather than taken on trust. The earnings side has a matching piece of honesty: get_earnings_daily and get_earnings_history read what has already been collected, and trigger_collection is the explicit refresh for when the numbers need to be current rather than merely recent.
A service manager with 10 tools: deploy a catalog service, start, stop, restart or remove it, read its Docker Compose definition and its recent logs, and read the earnings collected across deployed services.
- deploy_service deploys a service from the catalog by slug with its environment, and get_compose returns that service's Docker Compose definition.
- Lifecycle control by slug: start_service, stop_service, restart_service and remove_service.
- get_service_logs returns a service's recent logs, with lines setting how many come back.
- Earnings reads: get_earnings_daily over the last N days, and get_earnings_history for a given period.
- trigger_collection forces an immediate earnings collection across all services.
A host the server can deploy services onto, and the environment values a given catalog service needs, passed as env on deploy.
One command plus a key — npx cashpilot-mcp, then supply credentials