CashPilot
MCP server for CashPilot: track passive income and DePIN earnings, manage services
What can you do with CashPilot?
- Read-only resources for earnings, deployed services, the catalog, fleet status, workers, health scores and collector alerts (
cashpilot://earnings/summary,cashpilot://fleet/summary, ...). - Tools to query daily and historical earnings, read service logs, and start, stop, restart, deploy or remove services.
trigger_collectionruns an earnings collection across all services now;get_composereturns a service's Docker Compose definition.- One JSON-RPC endpoint (
/mcp) over HTTP, or stdio withTRANSPORT=stdio. - Listens on
127.0.0.1:8081by default;MCP_AUTH_TOKENadds bearer auth when you expose it. - Ships as a Docker image, an npm package (
npx cashpilot-mcp) and multi-arch Go binaries.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
cashpilot-mcpclaude mcp add cashpilot -e 'CASHPILOT_URL=<CASHPILOT_URL>' -e 'CASHPILOT_API_KEY=<your cashpilot_api_key>' -e 'CASHPILOT_READ_ONLY=false' -- npx -y cashpilot-mcp@0.3.0
{
"mcpServers": {
"cashpilot": {
"command": "npx",
"args": [
"-y",
"cashpilot-mcp@0.3.0"
],
"env": {
"CASHPILOT_URL": "<CASHPILOT_URL>",
"CASHPILOT_API_KEY": "<your cashpilot_api_key>",
"CASHPILOT_READ_ONLY": "false"
}
}
}
}
Environment variables
CASHPILOT_URLrequired CashPilot instance URL (e.g. http://localhost:8080)CASHPILOT_API_KEYrequired secret CashPilot API key: the admin key (CASHPILOT_ADMIN_API_KEY) for full control, or the read-only key (CASHPILOT_READONLY_API_KEY) together with CASHPILOT_READ_ONLY=1. Not the fleet key.CASHPILOT_READ_ONLYSet to true (or 1) to register only the tools that change nothing (no start, stop, restart, deploy, remove or collection)
drumsergio/cashpilot-mcp:v0.3.0claude mcp add cashpilot -e 'TRANSPORT=<TRANSPORT>' -e 'CASHPILOT_URL=<CASHPILOT_URL>' -e 'CASHPILOT_API_KEY=<your cashpilot_api_key>' -e 'CASHPILOT_READ_ONLY=false' -- docker run -i --rm drumsergio/cashpilot-mcp:v0.3.0
{
"mcpServers": {
"cashpilot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"drumsergio/cashpilot-mcp:v0.3.0"
],
"env": {
"TRANSPORT": "<TRANSPORT>",
"CASHPILOT_URL": "<CASHPILOT_URL>",
"CASHPILOT_API_KEY": "<your cashpilot_api_key>",
"CASHPILOT_READ_ONLY": "false"
}
}
}
}
Environment variables
TRANSPORTrequired Runs the image on stdio instead of its default HTTP listenerCASHPILOT_URLrequired CashPilot instance URL (e.g. http://localhost:8080)CASHPILOT_API_KEYrequired secret CashPilot API key: the admin key (CASHPILOT_ADMIN_API_KEY) for full control, or the read-only key (CASHPILOT_READONLY_API_KEY) together with CASHPILOT_READ_ONLY=1. Not the fleet key.CASHPILOT_READ_ONLYSet to true (or 1) to register only the tools that change nothing (no start, stop, restart, deploy, remove or collection)
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
cashpilot-mcp
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 talks to your own CashPilot instance with its admin API key, over HTTP or stdio.
Features
- Read-only resources for earnings, deployed services, the catalog, fleet status, workers, health scores and collector alerts (
cashpilot://earnings/summary,cashpilot://fleet/summary, ...). - Tools to query daily and historical earnings, read service logs, and start, stop, restart, deploy or remove services.
trigger_collectionruns an earnings collection across all services now;get_composereturns a service's Docker Compose definition.- One JSON-RPC endpoint (
/mcp) over HTTP, or stdio withTRANSPORT=stdio. - Listens on
127.0.0.1:8081by default;MCP_AUTH_TOKENadds bearer auth when you expose it. - Ships as a Docker image, an npm package (
npx cashpilot-mcp) and multi-arch Go binaries.
Quick start
Register the npm package in your MCP client (Claude Desktop, Claude Code, Cursor); npx runs it over stdio:
{
"mcpServers": {
"cashpilot": {
"command": "npx",
"args": ["-y", "cashpilot-mcp"],
"env": {
"CASHPILOT_URL": "http://localhost:8080",
"CASHPILOT_API_KEY": "<your CASHPILOT_ADMIN_API_KEY>"
}
}
}
}
The key is CashPilot's admin API key, not the fleet key. Docker Compose, the HTTP server and local builds are in Getting started.
Documentation
- Getting started: Docker Compose, npm, local build
- Configuration: environment variables and MCP client configuration
- Usage: resources and tools
- Development: testing, contributing, credits
- Related projects: the family and registry listings
Related projects
CashPilot, the passive income fleet manager this server talks to.
License
Frequently asked questions
What is CashPilot?
MCP server for CashPilot: track passive income and DePIN earnings, manage services
How do I install CashPilot?
It runs on your machine. In Claude Code: claude mcp add cashpilot -e 'CASHPILOT_URL=<CASHPILOT_URL>' -e 'CASHPILOT_API_KEY=<your cashpilot_api_key>' -e 'CASHPILOT_READ_ONLY=false' -- npx -y cashpilot-mcp@0.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does CashPilot need an API key?
Yes. It expects CASHPILOT_URL, CASHPILOT_API_KEY, TRANSPORT, which you set in its configuration.
Is CashPilot open source?
Yes. Its code is on GitHub under the GPL-3.0 license.
Who maintains CashPilot?
It is published by GeiserX. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.