deploy_service
Deploy a service from the catalog
LABSCO SUMMARY
get_compose is what keeps this from being a black box.
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.
What it is
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.
What you get
- 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.
Requirements
A running CashPilot instance: CASHPILOT_URL is its address (default http://localhost:8080) and CASHPILOT_API_KEY its admin API key (CASHPILOT_ADMIN_API_KEY, not the fleet key). Services deploy through that instance, with the environment values a given catalog service needs passed as env on deploy.
Setup effort
One command plus a key — npx cashpilot-mcp, then supply credentials
USE CASES
01
Standing up a service from the catalog
Deployment takes the slug and its environment; reading the Compose definition back is how you see what actually got run.
02
Working out why a deployed service is misbehaving
The logs say what happened and the Compose definition says what it was configured to do, which is usually where the mismatch is.
03
Reading what the services actually earned
Daily and period views read what has been collected; the collection trigger is what makes the numbers current rather than merely recent.
04
Taking a service down and putting it back
Stopping and starting are separate from removing, so pausing a service does not lose the deployment behind it.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_compose
Get the Docker Compose definition for a service
get_earnings_daily
Get daily earnings for the last N days
get_earnings_history
Get earnings history for a given period
get_service_logs
Get recent logs for a deployed service
remove_service
Remove a deployed service
restart_service
Restart a deployed service
start_service
Start a stopped service
stop_service
Stop a deployed service
trigger_collection
Trigger an immediate earnings collection across all services
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. The tools only work against a CashPilot instance you already run; the server listens on 127.0.0.1:8081 by default. The 8 cashpilot:// resources are not tools.
Requires
- npx on PATH
- A running CashPilot instance — its address goes in CASHPILOT_URL (default http://localhost:8080)
- CASHPILOT_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"cashpilot-mcp": {
"command": "npx",
"args": [
"-y",
"cashpilot-mcp"
],
"env": {
"CASHPILOT_URL": "http://localhost:8080",
"CASHPILOT_API_KEY": "<YOUR_CASHPILOT_API_KEY>"
}
}
}
}Set CASHPILOT_URL to your CashPilot instance's address (default http://localhost:8080) and CASHPILOT_API_KEY to that instance's admin API key (CASHPILOT_ADMIN_API_KEY — not the fleet key).
npx
TERMINAL
npx cashpilot-mcp
