Overview
What is Cashpilot Mcp?
Cashpilot Mcp is a tiny bridge that exposes any CashPilot instance as an MCP server, enabling LLMs to monitor passive income earnings, manage services, and control fleet workers. It is designed for users of CashPilot who want AI integration for automated oversight and management.
How to use Cashpilot Mcp?
Install via Docker Compose using the image drumsergio/cashpilot-mcp:latest with environment variables CASHPILOT_URL and CASHPILOT_API_KEY, or via npm using npx cashpilot-mcp. Configure using environment variables. The server exposes resources and tools over a single JSON-RPC endpoint (/mcp).
Key features of Cashpilot Mcp
- Exposes any CashPilot instance as an MCP server.
- Provides read-only resources for earnings, services, fleet, and health.
- Offers ten tools to query, manage, and trigger collection.
- Single JSON-RPC endpoint for all interactions.
- Supports both HTTP and stdio transports.
- Can be run via Docker or npm.
Use cases of Cashpilot Mcp
- LLMs monitoring passive income earnings from bandwidth-sharing services.
- AI agents managing deployed services (restart, stop, start, deploy, remove).
- Automated fleet worker control and health score checking.
- Triggering collection from an LLM or agent.
- Querying service logs and compose files via MCP tools.
FAQ from Cashpilot Mcp
What resources and tools does Cashpilot Mcp expose?
It exposes eight read-only resources (cashpilot://earnings/summary, cashpilot://earnings/breakdown, cashpilot://services/deployed, cashpilot://services/catalog, cashpilot://fleet/summary, cashpilot://workers, cashpilot://health/scores, cashpilot://collector-alerts) and ten tools (get_earnings_daily, get_earnings_history, get_service_logs, restart_service, stop_service, start_service, deploy_service, remove_service, trigger_collection, get_compose).
What are the runtime requirements?
It requires a running CashPilot instance with an admin API key. The server binary is written in Go 1.24 and can be run via Docker, npm (which downloads a pre-built Go binary), or local build from source.
Where does Cashpilot Mcp store data?
The server does not store any data; it acts as a bridge to the existing CashPilot instance, so all data resides in that CashPilot instance.
What transports are supported?
It supports HTTP (default, listening on 127.0.0.1:8081) and stdio (set TRANSPORT=stdio). Docker defaults HTTP to 0.0.0.0:8081.
