cashpilot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CASHPILOT_URL | Yes | CashPilot instance URL | |
| CASHPILOT_API_KEY | Yes | CashPilot admin API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_serviceB | Deploy a service from the catalog |
| get_composeB | Get the Docker Compose definition for a service |
| get_earnings_dailyC | Get daily earnings for the last N days |
| get_earnings_historyC | Get earnings history for a given period |
| get_service_logsB | Get recent logs for a deployed service |
| remove_serviceA | Remove a deployed service |
| restart_serviceA | Restart a deployed service |
| start_serviceC | Start a stopped service |
| stop_serviceB | Stop a deployed service |
| trigger_collectionA | Trigger an immediate earnings collection across all services |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Collector alerts | Recent collection errors and alerts |
| Deployed services | Running services with health, CPU, and memory usage |
| Earnings breakdown | Per-platform earnings with cashout eligibility |
| Earnings summary | Total earnings, today, this month, and active service count |
| Fleet summary | Aggregated fleet statistics across all workers |
| Health scores | Per-service health scores across the fleet |
| Service catalog | Full catalog of available bandwidth-sharing services |
| Workers | All registered workers (servers) in the fleet |
TDQS
Scored across 10 tools
Most tools are clearly distinct lifecycle actions (deploy, start, stop, restart, remove), but get_earnings_daily and get_earnings_history overlap in purpose and could cause selection confusion around which time range is intended.
All tools follow a consistent verb_noun snake_case pattern (deploy_service, get_service_logs, trigger_collection). The naming is predictable and easy to infer.
Ten tools is a well-scoped size for a service lifecycle and earnings reporting server. Each tool serves a clear operational purpose without unnecessary bloat.
The service lifecycle covers deploy/start/stop/restart/remove and logs, but there is no tool to list deployed services or retrieve service status, which is a notable gap for agents managing services. Earnings coverage is adequate with daily and historical views plus collection triggering.